Mcp Openapi
Auto-expose every operation in an OpenAPI or Swagger spec as MCP tools so agents can call your REST API with SSRF protections baked in.
Overview
mcp-openapi is a MCP server for the Build phase that materializes OpenAPI/Swagger operations as SSRF-guarded MCP tools for AI agents.
What is this MCP server?
- Each OpenAPI operation becomes its own MCP tool dynamically
- SSRF guarding on outbound calls from generated tools
- Works with OpenAPI and Swagger spec inputs
- stdio MCP via @infoinlet/mcp-openapi v0.1.1 on npm
- Generic bridge for any documented HTTP API—not a single-vendor connector
- Package @infoinlet/mcp-openapi at version 0.1.1
- Design: each OpenAPI operation maps to one MCP tool
- Marketplace source subfolder services/mcp-openapi
What problem does it solve?
You have a large OpenAPI spec but manually wrapping dozens of endpoints as MCP tools does not scale for one-person shipping.
Who is it for?
Builders with existing OpenAPI-documented APIs who want fast agent access without maintaining a custom MCP server per service.
Skip if: Undocumented RPC-only systems, or APIs where you refuse any automated outbound HTTP from the agent environment.
What do I get? / Deliverables
You point the server at a spec and register stdio MCP once; the agent gains callable tools per operation with guarded HTTP behavior.
- One MCP tool per OpenAPI operation from your spec
- SSRF-guarded outbound HTTP from agent-invoked tools
- Reusable stdio integration without per-endpoint MCP coding
Recommended MCP Servers
Journey fit
Integration work during build is when you wire third-party or your own HTTP APIs into agent workflows—OpenAPI-driven tools avoid hand-writing each endpoint wrapper. Turning specs into guarded MCP tools is the core integrations task for solo builders shipping API-backed products.
How it compares
Spec-driven generic REST MCP generator with SSRF guards, not a single-service connector like Stripe-or-Notion-specific MCP.
Common Questions / FAQ
Who is mcp-openapi for?
Indie devs and agent builders who already publish OpenAPI/Swagger and want Claude Code or Cursor to call those endpoints as MCP tools.
When should I use mcp-openapi?
Use it during build integrations when wiring a documented HTTP API into agent workflows and you want one tool per operation without hand-coded wrappers.
How do I add mcp-openapi to my agent?
Install @infoinlet/mcp-openapi (v0.1.1), configure the stdio MCP entry with path or URL to your OpenAPI/Swagger spec plus base URL and auth env vars as required by the package README.