mcp-proxy
Bridge that exposes stdio MCP servers over HTTP/SSE, or vice versa. Run a local server remotely, or connect to a remote server as if it were local.
mcp-proxy solves the transport mismatch problem in MCP. Most local MCP servers use stdio transport, but some clients (especially cloud-hosted ones) can only speak HTTP or SSE. mcp-proxy wraps either side: point it at a stdio server and it exposes an HTTP endpoint; point it at a remote HTTP server and it exposes a stdio interface for clients that expect one. It handles the session management, reconnection logic, and request correlation that you would otherwise have to write yourself. For anyone bridging between self-hosted local tooling and a cloud Claude/ChatGPT client, mcp-proxy is usually in the path.
Similar Tools
MCP Inspector
Visual testing tool for Model Context Protocol servers. Like Postman for MCP - call tools, browse resources, and view real-time logs in a browser UI. Zero install via npx.
MCP CLI
Lightweight CLI for discovering and calling MCP servers. Dynamic tool discovery reduces token consumption from 47K to 400 tokens. Three subcommands: info, grep, call.
MCP Hub
Centralized manager for MCP servers. Connect once to localhost:37373 and access all your servers through a single endpoint. REST API, web UI, and VS Code config compatible.
Smithery
Registry and hosting platform for MCP servers. 6,000+ servers indexed. One-command install and configuration via CLI. Supports local and hosted deployments.
Get started with mcp-proxy
Bridge that exposes stdio MCP servers over HTTP/SSE, or vice versa. Run a local server remotely, or connect to a remote server as if it were local.
Try mcp-proxyGet weekly tool reviews
Honest takes on AI dev tools, frameworks, and infrastructure - delivered to your inbox.
Subscribe FreeMore MCP Tools Tools
MCP Inspector
Visual testing tool for Model Context Protocol servers. Like Postman for MCP - call tools, browse resources, and view real-time logs in a browser UI. Zero install via npx.
MCP CLI
Lightweight CLI for discovering and calling MCP servers. Dynamic tool discovery reduces token consumption from 47K to 400 tokens. Three subcommands: info, grep, call.
MCP Hub
Centralized manager for MCP servers. Connect once to localhost:37373 and access all your servers through a single endpoint. REST API, web UI, and VS Code config compatible.
Related Guides
Claude Code Setup Guide
Configure Claude Code for maximum productivity -- CLAUDE.md, sub-agents, MCP servers, and autonomous workflows.
AI AgentsMCP Servers Explained
What MCP servers are, how they work, and how to build your own in 5 minutes.
AI AgentsClaude Code Complete Course
A complete, citation-backed Claude Code course with setup, prompting systems, MCP, CI, security, cost controls, and capstone workflows.
ai-developmentRelated Posts

Arcade AI Agent Authorization: A Developer Guide
Arcade just raised $60M to become the secure action layer for production AI agents. Here is what their MCP runtime actua...

Agent Identity Is the Missing Security Layer for AI Workflows
The Linux Foundation's Agent Name Service proposal points at a real gap in AI agent infrastructure: agents need verifiab...

GitHub Copilot Agent Finder: What ARD Means for Third-Party AI Tools in 2026
GitHub's Agent Finder discovers and invokes Claude, Codex, MCP servers, and skills automatically. Here is how the new AR...

MCP Goes Stateless: The 2026-07-28 Migration Guide
The MCP 2026-07-28 release candidate drops sessions entirely. Here is what changes, what breaks, and how to migrate your...

Zero-Touch OAuth Is the MCP Feature Enterprises Were Waiting For
MCP's new enterprise-managed authorization flow is not just less login friction. It moves agent tool access into identit...

Zero-Touch OAuth for MCP: Enterprise Auth Gets Practical
MCP's new Enterprise-Managed Authorization removes per-user OAuth friction. Anthropic, Okta, Figma, and Linear ship cent...
