Overview
Features
Dynamic loading of OpenAPI specs
Load OpenAPI specs from local files or remote HTTP/HTTPS URLs to generate MCP servers on the fly.
OpenAPI Overlays support
Apply overlays to OpenAPI specs via local files or URLs to modify endpoints and attributes before generating tools.
Customizable operation-to-tool mapping
Configure how each OpenAPI operation becomes an MCP tool, enabling custom naming and behavior.
Advanced operation filtering
Filter exposed operations with glob patterns for operationId and URL paths to control exposure.
Comprehensive parameter handling
Preserve parameter formats and capture location metadata to ensure correct parameter extraction and transmission.
API authentication handling
Support API authentication and security schemes to secure connected endpoints.
OpenAPI metadata-driven configuration
Use OpenAPI metadata (title, version, description) to configure MCP server and tool descriptions.
Hierarchical description fallbacks
Fallback from operation description to summary to path summary for robust tool descriptions.
Who Is This For?
- AI developers:Create MCP servers from OpenAPI specs to enable AI assistants to access APIs.
- Claude Desktop users:Configure and run MCP servers within Claude Desktop to access API tools.
- Cursor users:Run MCP servers in Cursor during development to expose API tools.
- Vercel SDK integrators:Integrate MCP tools into JS/TS apps via Vercel AI SDK.
- Platform teams:Manage tokens, users, analytics and API lifecycles for organizational APIs.




