rendis/mcp-openapi-proxy
Turn any OpenAPI 3.x spec into a fully functional MCP server — automatically. Zero codegen, one binary, stdio transport.
Platform-specific configuration:
{
"mcpServers": {
"mcp-openapi-proxy": {
"command": "npx",
"args": [
"-y",
"mcp-openapi-proxy"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
<div align="center">
Turn any OpenAPI 3.x spec into a fully functional MCP server — automatically.
Every REST API has an OpenAPI spec. Every AI agent speaks MCP.<br/> This bridge connects the two with zero code — point it at a spec, get MCP tools.
[](https://go.dev) [](LICENSE) [](https://modelcontextprotocol.io)
</div>
---
You have a REST API with 50+ endpoints and an OpenAPI spec that documents every one of them. You want an AI agent (Claude Code, Codex, Gemini CLI) to call your API through MCP. The standard approach: write one MCP tool definition per endpoint — input schemas, handlers, auth wiring — thousands of lines of boilerplate that breaks every time the API changes.
mcp-openapi-proxy eliminates that. One binary. One environment variable pointing to your spec. Every endpoint becomes an MCP tool at startup. No codegen, no generated files, no maintenance.
<p align="center"> </p>
flowchart LR
A["OpenAPI Spec<br/><small>YAML · JSON · URL</small>"] --> B["Spec Parser<br/><small>kin-openapi</small>"]
B --> C["Endpoints[]"]
C --> D["Tool Generator<br/><small>name + schema + handler</small>"]
D --> E["MCP Server<br/><small>stdio</small>"]
E <-->|"tool calls"| F["AI Agent<br/><small>Claude · Codex · Gemini</small>"]
style A fill:#24283b,stroke:#bb9af7,color:#bb9af7
style B fill:#24283b,stroke:#7dcfff,color:#7dcfff
style C fill:#24283b,stroke:#e0af68,color:#e0af68
style D fill:#24283b,stroke:#9ece6a,color:#9ece6a
style E fill:#24283b,stroke:#bb9af7,colLoading reviews...