> For the complete documentation index, see [llms.txt](https://docs.allmcp.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allmcp.co/help-center/troubleshooting.md).

# Troubleshooting

Common issues and quick fixes. Most problems come down to one of three things: a missing or invalid API key, a provider that isn't connected yet, or an OAuth consent step that hasn't been completed.

{% hint style="warning" icon="life-ring" %}
**Still stuck after this page?** Ask your agent to report the issue with a short description of what happened — it routes the details to the AllMCP team.
{% endhint %}

***

## Connection & tools

{% hint style="info" %}

<details>

<summary>My agent doesn't see any tools</summary>

A provider's tools become available once you connect that provider. Ask your agent to **"list the available integrations"** to see the catalog, then connect one. Once a provider is connected, its tools show up for the agent to use.

</details>

<details>

<summary>I get a 401 Unauthorized</summary>

Check that the `X-API-Key` header is present and the key is valid. The `Authorization: Bearer allmcp_xxx` format works as a fallback. Keys are created in the dashboard at [allmcp.co/login](https://allmcp.co/login).

</details>

<details>

<summary>Connecting a provider asks me to complete a consent step</summary>

That's expected for OAuth providers (Google Sheets, Google Ads, amoCRM, Kommo). Your agent will hand you a consent link — open it in a browser and grant access. Once you've granted access, the provider's tools become available.

</details>

<details>

<summary>A provider stopped working / asks me to reconnect</summary>

This happens when access to the provider was revoked or the grant expired. Ask your agent to reconnect the provider — you'll get a fresh consent link to grant access again. AllMCP keeps connections refreshed for you while access is still valid, so this is rare.

</details>
{% endhint %}

## Multi-user & data scoping

{% hint style="info" %}

<details>

<summary>An agent sees the wrong user's data</summary>

For multi-user setups, append `?user_id=<id>` to the endpoint URL (add `?org_id=<id>` as well if you separate users by organization) so each request maps to that user's own connected accounts. See [Multi-Tenancy](https://docs.allmcp.co/documentation/api-reference/multi-tenancy).

</details>

<details>

<summary>I'm hitting rate limits</summary>

Rate limits are enforced by the upstream provider, not AllMCP. For example, Bitrix24 allows \~2 requests/second per webhook and queues the excess. Spread bulk operations out, or let the agent retry.

</details>
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.allmcp.co/help-center/troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.