Claude Desktop

Connect AllMCP to Claude Desktop in under 60 seconds — and to Claude on the web and mobile with the same steps.

Get your API key Browse providers

---

Add as a Connector — no terminal needed

The fastest path, and the only one you need on claude.ai web and the Claude mobile apps. You sign in with your AllMCP account instead of pasting an API key.

1. Open the connector dialog

   Go to Settings → Connectors → Add custom connector (the same screen exists in Claude Desktop, on claude.ai, and in the mobile apps).

2. Paste the AllMCP URL

   Enter a name (e.g. AllMCP) and the server URL:

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

   Leave the optional OAuth Client ID / Client Secret fields empty — Claude registers itself automatically.

3. Authorize with your AllMCP account

   Claude opens the AllMCP authorization page. Continue with Google or GitHub — the same one-click sign-in as the dashboard. That’s it: no API key, no config file, no Node.js.

4. Verify it’s working

   Open a new conversation and type:

   What integrations does AllMCP support?

   Claude returns the full provider catalog, so you know the connection is live.

Note

You can disconnect a connector anytime from your AllMCP dashboard — any access it granted expires on its own shortly after.

---

Setup via config file

Prefer the terminal, a pinned API key, or scoping the connection to a specific team member? The config-file route is still fully supported.

One command

Run this in a terminal (Node.js 18.17+ — the bridge below needs it anyway):

npx allmcp install claude-desktop

It locates the config file on macOS, Windows, or Linux, backs it up to claude_desktop_config.json.bak, and merges the allmcp entry without touching your other servers. Keyless by default — Claude Desktop opens the AllMCP sign-in in your browser on first launch. Then restart Claude Desktop and you’re done.

Want a pinned API key instead of OAuth? Add --key YOUR_API_KEY (or set the ALLMCP_KEY environment variable). Or run the full interactive setup — sign-in, auto-detect, verify — with a bare npx allmcp.

Or edit the file by hand

1. Locate the config file

   Windows

   C:\Users\<your-username>\AppData\Roaming\Claude\claude_desktop_config.json

   This is the same location as %APPDATA%\Claude\claude_desktop_config.json — paste that into the File Explorer address bar to jump straight there.

   macOS

   ~/Library/Application Support/Claude/claude_desktop_config.json

2. Add the allmcp entry

   Claude Desktop’s config file connects to remote servers through the mcp-remote bridge (it needs Node.js installed — check with node --version). Add allmcp to mcpServers, replacing YOUR_API_KEY with your AllMCP key:

   claude_desktop_config.json

   {
     "mcpServers": {
       "allmcp": {
         "command": "npx",
         "args": ["-y", "mcp-remote", "https://go.allmcp.co/mcp/", "--header", "X-API-Key:${ALLMCP_API_KEY}"],
         "env": {
           "ALLMCP_API_KEY": "YOUR_API_KEY"
         }
       }
     }
   }

   Caution

   Two things matter here. Claude Desktop’s config only supports local command servers — a plain "url" entry is rejected (and can blank out your mcpServers), which is why the connection goes through npx mcp-remote. And write the header with no space — X-API-Key:${ALLMCP_API_KEY} — with the key value in env; this sidesteps a Windows npx quirk that splits spaces inside arguments.

   If you already have other MCP servers, add allmcp alongside them inside the same mcpServers object.

3. Apply the config

   Restart Claude Desktop — changes to the config file only take effect after a restart.

   Caution

   Restart required — fully quit, don’t just close the window. On Windows: right-click the system-tray icon and choose Quit. On macOS: quit from the menu-bar icon.

4. Verify it’s working

   Open a new conversation and type:

   What integrations does AllMCP support?

   Claude returns the full provider catalog, so you know the connection is live.

Note

Connector or config file? The Connector path signs you in with your AllMCP account and works everywhere — Desktop, web, mobile. The config file authenticates with an API key and is the right choice for scripted setups or scoping a shared machine to one team member with ?user_id=.

Caution

No tools showing up after restart?

Quick checks

• Did you fully quit? Closing the window isn’t enough — quit from the system-tray icon (Windows) or the menu-bar icon (macOS), then reopen.
• Is Node.js installed? Run node --version in a terminal. If it errors, install the LTS from nodejs.org and restart Claude Desktop.
• First launch is slow — npx downloads mcp-remote once; give it a few seconds.
• Key correct? ALLMCP_API_KEY should be your real key starting with allmcp_.

See the mcp-remote page for more on the bridge.

---

Connect your first provider

Just ask Claude in plain language. For a provider that uses a key or webhook URL, include the credential in your message:

Connect my Bitrix24. The webhook URL is https://my-portal.bitrix24.ru/rest/1/abc123/

For an OAuth provider, just name it:

Connect Google Sheets

Note

For Google Sheets and other OAuth providers, Claude returns a link — open it in your browser to authorize access. AllMCP handles the consent and keeps your connection refreshed for you.

---

Scoping to a specific user

If you’re building a team setup where multiple users share a Claude Desktop instance, add user_id to the URL argument:

claude_desktop_config.json

{
  "mcpServers": {
    "allmcp": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://go.allmcp.co/mcp/?user_id=marina-uuid", "--header", "X-API-Key:${ALLMCP_API_KEY}"],
      "env": {
        "ALLMCP_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Each user_id keeps its own separate set of connected providers, so one person’s credentials never mix with another’s.

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

Quickstart Connect AllMCP to your agent in under 2 minutes.

All providers Browse every connected provider.