openapi-directory

The OpenAPI Directory MCP Server provides access to the APIs.guru OpenAPI directory, enabling you to discover, compare, and analyze thousands of API specifications right from your chat interface. It supports a progressive discovery workflow with 22 built-in prompts that help you search for APIs, evaluate summaries, examine endpoints, and generate integration guidance. You can import your own custom OpenAPI specs alongside the public directory, making it easy to reason about both external and internal APIs in a single conversational space.

To use it, add the MCP server to your Claude Code setup (or your chosen MCP client) and invoke prompts such as api_discovery to find APIs based on use cases, get_api_summary for high-level details, and get_endpoints or get_endpoint_details for deeper endpoint-level information. The slash commands are automatically exposed for rapid prompt execution, allowing you to trigger tasks like code generation, authentication guidance, and documentation analysis without leaving your chat context.

Prerequisites:

• Node.js (≥14) and npm/yarn installed
• Access to your MCP client (e.g., Claude Code) and permission to add MCP servers

Installation steps:

1. Clone the repository and install dependencies

git clone https://github.com/rawveg/openapi-directory-mcp.git
cd openapi-directory-mcp
npm install

2. Build the project (if applicable)

npm run build

3. Run locally to verify (example)

node dist/index.js

4. Configure your MCP client to connect to the server. Example configuration shown in the mcp_config section below. Ensure the path to the built server matches your environment.

5. Optional: integrate with NPX workflow

npx -y openapi-directory-mcp

Prerequisites note: Replace /path/to/openapi-directory-mcp and /path/to/openapi-directory-mcp/dist/index.js with your actual local paths when configuring the MCP.

Tips and considerations:

• The server exposes access to APIs.guru's directory as well as support for importing custom OpenAPI specifications. Make sure your custom specs are valid OpenAPI definitions to ensure proper parsing and discovery.
• If you upgrade dependencies, re-run build and test locally to avoid runtime issues.
• When using local development prompts, specify concise search queries to maximize efficiency and minimize context usage.
• For best results, leverage the progressive discovery prompts: start with api_discovery, then move to get_api_summary, followed by get_endpoints/get_endpoint_details as needed.
• If you encounter authentication or rate-limiting issues with the public directory, consider using your own imported specs to maintain a smooth workflow within the MCP.