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

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.

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

2-level mode One client key, multiple users. Ideal for a company deploying AllMCP for their team.

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

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.

API key providers
OAuth2 providers

Providers such as Bitrix24, amoCRM, Kommo, YouGile, Binotel, SalesDrive, Altegio, and iiko authenticate with an API key, webhook URL, or provider-issued token. Ask your agent to connect the provider, then enter the credential on the secure browser page it returns.

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.

System tools The always-on tools every connection ships with.

Multi-tenancy How clients, organizations, and users map to credentials.