> 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/documentation/how-it-works.md).

# How It Works

AllMCP gives your AI agent one endpoint that connects to all your SaaS tools. Point your MCP client at the endpoint with your API key, ask your agent to connect a provider, and that provider's tools become available to the agent. This page covers the three things you need: the endpoint, your API key, and how to identify users.

***

## The endpoint

Your agent connects over MCP (SSE / Streamable HTTP) to:

```
https://go.allmcp.co/mcp/
```

That single URL is all your agent ever talks to, no matter how many providers you connect.

***

## Authentication

Every request carries your AllMCP API key in a single header:

```
X-API-Key: allmcp_xxxxxxxxxxxxxxxxxxxxxxxx
```

If your client can't set custom headers, the `Authorization: Bearer` format works too:

```
Authorization: Bearer allmcp_xxxxxxxxxxxxxxxxxxxxxxxx
```

{% hint style="info" icon="key" %}
Your raw API key is never stored or logged.
{% endhint %}

***

## Identifying users

Your API key identifies you. To keep each end user's provider connections separate, add identifiers to the endpoint URL. Pick the mode that fits how you're using AllMCP.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-user" style="color:$primary;">:user:</i></h4></td><td><strong>Solo mode</strong></td><td>One API key, one user. Ideal for Claude Desktop, Cursor, personal agents.</td><td><a href="https://docs.allmcp.co/documentation/api-reference/multi-tenancy">https://docs.allmcp.co/documentation/api-reference/multi-tenancy</a></td></tr><tr><td><h4><i class="fa-users" style="color:$primary;">:users:</i></h4></td><td><strong>2-level mode</strong></td><td>One client key, multiple users. Ideal for a company deploying AllMCP for their team.</td><td><a href="https://docs.allmcp.co/documentation/api-reference/multi-tenancy">https://docs.allmcp.co/documentation/api-reference/multi-tenancy</a></td></tr><tr><td><h4><i class="fa-layer-group" style="color:$primary;">:layer-group:</i></h4></td><td><strong>3-level mode</strong></td><td>One client key, multiple organizations, multiple users per org. Ideal for platforms building on top of AllMCP.</td><td><a href="https://docs.allmcp.co/documentation/api-reference/multi-tenancy">https://docs.allmcp.co/documentation/api-reference/multi-tenancy</a></td></tr></tbody></table>

### Solo mode

One API key, one user. Ideal for Claude Desktop, Cursor, personal agents.

```
URL:    https://go.allmcp.co/mcp/
Header: X-API-Key: allmcp_xxx
```

### 2-level mode

One client key, multiple users. Ideal for a company deploying AllMCP for their team.

```
URL:    https://go.allmcp.co/mcp/?user_id={external_user_id}
Header: X-API-Key: allmcp_xxx
```

`user_id` is your system's identifier for the user — a UUID, a database ID, any stable string. Each user keeps their own set of provider credentials.

### 3-level mode

One client key, multiple organizations, multiple users per org. Ideal for platforms building on top of AllMCP.

```
URL:    https://go.allmcp.co/mcp/?org_id={org_id}&user_id={user_id}
Header: X-API-Key: allmcp_xxx
```

This is the full hierarchy: you (the client) → your customer (the organization) → their employee (the user).

***

## Connecting a provider

Once your client is pointed at the endpoint, ask your agent to connect a provider. The credentials a provider needs depend on how it authenticates.

{% tabs %}
{% tab title="API key providers" %}
Providers such as Bitrix24, YouGile, Binotel, SalesDrive, and Altegio authenticate with an API key or webhook URL you supply. Hand your agent the credential and ask it to connect the provider; its tools become available right away.
{% endtab %}

{% tab title="OAuth2 providers" %}
Providers such as Google Sheets, Google Ads, amoCRM, and Kommo use OAuth2. Ask your agent to connect the provider and it returns a link. Open that link, approve access in your browser, and the provider's tools become available. AllMCP handles the consent flow and keeps the connection refreshed for you.

{% hint style="info" icon="bolt" %}
If a connection ever needs to be re-approved, the next tool call returns a clear message telling you to reconnect.
{% endhint %}
{% endtab %}
{% endtabs %}

After a provider is connected, your agent can use that provider's tools. You only ever deal with the providers you've actually connected.

***

## Discovering and managing connections

A few built-in capabilities are always available, no matter which providers are connected. You don't trigger these yourself — just ask your agent in plain language ("connect Kommo", "which providers am I connected to?", "what can Bitrix24 do?") and it handles the rest.

| You can ask your agent to… | What happens                                                                             |
| -------------------------- | ---------------------------------------------------------------------------------------- |
| Browse providers           | Shows the catalog of available providers and which ones you've already connected.        |
| Connect a provider         | Links an account using the credentials you supply or by walking you through its sign-in. |
| Disconnect a provider      | Removes a connection so its tools are no longer available.                               |
| Inspect a provider         | Shows what a connected provider can do, so you know what to ask for before you start.    |
| Report a problem           | Sends a report to the AllMCP team when something goes wrong.                             |

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-bolt" style="color:$primary;">:bolt:</i></h4></td><td><strong>System tools</strong></td><td>The always-on tools every connection ships with.</td><td><a href="https://docs.allmcp.co/documentation/api-reference/system-tools">https://docs.allmcp.co/documentation/api-reference/system-tools</a></td></tr><tr><td><h4><i class="fa-users" style="color:$primary;">:users:</i></h4></td><td><strong>Multi-tenancy</strong></td><td>How clients, organizations, and users map to credentials.</td><td><a href="https://docs.allmcp.co/documentation/api-reference/multi-tenancy">https://docs.allmcp.co/documentation/api-reference/multi-tenancy</a></td></tr></tbody></table>


---

# 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/documentation/how-it-works.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.