mcp-openapi-schema-explorer and mcp-openapi
These tools are ecosystem siblings: one provides a server for general OpenAPI specification access, while the other offers a specialized server designed for token-efficient client-side exploration of those OpenAPI/Swagger specs using MCP Resource Templates.
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 mcp-openapi
ReAPI-com/mcp-openapi
OpenAPI specification MCP server.
Loads and dereferences multiple OpenAPI specifications from a directory, exposing API operations and schemas through MCP tools for LLM-powered IDE integration in Cursor. Implements a catalog-based architecture with search and lookup capabilities across specifications, using custom `x-spec-id` fields to disambiguate overlapping endpoints and schemas between services. Integrates directly into Cursor via `.cursor/mcp.json` configuration and provides tools for dynamic catalog refresh and semantic operation/schema discovery.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work