#1414th of 14 in Gateways
mcpo
Exposes any MCP server as an OpenAPI HTTP endpoint
- Stars
- 4.4k
- License
- MIT
- Last commit
- Feb 2026
- Last release
- Feb 2026
Overview
mcpo wraps an MCP server command, SSE or Streamable HTTP endpoint and exposes its tools as an OpenAPI REST server on port 8000 with generated docs, so HTTP clients such as Open WebUI can call MCP tools. A Claude Desktop-style config serves several servers under separate routes with hot reload; OAuth 2.1 dynamic client registration handles protected upstreams. Runs via uvx, pip or Docker.
Who it is for: Open WebUI users exposing MCP tools over HTTP
Strengths
- One command turns any MCP server into an OpenAPI server with /docs
- stdio, SSE and Streamable HTTP upstreams; OAuth 2.1 with dynamic registration
- Config file in Claude Desktop format with hot reload
- Docker image and --root-path for reverse proxies
Weaknesses
- Last commit 2026-02-27
- Single shared API key; no users or RBAC
- Converts to OpenAPI only; does not aggregate servers into one MCP endpoint
- Python 3.8+ process per deployment; no clustering
What it needs
- no GPU
- Docker
- Needs MCP servers to proxy
- port 8000
Also in Gateways
See all 14| Rank | Project | Score |
|---|---|---|
| 1 | OmniRouteOpenAI-compatible gateway that routes requests across hundreds of AI providers | 86 out of 100 |
| 2 | LiteLLMOpenAI-format gateway and Python SDK for calling 100+ LLM providers | 84 out of 100 |
| 3 | freellmapiOpenAI-compatible router that fails over across free LLM provider tiers | 76 out of 100 |
| #4 | ContextForge MCP GatewayRegistry and proxy federating MCP, A2A, REST and gRPC behind one endpoint | 68 out of 100 |
| #5 | HigressEnvoy-based API gateway with LLM proxy plugins and MCP server hosting | 61 out of 100 |