MCP.so
Sign In

mcpo MCP Server

@MaxLammers-XYZ

Basic information

Category

Other

License

MIT license

Transports

stdio

Author

MaxLammers-XYZ

About mcpo MCP Server

Expose any MCP tool as an OpenAPI-compatible HTTP server—instantly. CA: GRgoNjoiDz5oPAua3TGy1Qqy7ViWBwF1LNoEds27bonk

mcpo MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "MCPO": {
      "command": "uvx",
      "args": [
        "mcpo",
        "--port",
        "8000",
        "--api-key",
        "top-secret",
        "--",
        "your_mcp_server_command"
      ]
    }
  }
}

mcpo MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is ⚡️ mcpo?

⚡️ mcpo is a proxy that takes any MCP server command and exposes it as an OpenAPI-compatible HTTP server instantly. It makes MCP tools accessible via standard RESTful OpenAPI, so they work with LLM agents and apps that expect OpenAPI servers.

How to use ⚡️ mcpo?

Install via pip install mcpo or use uvx mcpo with Docker. Run with flags like --port 8000 --api-key "top-secret" -- your_mcp_server_command. For SSE MCP servers, add --server-type "sse" and the SSE URL. Multiple tools can be served via a config file following the Claude Desktop format; each tool gets its own route and OpenAPI schema.

Key features of ⚡️ mcpo

  • Auto‑generates OpenAPI schema and interactive docs for every tool
  • Adds security, stability, and scalability using trusted web standards
  • Works instantly with OpenAPI tools, SDKs, and UIs
  • Supports both stdio and SSE MCP servers
  • Serve multiple MCP tools from a single config file
  • Pure HTTP—no custom protocol, no glue code

Use cases of ⚡️ mcpo

  • Expose any MCP tool as a RESTful API for LLM agents
  • Integrate MCP tools with OpenAPI‑compatible platforms and SDKs
  • Secure MCP tools with an API key and standard HTTP auth
  • Host multiple MCP tools behind one endpoint with separate routes

Frequently asked questions

1

What does mcpo do?

It proxies an MCP server command to an OpenAPI‑compatible HTTP server, making the MCP tools accessible via standard RESTful endpoints with auto‑generated docs.

2

Why use mcpo instead of native MCP?

Native MCP runs over raw stdio, which is inherently insecure, incompatible with most tools, and missing standard features like docs and auth. mcpo adds HTTP, security, stability, and automatic OpenAPI documentation.

3

How do I secure my tools with mcpo?

Use the `--api-key` flag when starting mcpo, e.g., `mcpo --api-key "top-secret" -- your_server_command`.

4

Can I serve multiple MCP tools at once?

Yes. Provide a config file (Claude Desktop format) with the `--config` flag. Each tool gets its own route (e.g., `/memory`, `/time`) and dedicated OpenAPI schema and docs.

5

What are the runtime requirements?

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

Comments

More Other MCP servers