mcp-openapi
If you are the rightful owner of mcp-openapi and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
A Model Context Protocol (MCP) server that loads and serves multiple OpenAPI specifications to enable LLM-powered IDE integrations.
The @reapi/mcp-openapi server is designed to facilitate the integration of OpenAPI specifications with LLM-powered development tools, such as IDEs like Cursor. It acts as a bridge, allowing these tools to understand and work with APIs directly. The server can load multiple OpenAPI specifications from a directory, expose API operations and schemas through the MCP protocol, and maintain a catalog of all available APIs. This enables LLMs to provide intelligent code completion, assist in API integration, and generate API-aware code snippets. The server supports dereferenced schemas for complete API context and is sponsored by ReAPI, a platform that simplifies API design and testing.
Features
- Loads multiple OpenAPI specifications from a directory
- Exposes API operations and schemas through MCP protocol
- Enables LLMs to understand and work with your APIs directly in your IDE
- Supports dereferenced schemas for complete API context
- Maintains a catalog of all available APIs
Tools
refresh-api-catalog
Refresh the API catalog. Returns: Success message when catalog is refreshed
get-api-catalog
Get the API catalog, the catalog contains metadata about all openapi specifications, their operations and schemas. Returns: Complete API catalog with all specifications, operations, and schemas
search-api-operations
Search for operations across specifications. Inputs: query (string): Search query, specId (optional string): Specific API specification ID to search within. Returns: Matching operations from the API catalog
search-api-schemas
Search for schemas across specifications. Inputs: query (string): Search query, specId (optional string): Specific API specification ID to search. Returns: Matching schemas from the API catalog
load-api-operation-by-operationId
Load an operation by operationId. Inputs: specId (string): API specification ID, operationId (string): Operation ID to load. Returns: Complete operation details
load-api-operation-by-path-and-method
Load an operation by path and method. Inputs: specId (string): API specification ID, path (string): API endpoint path, method (string): HTTP method. Returns: Complete operation details
load-api-schema-by-schemaName
Load a schema by schemaName. Inputs: specId (string): API specification ID, schemaName (string): Name of the schema to load. Returns: Complete schema details
