mcp-openapi-schema-explorer and openmcp
These are **complements**: the schema explorer provides efficient browsing and understanding of OpenAPI specifications, while the server generator consumes those specifications to create functional MCP servers, addressing different stages of the OpenAPI-to-MCP workflow.
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 openmcp
getdatanaut/openmcp
Turn any openapi file into an mcp server, with just the tools you need.
Supports both OpenAPI-to-MCP conversion and stdio-based MCP server composition, allowing selective tool exposure through an `openmcp.json` config file. Implements stdio and SSE transports with direct integration into major chat clients (Cursor, Claude) via automated client configuration. Handles authentication management across multiple servers and enables mixing heterogeneous MCP sources—OpenAPI specs, stdio servers, and others—into a single unified MCP endpoint.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work