MCPO — MCP-to-OpenAPI Proxy Server

Practical Notes

• README quick usage shows --port 8000 and an --api-key gate; docs UI is at /docs.
• README documents subpath hosting via --root-path and multi-tool configs via a Claude Desktop-style config.json (with optional hot reload).

How to Use MCPO Without Over-Exposing Tools

The moment you publish an OpenAPI surface, you should think like an API owner:

• Put MCPO behind auth (--api-key) and rotate keys.
• Prefer running it inside your private network; if public, add rate limits at a reverse proxy.
• Keep your MCP server command minimal and pinned to known versions.

A Useful Pattern: “Adapter Layer”

If your internal tools are MCP-based but your consumers are not, MCPO becomes a clean adapter:

• MCP tool stays local/agent-friendly.
• OpenAPI surface is stable for integrations and monitoring.

FAQ

Q: Is uv required? A: No. README shows uvx as recommended, but also documents pip install and Docker run.

Q: Can it proxy non-stdio MCP servers? A: Yes—README includes --server-type options like sse and streamable-http.

Q: How do I serve multiple tools? A: Use a config file in Claude Desktop format; README shows mcpo --config ... and --hot-reload.