What it does
At startup, the server reads an OpenAPI 3 spec and builds one MCP tool per operation in memory, with no code generation or per-endpoint files. Each operationId becomes the tool name, the summary becomes its description, and parameters and request body form the input schema. A tool call makes the real HTTP request and returns the response body, cut at 50,000 characters. The whole server is a single file with no dependencies.
It suits cases where an AI client such as Claude or Cursor should call an API's endpoints. For small public APIs that only publish HTML documentation, the publisher suggests writing a small spec by hand and running it the same way. Large APIs can have hundreds of endpoints, so a regex filter can limit the exposed tools to the useful ones.
Running it requires Node.js. In local mode the client launches the server on the same machine; in HTTP mode it connects to a URL, which also allows self-hosting. Credentials go in an environment variable, and the spec's securitySchemes decide where they are sent. OAuth2 client credentials and refresh tokens are supported, extra headers can be added, and HTTP mode can require a bearer token.
Limitations and requirements
OpenAPI 3 only; Swagger 2.0 specs must be converted first. YAML specs need an additional npm package. JSON request bodies only, with no file uploads. There is no interactive OAuth login, and only one security scheme is used per API; per-endpoint security overrides are not applied. HTTP mode speaks plain HTTP, has no streaming, batch requests or OAuth for connecting clients, and some remote clients may require these. Rotated refresh tokens are kept in memory only and are lost on restart. When deployed remotely, all users share the server's IP for upstream rate limits, and without MCP_AUTH_TOKEN anyone with the URL can use the API key.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.Asthanaji05/openapi-mcp
Turn any OpenAPI 3 spec into a working MCP server. One file, local (stdio) or remote (HTTP).
v0.1.1As shown on registry.modelcontextprotocol.io when we last read it