Bridge that connects Claude Desktop to remote MCP servers via HTTP POST
npm install @airbodev/mcp-remote-bridgeA lightweight bridge that connects Claude Desktop to remote MCP (Model Context Protocol) servers via HTTP POST.
Claude Desktop communicates with MCP servers via stdio (standard input/output). If your MCP server is a remote HTTP API, this bridge translates between the two protocols.
```
Claude Desktop (stdio) ←→ mcp-remote-bridge ←→ Your Server (HTTP POST)
No installation required! Just configure Claude Desktop to use npx.
Edit your Claude Desktop config file:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json
- Windows:
`json`
{
"mcpServers": {
"my-server": {
"command": "npx",
"args": ["-y", "@airbodev/mcp-remote-bridge"],
"env": {
"MCP_SERVER_URL": "https://your-server.com/mcp",
"MCP_AUTH_TOKEN": "your-token-here"
}
}
}
}
Then restart Claude Desktop.
| Variable | Required | Description |
| ---------------- | -------- | ------------------------------------------------------------- |
| MCP_SERVER_URL | Yes | The URL of your MCP server endpoint |MCP_AUTH_TOKEN
| | Yes | Authentication token (sent as Authorization: Token ) |
1. Claude Desktop starts the bridge as a child process
2. Claude sends JSON-RPC messages via stdin
3. The bridge forwards them as HTTP POST requests to your server
4. Your server responds with JSON-RPC
5. The bridge sends the response back to Claude via stdout
Your MCP server must:
- Accept POST requests with Content-Type: application/jsonAuthorization: Token
- Accept header
- Respond with valid JSON-RPC 2.0 messages
Make sure you set the MCP_SERVER_URL in the env section of your config.
Make sure you set the MCP_AUTH_TOKEN in the env` section of your config.
1. Verify your server URL is correct and accessible
2. Check if your token is valid
3. Ensure your server is running
4. Try restarting Claude Desktop
- Node.js 18 or higher
MIT