Connecting AllMCP

AllMCP speaks the standard MCP protocol over HTTP, with two ways to authenticate:

• Sign in (OAuth) — clients with a connector dialog (Claude Desktop/web/mobile, ChatGPT, Perplexity) need only the URL. Add it, sign in with Google or GitHub, done — no key to copy.
• API key — config-file and code-based clients send your key in a header. Best for scripted setups and team scoping with ?user_id=.

Parameter	Required	Where	Value
url	Yes	Config	https://go.allmcp.co/mcp/
X-API-Key	For API-key clients	HTTP header	Your AllMCP API key (allmcp_xxx). Clients that only accept a bearer token can send it as Authorization: Bearer allmcp_xxx instead. Not needed when the client signs in with OAuth.
user_id	Optional	URL query param	An identifier for the end user, so each person keeps their own connected providers
org_id	Optional	URL query param	An identifier for the organization, so each workspace keeps its own connected providers

---

Two tracks

Desktop & IDE clients

Note

No code required. Add AllMCP with one command (CLI clients) or one config block (desktop & IDE clients). Each page below shows the exact step for that client.

Claude Desktop Sign in as a Connector, or use the config file — also covers claude.ai web and mobile.

ChatGPT Add AllMCP as a custom app with OAuth sign-in.

Claude Code One-command setup in the terminal.

Cursor One-click install or config block.

Windsurf Connect AllMCP to Windsurf.

VS Code Connect AllMCP to VS Code.

OpenAI Codex CLI, IDE extension, and Desktop app.

Gemini CLI One-command setup in the terminal.

Perplexity Add AllMCP as a custom connector.

More clients

Note

More MCP clients that work with AllMCP. Same https://go.allmcp.co/mcp/ endpoint and X-API-Key header — only the config location differs.

Cline VS Code AI agent extension.

Roo Code VS Code AI agent extension.

Continue VS Code & JetBrains assistant.

Zed The Zed editor.

Goose Block's open-source agent.

Warp The Warp terminal.

mcp-remote bridge For clients that only run local servers.

Agent frameworks

Note

Use AllMCP as a tool source inside Python agent code. Each framework has a 10-line setup snippet.

Frameworks overview Read this first — connection params and the general pattern.

Anthropic SDK Native MCP support via the anthropic package.

LangChain & LangGraph Connect via langchain-mcp-adapters.

CrewAI Multi-agent crews with AllMCP tools.

PydanticAI Typed agents with native MCP support.

All 15 frameworks LlamaIndex, AutoGen, DSPy, Flowise, Zapier, Ollama, and more.

---

URL construction

Just me

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

One per end user

https://go.allmcp.co/mcp/?user_id=<your-user-id>

One per organization and user

https://go.allmcp.co/mcp/?org_id=<your-org-id>&user_id=<your-user-id>

Note

user_id and org_id can be any stable identifier from your system, such as UUIDs, database IDs, or slugs. Each value keeps that user’s or organization’s connected providers separate, so credentials never cross over between them.

---

Client compatibility

Every client on this page works with the plain https://go.allmcp.co/mcp/ endpoint — you never have to add tuning options to the URL. AllMCP tailors what it presents to each client automatically, so browser connectors, terminal agents, IDE assistants, and desktop apps each see exactly the tools they can use.

Client	Setup	Extra URL options
Claude Desktop & Claude Code	Config block / one command	None needed
ChatGPT connectors	Custom connector	None needed
OpenAI Codex	CLI, IDE & Desktop	None needed
Cursor, VS Code, Windsurf, Zed	Config block	None needed
Goose	Config block	None needed
mcp-remote bridge	Local bridge command	None needed

Note

Just connected a provider but don’t see its tools yet? Some clients keep a fixed tool list and only pick up new tools when you refresh. If your new provider’s tools don’t appear right after you connect it, ask your client to refresh its tools (or reconnect) once — they’ll show up.

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