Overview: @reapi/mcp-openapi
Title
@reapi/mcp-openapi β A Model Context Protocol (MCP) server for serving OpenAPI specifications to LLM-powered IDEs
How to Use
- Installation: Run via
npx
in your project or globally.
- Configuration:
- Project-specific: Create
.cursor/mcp.json
with OpenAPI specs directory.
- Global: Configure
~/.cursor/mcp.json
for all projects.
- Enable in Cursor IDE:
- Enable the server in Cursor Settings > MCP.
- Refresh the API catalog via chat prompts (e.g., "Reload OpenAPI specs").
Key Features
- Multi-Spec Support: Loads and serves multiple OpenAPI specs from a directory.
- MCP Integration: Bridges OpenAPI specs with LLM-powered tools (e.g., Cursor IDE).
- Dereferenced Schemas: Ensures complete API context for LLMs.
- Catalog Management: Maintains a searchable catalog of APIs, operations, and schemas.
- Spec ID Customization: Resolves conflicts via
x-spec-id
in OpenAPI files.
Use Cases
- LLM-Powered Development:
- Enables AI-assisted code completion, API integration, and snippet generation in IDEs.
- API Exploration:
- Query available APIs, operations, and schemas via natural language (e.g., "Show all POST endpoints").
- Testing & Validation:
- Use with ReAPIβs no-code testing module for CI/CD-ready API validation.
- Team Collaboration:
- Share project-specific specs via portable
.cursor/mcp.json
configurations.
Powered by ReAPI
- API CMS: Design, version, and publish OpenAPI specs via no-code editor.
- API Testing: No-code test creation with cloud execution and CI/CD integration.
- Learn More: reapi.com.
Roadmap
- Semantic search, remote spec sync, and code template support.
- Community-driven improvements via contributions and feedback.
Example Prompt (Cursor IDE):
"Search for all GET operations in the 'user-service' API"