MCP OpenAPI

This project aims to accelerate the adoption of the MCP protocol by simplifying server generation through automated tooling. It parses an OpenAPI specification and dynamically generates the corresponding MCP server components.

Key Features

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

Use Cases

One common use case is deploying this application as a sidecar alongside existing services. This enables seamless MCP support without requiring manual server implementation.

Why MCP OpenAPI Proxy?

By automating the translation from OpenAPI to MCP, this tool reduces the overhead of manual server development and promotes faster adoption of the MCP protocol within modern service architectures.

Workflow

sequenceDiagram
    actor user as User
    actor agent as Agent
    participant ingress as Ingress
    participant mcp_proxy as MCP Proxy
    participant openapi_server as OpenAPI Server
    participant db as Database

    user->>ingress: Request for OpenAPI resource
    ingress->>openapi_server: Forward request
    openapi_server->>db: Query database
    db-->>openapi_server: Database response
    openapi_server-->> user: OpenAPI Server response

    Note over user,db: LLM interaction

    user->>agent: Send a prompt
    agent->>ingress: Request for MCP tool
    ingress->>mcp_proxy: Forward request
    mcp_proxy->>openapi_server: Forward request
    openapi_server->>db: Query database
    db-->>openapi_server: Database response
    openapi_server-->>mcp_proxy: OpenAPI Server response
    mcp_proxy-->>agent: MCP server response
    agent-->>user: Prompt response

Environment variables

Name	Default	Description
OPENAPI_SPEC_URL		URL of the Open API specification.
TRANSPORT	streamable-http	Transport type to use for communication with the MCP server.
HOST	127.0.0.1	Hostname or IP address to bind the server to.
PORT	8000	Port number to listen on.