Overview
Features
MCP Resource Access
Explore OpenAPI specs via intuitive MCP URIs (e.g., openapi://info, openapi://paths/...); read-only access designed for MCP clients.
OpenAPI v3.0 & Swagger v2.0 Support
Loads both formats and automatically converts Swagger v2.0 to OpenAPI v3.0 on load.
Local & Remote Files
Supports loading specs from local file paths or HTTP/HTTPS URLs.
Token-Efficient
Minimizes token usage for LLMs by presenting structured views rather than entire documents.
Multiple Output Formats
Returns detailed views in JSON (default), YAML, or minified JSON via --output-format.
Dynamic Server Name
Server name in MCP clients reflects the info.title of the loaded spec.
Reference Transformation
Transforms internal $ref references (e.g., #/components/...) into clickable MCP URIs for easier navigation.
Who Is This For?
- MCP Clients:Explore large OpenAPI specs without loading entire documents into LLM context.
- Developers:Integrate token-efficient access into MCP-enabled workflows for API exploration and quick inspection.




