Openapi MCP Server

Connect Openapi to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Load OpenAPI 2.x/3.x specs and expose generic tools to discover and call multiple APIs. The openapi mcp server is what makes that connection.

What the server does

Connect AI clients to OpenAPI APIs quickly, with one MCP server, direct CLI access, and built-in auth support.

openapi-dynamic-mcp lets MCP clients and shell users work with OpenAPI APIs without writing custom glue code for each service. Point it at one or more OpenAPI specs, then list APIs, inspect endpoints, authenticate, and make requests through a consistent interface.

• Get from spec to usable tools fast — start from a YAML config and immediately browse endpoints or call them from MCP or the CLI
• Authenticate the way your API expects — supports API keys, bearer/basic auth, and OAuth2 client credentials, password, device code, and auth code with PKCE
• Avoid repeated sign-in work — store tokens once and reuse them later
• Handle interactive OAuth cleanly — device-code and browser-based auth return instructions an agent can present to the user
• Keep responses focused — project large outputs with JSONPath selectors
• Inspect before you send — use dry runs to preview request shape without network I/O

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• OPENAPI_DYNAMIC_MCP_AUTH_FILE — __API_KEY
• list_apis — List configured APIs
• list_api_endpoints — Search or paginate endpoints in one API
• get_api_endpoint — Inspect endpoint metadata, parameters, responses, and security
• get_api_schema — Return a schema object or JSON Pointer target from the spec
• make_endpoint_request — Preview or execute an endpoint request
• Cursor — The Cursor tool exposed by this server
• OAuth2 — The OAuth2 tool exposed by this server

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: PET_API_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js 20+

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Openapi's toolset — OPENAPI_DYNAMIC_MCP_AUTH_FILE, list_apis, list_api_endpoints and 5 more — is a fair guide to whether it matches your workflow. It is maintained by mayorandrew; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.