mcpo

Why we included this project

MCP servers usually speak over raw stdio, which makes them awkward to plug into systems that expect plain REST APIs. mcpo fixes that by standing in front of a server and exposing its tools as an OpenAPI-compatible HTTP service with interactive docs generated automatically, regardless of whether the server runs over stdio, SSE, or streamable HTTP. That is convenient for teams wiring MCP-based tools into LLM agent pipelines, internal tooling, and web UIs that only speak HTTP. It also layers on production concerns like API key authentication, OAuth 2.1, serving behind a subpath, and hot-reloading a multi-tool config, so you get auth and operational controls without writing glue code. If you are tired of babysitting raw stdio sockets, this is a low-effort bridge that makes MCP servers behave like well-behaved web services.