FITsociety Help EN

Solving MCP error messages

5 min read

Does your AI assistant report an error from FITsociety? It often mentions a code starting with COMPANY_MCP. As an Admin you also see that code at the connection under Recent Tool Calls, beside the failed call.

Check this first

  1. Is the connection still active? Look under Settings → AI connections (MCP) and open the connections list. Does it say Revoked or Expired? Then connect again from your AI assistant.

  2. Is the part on? Click the connection and look under Modules. If it is missing, revoke the connection and connect again with that part.

  3. May the assistant make changes? Is the connection read-only, or is the required write action missing? Reconnect and enable the action under Also make changes.

  4. Have you given consent? Check that you explicitly authorized the selected health data and private communications.

Login and access

  • COMPANY_MCP_TOKEN_INVALID: your login in the AI assistant has expired or was revoked. Reconnect the connector in your AI assistant and log in again.

  • COMPANY_MCP_KEY_INVALID: the API key is wrong, expired or revoked. Create a new key under New API key.

  • COMPANY_MCP_KEY_REQUIRED: the AI tool does not send a key. Check the tool's settings.

  • COMPANY_MCP_FEATURE_DISABLED: MCP is available to all FITsociety companies. If you still receive this code, send the code, company name and time to support so we can check why access is being blocked.

  • COMPANY_MCP_COMPANY_BLOCKED: your company is blocked. Contact support.

  • COMPANY_MCP_GRANT_OWNER_INACTIVE: the coach who made the connection is no longer an active Manager or Admin, and there is no other active Manager or Admin in the company either. Make sure there is an active Manager or Admin and let them connect again.

Permissions

  • COMPANY_MCP_ACCESS_DENIED: the connection lacks the part, write action or consent that is needed. Go through the checklist above.

  • COMPANY_MCP_MODULE_FORBIDDEN: the action belongs to a part that is not in your connection. Connect again with that part.

  • COMPANY_MCP_TOOL_NOT_GRANTED: the action is not allowed for this connection. Let your assistant refresh its list of tools, or connect again with the right permissions.

Too much at once or too slow

  • COMPANY_MCP_QUERY_BUDGET_EXCEEDED: the connection performed too many actions within one minute. A change counts more heavily than a lookup. Wait a moment and let the assistant continue where it stopped.

  • COMPANY_MCP_RATE_LIMITED: too many requests came in at once. Wait a moment and try again.

  • COMPANY_MCP_CIRCUIT_OPEN: this action is temporarily paused after repeated failures. Wait a moment and try again.

  • COMPANY_MCP_TOOL_TIMEOUT: the action took too long. First check in FITsociety whether the change was saved after all, before you have it done again.

Saving changes

  • COMPANY_MCP_IDEMPOTENCY_REQUIRED: the assistant did not include a unique key with a change. Have it refresh the tool list and perform the change with the required unique key. If the outcome is uncertain, first check what was saved in FITsociety.

  • COMPANY_MCP_IDEMPOTENCY_IN_PROGRESS: the same change is still being processed. Wait a moment and then check the result.

  • COMPANY_MCP_IDEMPOTENCY_KEY_REUSED: the assistant used the same key for a different change. Have it perform the new change as a separate instruction with a new key. An unchanged retry of the same instruction must use the same key.

Data and input

  • COMPANY_MCP_CLIENT_NOT_FOUND: the member was not found in this company, or was removed, rejected or blocked. Check the name and the company.

  • COMPANY_MCP_NOT_FOUND: the requested item does not exist (anymore). Let the assistant search again first.

  • COMPANY_MCP_INVALID_INPUT: the assistant filled in something incorrectly, such as a date or an ID. Phrase your question more precisely.

  • COMPANY_MCP_CONFLICT: the change clashes with what already exists, for example because more than one item matches. Say exactly which item you mean.

  • COMPANY_MCP_DATE_RANGE_TOO_WIDE: the requested period is too long. Ask for a shorter period.

A member reports an error

  • COMPANY_MCP_CLIENT_MCP_DISABLED: your company does not allow AI connections for members. As an Admin, enable this under Member access under Settings → AI connections (MCP) and choose at least one allowed area.

  • COMPANY_MCP_CLIENT_AI_DISABLED: Client AI is not enabled for this member. Read: Client AI for members: reviewing requests and enabling access.

  • COMPANY_MCP_CLIENT_MCP_SCOPE_NOT_ALLOWED: the areas in the member's connection are no longer allowed under Member access. Adjust the policy or let the member connect again.

Still not working?

Send us a chat message with the error code, connection name, time and technical tool name from Recent Tool Calls. A screenshot also helps. Never send your API key.

Also read: Seeing in the audit log what an AI assistant looked up or did.

After a timeout or unclear result, do not have the assistant repeat all previous changes. Check the outcome and resume from the unfinished step. An exact retry must use the same unique key so that a saved change is not applied twice.

Was this article helpful? Thanks for your feedback!

Thanks, we read every comment.

Related articles