MCP OpenAPI

What is MCP OpenAPI?

MCP OpenAPI parses an OpenAPI specification and dynamically generates the corresponding MCP server components. It is designed to accelerate adoption of the Model Context Protocol by automating server creation from existing API definitions.

How to use MCP OpenAPI?

Deploy the application as a sidecar alongside an existing service. Set the OPENAPI_SPEC_URL environment variable to point to your OpenAPI specification and optionally configure TRANSPORT, HOST, and PORT. The server will parse the spec and expose MCP-compatible tools.

Key features of MCP OpenAPI

• Parses OpenAPI specifications
• Dynamically generates MCP-compatible server code and tools
• Designed to streamline integration and deployment

Use cases of MCP OpenAPI

• Deploy as a sidecar to add MCP support to existing services
• Automate MCP server creation without manual implementation

FAQ from MCP OpenAPI

What problem does MCP OpenAPI solve?

It reduces the overhead of manually developing MCP servers by automatically translating an OpenAPI specification into the required MCP components.

How do I configure the server?

Set the OPENAPI_SPEC_URL environment variable to the URL of your OpenAPI specification. Optional variables include TRANSPORT (default streamable-http), HOST (default 127.0.0.1), and PORT (default 8000).

What transport does it use?

The default transport is streamable-http, as shown in the TRANSPORT environment variable default. No other transports are documented.

What is a typical deployment pattern?

The project recommends deploying it as a sidecar alongside an existing service, allowing the service to gain MCP compatibility without code changes.

Does the server require a database?

The architecture diagram shows that the underlying OpenAPI server may query a database, but MCP OpenAPI itself does not require one; it proxies requests to the existing API server.