Token-efficient access to local or remote OpenAPI/Swagger specs via MCP Resources.
Documentation
MCP OpenAPI Schema Explorer# Project Goal
The primary goal of this project is to allow MCP clients (like Cline or Claude Desktop) to explore the structure and details of large OpenAPI specifications without needing to load the entire file into an LLM's context window. It achieves this by exposing parts of the specification through MCP Resources, which are well-suited for read-only data exploration.
Installation
For the recommended usage methods (npx and Docker), no separate installation step is required. Your MCP client will download the package or pull the Docker image automatically based on the configuration you provide.
Features
MCP Resource Access: Explore OpenAPI specs via intuitive URIs.
OpenAPI v3.0 & Swagger v2.0 Support: Loads both formats, automatically converting v2.0 to v3.0.
Local & Remote Files: Load specs from local file paths or HTTP/HTTPS URLs.
Token-Efficient: Designed to minimize token usage for LLMs by providing structured access.
Multiple Output Formats: Get detailed views in JSON, YAML, or minified JSON.
Contributing
Contributions are welcome! Please see the CONTRIBUTING.md file for guidelines on setting up the development environment, running tests, and submitting changes.