Practical overview
When it fits
Use Mcpo when an existing MCP tool needs to be made available to an agent, SDK, or application that consumes OpenAPI-compatible HTTP services.
Who it is for
- Developers connecting MCP server tools to agents or applications that accept OpenAPI-compatible HTTP services.
- Teams operating MCP tools who want a generated HTTP interface and per-tool API documentation.
Documented uses
- Expose an MCP server command as a RESTful OpenAPI service.
- Connect MCP tools to clients that expect OpenAPI rather than MCP.
- Serve multiple configured MCP tools on separate routes.
- Use documented SSE or Streamable HTTP MCP endpoints as inputs to the proxy.
Requirements & limits
- The project requires Python 3.8 or later; uv is optional and recommended in the README.
- The proxy accepts a server command, or documented SSE and Streamable HTTP endpoints; the MCP tool itself must be provided separately.
- The README documents API-key protection and OAuth 2.1 for Streamable HTTP server types.
- A configuration file can define multiple tools, separate routes, and optional hot reload.
- The repository identifies the project as MIT-licensed open-source software.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Expose a local MCP server over OpenAPI
Start Mcpo with an MCP server command and access its generated OpenAPI documentation.
Before you start
- Python 3.8 or later.
- An MCP server command available in the environment.
- uv, or Python with pip.
Steps
Start Mcpo with uv using
uvx mcpo --port 8000 --api-key "top-secret" -- your_mcp_server_command, or install with the command below and run the documentedmcpocommand.pip install mcpoReplace
your_mcp_server_commandwith the command for the MCP server you want to expose.Open
http://localhost:8000/docsto view the generated interactive documentation.
Expected outcome
The MCP server’s tools are exposed through an OpenAPI-compatible HTTP service, with interactive documentation at the local `/docs` path.
Guide limitations
- This recipe covers the documented local command-based setup; it does not establish deployment configuration or integration with a particular client.
- The documented command includes an API key; protect the key and configure access appropriately for your environment.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 9 October 2026
- Original website title
- open-webui/mcpo · Official homepage title · retained in its source language

