Multi-Tenancy

AllMCP separates your connections by client, organization, and user. You choose how many levels you need: a single personal setup, a team where each person connects their own accounts, or a platform serving many customer companies.

Each user keeps their own private set of connections. When Marina connects Bitrix24, only Marina’s session can use Bitrix24 — nobody else on the same client key sees her connection or her data.

---

Choosing a mode

All three modes use the same endpoint and the same API-key header. The only difference is which identifiers you add to the URL.

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

Solo mode

One key, one user. Use this for personal setups — Claude Desktop, Cursor, or a private agent.

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

You don’t need to add anything to the URL. Every connection you make belongs to you.

2-level mode (Direct)

One client key, multiple users. Use this when your team or product has several people who each connect their own provider accounts.

URL:    https://go.allmcp.co/mcp/?user_id=EXTERNAL_USER_ID
Header: X-API-Key: allmcp_xxx

user_id is any stable identifier from your own system — a database ID, a Slack user ID, an email hash. Each distinct user_id gets its own private set of connections.

Example: A company of 20 sales reps, each connecting their own Bitrix24:

per_user_url.py

# Each rep gets their own URL:
url = f"https://go.allmcp.co/mcp/?user_id={rep.id}"

3-level mode (Platform)

One platform key, multiple organizations, multiple users per organization. Use this if you’re a platform (a SaaS or AI product) offering AllMCP to many customer companies.

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

Example: A B2B platform serving multiple companies, each with their own users:

per_org_user_url.py

url = f"https://go.allmcp.co/mcp/?org_id={company.id}&user_id={employee.id}"

Note

Independent connections. Each org_id + user_id combination is its own private set of connections. Marina at JSM Co and Marina at Acme Corp are two separate users, even if they share the same user_id string.

---

Which identifiers to pass

Add identifiers to the URL based on the mode you want:

org_id	user_id	Result
Not set	Not set	Solo — a single default user for the key
Not set	Set	2-level — a user under your client key
Set	Set	3-level — a user under an organization under your client key
Set	Not set	Treated as Solo — organization scoping needs a user_id too

Tip

No pre-registration needed. You don’t have to create users or organizations ahead of time. Just start making calls with the user_id (and org_id if you’re on a platform) and AllMCP keeps each one separate for you.

---

Branded OAuth consent (platform mode)

In 3-level mode, each organization can use its own OAuth app for OAuth2 providers, so the consent screen your enterprise customers see carries their branding instead of AllMCP’s.

Set this up in the AllMCP dashboard under Organizations → select the organization → OAuth Apps.

---

Your connections stay private

Every user’s connections are kept private and isolated. No user, organization, or client can see another user’s stored credentials.

Danger

Even you can’t read another user’s credentials. As the key holder, you can manage who connects, but you cannot read the stored credentials of any individual user.

---

Related

API Keys

Built-in capabilities