Openapi
Register an OpenAPI or Swagger spec as MCP tools so agents can call REST endpoints without you writing one tool per route.
Overview
io.github.Docat0209/openapi is a Build-phase MCP server that turns OpenAPI/Swagger specs into MCP tools without writing adapter code.
What is this MCP server?
- Converts any OpenAPI/Swagger document into MCP tools with zero code
- npm package mcp-openapi v0.2.3 with stdio transport
- Works with specs you already publish for partners or internal clients
- Speeds up agent access to Stripe-like REST APIs, internal microservices, and generated SDK backends
- Server version 0.2.3
- npm package identifier mcp-openapi
Community signal: 3 GitHub stars.
What problem does it solve?
Your agent needs to hit REST APIs described by OpenAPI, but manually mirroring every path as an MCP tool does not scale.
Who is it for?
Solo builders with OpenAPI-described APIs or third-party REST specs who want fast MCP coverage for Claude Code or Cursor.
Skip if: GraphQL-only stacks, undocumented legacy HTTP, or workflows requiring heavily customized tool semantics per endpoint.
What do I get? / Deliverables
Once registered, your agent can call REST operations as MCP tools generated from your OpenAPI document.
- MCP tools mapped from OpenAPI paths and operations
- Agent-ready REST invocation without per-route MCP coding
- Version 0.2.3 server registration via npm stdio
Recommended MCP Servers
Journey fit
REST and OpenAPI specs are wired into the product and agent stack during the build phase when backends and third-party services are connected. OpenAPI-to-MCP is classic integrations work: translating existing HTTP contracts into agent-accessible tools.
How it compares
OpenAPI-to-MCP auto-bridge, not a REST framework and not a single-purpose integration skill.
Common Questions / FAQ
Who is io.github.Docat0209/openapi for?
Developers shipping or consuming REST APIs documented with OpenAPI or Swagger who want MCP tool coverage without manual wrappers.
When should I use io.github.Docat0209/openapi?
During build when connecting agents to your backend, webhooks admin, or vendor REST APIs that already have a machine-readable spec.
How do I add io.github.Docat0209/openapi to my agent?
Install npm package mcp-openapi v0.2.3, add a stdio MCP server block in your agent config, and supply the OpenAPI spec location and credentials per project docs.