mcp-openapi-schema-explorer and openapi-to-mcp
One tool provides token-efficient access to OpenAPI/Swagger specs for client-side exploration using MCP Resource Templates, while the other generates individual MCP servers for each endpoint within an OpenAPI/Swagger API, enabling AI clients to interact with REST APIs via Streamable HTTP.
About mcp-openapi-schema-explorer
kadykov/mcp-openapi-schema-explorer
MCP server providing token-efficient access to OpenAPI/Swagger specs via MCP Resource Templates for client-side exploration.
Implements parameterized resource templates (e.g., `openapi://paths/{path}/{method}`) that enable dynamic, on-demand access to OpenAPI/Swagger specs without pre-enumerating endpoints, avoiding context bloat. Supports both local files and remote HTTP/HTTPS URLs, with automatic Swagger v2.0-to-OpenAPI v3.0 conversion. Runs via stdio transport and integrates with MCP clients like Claude Desktop, Cline, and Windsurf through configurable execution methods (npx, Docker, or node).
About openapi-to-mcp
EvilFreelancer/openapi-to-mcp
Turns any OpenAPI/Swagger API into an MCP server. One MCP tool per endpoint, Streamable HTTP - for AI clients calling your REST API.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work