mcp-remote bridge

Some MCP clients can only launch local servers (a command on your machine), not connect to a remote URL. mcp-remote is a small open-source bridge that lets those clients reach AllMCP over HTTP. You only need this for clients that don’t support remote HTTP servers directly.

Get your API key All clients

---

Requirements

Node.js must be installed — mcp-remote runs through npx.

---

Config block

Wherever your client lets you define a local (command-based) MCP server, use:

mcp config

{
  "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

Write the header as X-API-Key:${ALLMCP_API_KEY} with no space. The value is read from env rather than written inline, which avoids a known issue where spaces in a --header argument get split.

---

Scoping to a specific user

Add user_id to the URL argument to keep each person’s connected providers separate:

"args": ["-y", "mcp-remote", "https://go.allmcp.co/mcp/?user_id=your-user-id", "--header", "X-API-Key:${ALLMCP_API_KEY}"]

---

Next steps

All clients Find your MCP client's setup guide.

Quickstart Connect AllMCP to your agent in under 2 minutes.