⚡️ mcpo

What is ⚡️ mcpo?

⚡️ mcpo is a proxy that takes any MCP server command and exposes it as an OpenAPI‑compatible HTTP server. It converts stdio or SSE‑based MCP tools into standard RESTful endpoints, making them usable by LLM agents and applications that expect OpenAPI servers—no custom protocol or glue code required.

How to use ⚡️ mcpo?

Run uvx mcpo --port 8000 --api-key "top-secret" -- your_mcp_server_command (or pip install mcpo then mcpo). For SSE servers use --server-type "sse". You can also start with a config file via mcpo --config /path/to/config.json, which follows the Claude Desktop format and serves each tool on a separate route (e.g. /memory). Docker is also supported: docker run -p 8000:8000 ghcr.io/open-webui/mcpo:main ....

Key features of ⚡️ mcpo

• Expose any MCP tool as an OpenAPI HTTP server instantly
• Works with both stdio and SSE MCP servers
• Auto‑generates interactive docs for every tool, no config needed
• Serve multiple tools via a single config file, each on its own route
• Run via uvx, pip, or Docker with zero installation hassle
• Adds security, stability, and scalability using trusted web standards

Use cases of ⚡️ mcpo

• Integrate MCP tools with LLM agents and apps that require OpenAPI endpoints
• Replace insecure, incompatible stdio MCP servers with standard HTTP APIs
• Expose multiple MCP tools behind one server with separate, documented routes
• Enable MCP tools to work with OpenAPI‑compatible SDKs, UIs, and automation

FAQ from ⚡️ mcpo

What does mcpo do that native MCP cannot?

Native MCP servers typically use raw stdio, which is insecure, incompatible with most tools, and lacks features like docs, auth, and error handling. mcpo wraps any MCP server as a standard OpenAPI HTTP server, adding security, stability, and auto‑generated interactive documentation.

What are the requirements to run mcpo?

Python 3.8+ is required. Using uv is optional but recommended for faster startup and packaging.

How can I serve multiple MCP tools at once?

Use a config file in the Claude Desktop format. Run mcpo --config /path/to/config.json. Each tool in the config gets its own route (e.g. /memory) and dedicated OpenAPI schema. Access the UI at http://localhost:8000/<tool>/docs.

Does mcpo support SSE‑based MCP servers?

Yes. Use the --server-type "sse" flag and provide the SSE endpoint URL instead of a command. Example: mcpo --port 8000 --api-key "top-secret" --server-type "sse" -- http://127.0.0.1:8001/sse.

How do I secure the mcpo server?

Use the --api-key flag to require an API key for all requests. The server runs over plain HTTP by default; for production, place it behind a reverse proxy with TLS.