mcp-openapi
The @reapi/mcp-openapi server helps developers integrate multiple OpenAPI specifications into LLM-powered IDEs. It acts as a bridge between API definitions and development tools to enhance productivity and enable intelligent features like code completion.
What is the purpose of the @reapi/mcp-openapi server?
The @reapi/mcp-openapi server is designed to load and serve multiple OpenAPI specifications, enabling LLM-powered IDE integrations and providing a bridge between OpenAPI specifications and development tools.
How does the server handle multiple OpenAPI specifications?
The server loads multiple OpenAPI specifications from a specified directory, processes and dereferences them for complete context, and maintains a catalog of all API operations and schemas.
What are the benefits of using project-specific configuration in Cursor?
Project-specific configuration allows you to maintain different sets of specifications for different projects, manage LLM context limits, and keep the configuration portable and easier to share across team members.
How can I refresh the API catalog in Cursor?
You can refresh the API catalog by opening Cursor's chat panel and typing prompts like 'Please refresh the API catalog' or 'Reload the OpenAPI specifications'.
What formats are supported for OpenAPI specifications?
The server supports OpenAPI 3.x specifications in both JSON and YAML formats, with files having .json, .yaml, or .yml extensions.