@minamorl/openapi-mcp-bridge
Provides tools to dynamically bridge any OpenAPI 3.x specification to MCP tools, enabling interaction with APIs that expose a Swagger/OpenAPI spec.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@minamorl/openapi-mcp-bridgefind all available pets from the pet store API"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@minamorl/openapi-mcp-bridge
Runtime MCP server that dynamically bridges any OpenAPI 3.x spec to MCP tools.
No code generation. No build step. One command.
Quick Start
npx @minamorl/openapi-mcp-bridge --spec https://petstore3.swagger.io/api/v3/openapi.jsonRelated MCP server: OpenAPI MCP Server
Why not codegen?
Existing tools (openapi-mcp-generator, etc.) generate static TypeScript files from your OpenAPI spec. Every time the API changes, you regenerate, rebuild, redeploy.
openapi-mcp-bridge takes a different approach: runtime bridging. It reads the OpenAPI spec at startup and dynamically creates MCP tools. Update the spec → restart the server. That's it.
Codegen tools | openapi-mcp-bridge | |
API spec changes | Regenerate → rebuild → restart | Restart only |
Setup | npm install → generate → configure → build → start | npx + 1 flag |
OAuth2 | "Put token in .env" | Built-in auth flows |
Transport | stdio only | stdio + Streamable HTTP (planned) |
Usage
CLI
# From URL
openapi-mcp-bridge --spec https://api.example.com/openapi.json
# From local file (JSON or YAML)
openapi-mcp-bridge --spec ./api.yaml
# With auth
openapi-mcp-bridge --spec ./api.yaml --auth-type bearer --auth-token $TOKEN
# With custom base URL
openapi-mcp-bridge --spec ./api.yaml --base-url http://localhost:3000
# With custom headers
openapi-mcp-bridge --spec ./api.yaml -H "X-Custom: value"Claude Desktop / Cursor config
{
"mcpServers": {
"my-api": {
"command": "npx",
"args": ["@minamorl/openapi-mcp-bridge", "--spec", "https://api.example.com/openapi.json"]
}
}
}Programmatic API
import { parseSpec, createBridgeServer, startStdioServer } from "@minamorl/openapi-mcp-bridge";
const doc = await parseSpec("./api.yaml");
const server = await createBridgeServer({ doc, baseUrl: "http://localhost:3000" });
await startStdioServer(server);How It Works
OpenAPI 3.x spec (JSON/YAML/URL)
↓ Parse + resolve $refs
Tool definitions (name, schema, method, path)
↓ Register as MCP tools
MCP Server (stdio)
↓ On tool call
HTTP request to actual API
↓
Response back to LLMParser reads and validates the OpenAPI spec, resolving all
$refreferencesMapper converts each operation to an MCP tool with proper input schemas
Server registers tools and handles MCP protocol
Executor translates tool calls into HTTP requests
Auth
# Bearer token
--auth-type bearer --auth-token YOUR_TOKEN
# API key
--auth-type api-key --auth-token YOUR_KEY --api-key-header X-API-Key
# Basic auth (token = base64 of user:pass)
--auth-type basic --auth-token BASE64_CREDENTIALSLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/minamorl/openapi-mcp-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server