mcp-proxy and mcpo
These are complements—mcp-proxy handles transport bridging between HTTP and stdio protocols, while mcpo wraps MCP servers with an OpenAPI interface, so they solve different layers of proxy needs and could be used together in a stack.
About mcp-proxy
sparfenyuk/mcp-proxy
A bridge between Streamable HTTP and stdio MCP transports
Enables bidirectional transport bridging with support for both SSE and Streamable HTTP protocols, allowing stdio-based MCP clients (like Claude Desktop) to connect to remote HTTP servers and vice versa. Implements protocol translation through two modes: stdio-to-HTTP for remote server access via local stdio interface, and HTTP-to-stdio for exposing local servers over SSE with configurable CORS, OAuth2 authentication, and environment variable passing. Built in Python with Docker support for containerized deployment.
About mcpo
open-webui/mcpo
A simple, secure MCP-to-OpenAPI proxy server
Bridges stdio-based MCP servers to HTTP via auto-generated OpenAPI schemas, supporting multiple transport types (stdio, SSE, Streamable HTTP) with optional OAuth 2.1 authentication. Enables serving multiple MCP tools simultaneously through a single config file with hot-reload capability, making them compatible with standard REST clients and LLM agent frameworks without custom integration code.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work