Bridge for MCP servers

Claude Desktop speaks stdio; your server speaks HTTP. mcp-bridge translates between the two — a single Go binary with no runtime dependencies. Designed for stateless JSON mode and serverless backends like Azure Functions and AWS Lambda.

Claude Code uses HTTP transport natively, but has known auth and timeout issues; the bridge works reliably for both clients.

Install

If you have Go installed:

go install github.com/markwharton/mcp-bridge@latest

Or download a binary for your platform from the releases page. Roughly 5 MB, no runtime dependencies.

What it does

• Bridges stdio ↔ HTTP Translates Model Context Protocol traffic between stdio-only clients (Claude Desktop) and HTTP-based servers.
• Single Go binary Roughly 5 MB, zero runtime dependencies. Run it directly — no Python, Node, or container overhead.
• Stateless JSON mode Designed for serverless backends like Azure Functions and AWS Lambda. The bridge is the persistent piece; your server can be ephemeral.
• Works with both clients Claude Desktop needs the bridge (stdio only). Claude Code uses HTTP natively but has auth and timeout edges — the bridge sidesteps them.

Docs

• Notes from the workshop Release notes — what changed and what to do with it.
• Source github.com/markwharton/mcp-bridge — MIT licensed.