mcpo and mcp-proxy
These are competitors offering different architectural approaches to the same problem: converting MCP servers into HTTP interfaces, with A focusing on OpenAPI standardization while B emphasizes multi-server aggregation capabilities.
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.
About mcp-proxy
tbxark/mcp-proxy
An MCP proxy server that aggregates and serves multiple MCP resource servers through a single HTTP server.
Supports multiple MCP client transport types (stdio, SSE, streamable-http) and exposes aggregated tools, prompts, and resources via Server-Sent Events or streamable HTTP endpoints. Built in Go with Docker support for launching Node.js and Python-based MCP servers via `npx` and `uvx`. Includes a web-based Claude configuration converter for simplified client setup.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work