> For the complete documentation index, see [llms.txt](https://docs.metacopier.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metacopier.io/ai/ai/troubleshooting.md). # Troubleshooting *** ## The assistant says it has no tools, or does not see MetaCopier at all The tool list is fetched when the connection is established and then cached by your AI application. If you changed the URL, changed toolsets or the catalogue was extended, the client is still holding the old list. **Fix.** Disconnect and reconnect the connector, or restart the client. In ChatGPT and Claude, removing and re-adding the connector is the reliable way. *** ## The assistant refuses to do something it should be able to do Ask it directly: > Describe this connection. The answer names the project, whether the connection may write, when the current credential expires (on OAuth, an API key does not expire) and which access rules apply. Common outcomes:
What it saysWhat to do
Read onlyYour key is READ_ONLY, or you are on a /readonly endpoint, or the OAuth connection has no write scope, or the project has more than 100 accounts. See authentication and large projects are read only.
The wrong projectYou connected without naming a project and got the oldest one. Use /p/{projectId}/mcp. See which project does it use.
The right project, still refusedAn access policy on the key is blocking the endpoint. See access policy.
*** ## `... is not available on this endpoint.` The tool exists, but it is not in the toolsets this URL publishes, or it is a write tool on a `/readonly` endpoint. **Fix.** Add the toolset to the URL or the `X-MC-Toolsets` header, or drop the `/readonly` suffix. See [endpoints and toolsets](/ai/ai/endpoints.md). *** ## `There is no toolset named ...` A typo in the URL. The error lists every toolset that exists, and the [toolset table](/ai/ai/endpoints.md#toolsets) has them too. Note that they are singular or plural exactly as listed, for example `copiers` and not `copier`. In the URL they have to be lowercase, in the `X-MC-Toolsets` header the case does not matter. *** ## `[PROJECT_NOT_FOUND]` MetaCopier could not resolve a project for the connection. Either the project id in the URL does not exist or was deleted, or you connected without a project and nothing qualified. Nothing qualifies when: * You own no project at all, for example because every project you work with was shared with you rather than created by you. * Every project you own is a white label project. Those are skipped on purpose. **Fix.** Name the project in the URL: `https://ai.metacopier.io/p/{projectId}/mcp`. *** ## `[AI_CREDENTIAL_CUSTOMER_NOT_RESOLVED]` You signed in, but the login could not be matched to a MetaCopier customer. This usually means you signed in with a different identity from the one your MetaCopier account uses, for example a different email or a different social login. **Fix.** Sign out in the AI application, reconnect, and sign in with the account you use in the MetaCopier web app. *** ## `[AI_KEY_REVOKED]` The project's **AI Apps** key was revoked, which blocks all AI access to that project. **Fix.** Restore or recreate the key in **Projects → API Keys**, then reconnect. *** ## `401 Unauthorized`
CauseFix
The API key is wrong, expired or revokedCreate a new key and update your client
The key was pasted with a trailing space or a line breakPaste it again, carefully
The OAuth session endedReconnect the connector and sign in again
The token was issued for a different serverCheck the URL. A token is only valid for the MCP server it was issued for.
*** ## `404 Not Found` The URL shape is wrong. Valid shapes are: ``` https://ai.metacopier.io/mcp https://ai.metacopier.io/mcp/readonly https://ai.metacopier.io/mcp/x/{toolset} https://ai.metacopier.io/mcp/x/{toolset}/readonly https://ai.metacopier.io/p/{projectId}/mcp https://ai.metacopier.io/p/{projectId}/mcp/readonly https://ai.metacopier.io/p/{projectId}/mcp/x/{toolset} https://ai.metacopier.io/p/{projectId}/mcp/x/{toolset}/readonly ``` A `{projectId}` that is not a valid UUID also produces a 404, and so does a malformed toolset list such as `x/copiers,` or `x/,copiers`. *** ## The assistant is slow or loses track of what it is doing Too many tools. A model given 129 tools spends its attention choosing between them rather than answering. **Fix.** Connect to the toolsets you actually need. `/mcp/x/accounts,copiers,logs` is a good working set for diagnosing problems, and the default `/mcp` already gives you exactly that. *** ## A trade did not happen, or happened differently than expected 1. If the assistant used `metacopier_send_order`, it never waited for the broker. Check the account log, the rejection is there. 2. Check the symbol. Brokers spell symbols differently, and the assistant may have used the name you said rather than the name the account has. 3. If the account is a master, the trade was copied to its followers with each copier's own sizing. That is normal, see [trading with AI](/ai/ai/trading.md#copiers-still-apply). 4. Ask the assistant to read the account log for the last few minutes and explain it. That is what the `logs` toolset is for. *** ## Still stuck {% content-ref url="/pages/J12gWkmL9SXg0F1wNGAQ" %} [Support](/metacopier/support.md) {% endcontent-ref %} When you write in, include the URL you connected to, whether you used an API key or OAuth, and the exact error text.