MCP OpenAPI Schema Explorer is a TypeScript server that provides token-efficient access to OpenAPI (v3.0) and Swagger (v2.0) specifications. Developed by Aleksandr Kadykov, it transforms large API specifications into navigable MCP resources with URI-based references, allowing AI assistants to explore API structures without loading entire specs into their context windows. The server loads specs from local files or remote URLs, automatically converts Swagger v2.0 to OpenAPI v3.0, and returns information in configurable formats (JSON, YAML, or minified JSON), making it particularly valuable for working with complex APIs that would otherwise consume excessive tokens.
まだレビューはありません. 最初のレビューを投稿しましょう！
会話に参加するにはサインインしてください
Highlight AIAccesses top-level fields of the OpenAPI document (e.g., info, servers, tags) or lists the contents of paths or components. The specific available fields depend on the loaded specification. Example: `openapi://info`.
Lists the available HTTP methods (operations) for a specific API path. Parameter: `{path}` - The API path string. Must be URL-encoded (e.g., `/users/{id}` becomes `users%2F%7Bid%7D`). Example: `openapi://paths/users%2F%7Bid%7D`.
Gets the detailed specification for one or more operations (HTTP methods) on a specific API path. Parameters: `{path}` - The API path string (Must be URL-encoded), `{method*}` - One or more HTTP methods (e.g., `get`, `post`, `get,post`). Example: `openapi://paths/users%2F%7Bid%7D/get`.
Lists the names of all defined components of a specific type (e.g., schemas, responses, parameters). The specific available types depend on the loaded specification. Example: `openapi://components/schemas`.
Gets the detailed specification for one or more named components of a specific type. Parameters: `{type}` - The component type, `{name*}` - One or more component names (e.g., `User`, `Order`, `User,Order`). Example: `openapi://components/schemas/User`.
