APIs.guruMCP Configuration & Schema Registry
The APIs.guru Model Context Protocol (MCP) configuration provides a validated, machine-readable JSON schema and executable bridge that connects state-of-the-art AI coding assistants — including Claude Desktop, Cursor IDE, Windsurf, Cline, and VS Code Copilot — directly to the APIs.guru REST API. By leveraging the standardized open Model Context Protocol, AI agents can dynamically discover capabilities, validate input parameters against strict JSON Schemas, and execute live API operations without context switching or manual copy-pasting.
Quick Specs & Integration Summary
Technical Architecture & Protocol Semantics
Under the Model Context Protocol specification, the APIs.guru configuration functions as an isolated protocol adapter. When an AI agent initializes a session, the client establishes a bidirectional JSON-RPC 2.0 communication channel over standard input/output (stdio) or Server-Sent Events (SSE). During the initial handshake, the server publishes its tool manifest extracted from the APIs.guru OpenAPI specification (version 2.2.0).
APIs.guru serves as a centralized, authoritative index for the web API ecosystem, functioning as a dynamic encyclopedia of machine-readable API definitions. Maintained by a dedicated community and governed by a transparent process, its core capability is to aggregate, standardize, and serve the latest OpenAPI specifications from thousands of public APIs. By providing a single, unified interface for these diverse API contracts, it eliminates the significant overhead developers traditionally face in manually searching for, validating, and integrating API documentation from disparate sources. The platform is invaluable for enterprises and individual developers engaged in building integrations, developing API-driven applications, conducting market research on available services, or ensuring their own API adheres to community standards. Typical use cases span from a startup needing to quickly discover and compare payment processing APIs to a large corporation auditing its API portfolio for consistency and identifying opportunities for consolidation or enhancement. Exposing the APIs.guru repository as tools via the Model Context Protocol (MCP) transforms it from a passive reference into an active, intelligent resource for AI coding assistants. This integration grants the AI agent a live, queryable awareness of the vast API landscape, enabling it to move beyond static code generation to context-aware, informed decision-making. The primary value lies in automated discovery and validation. Instead of a developer manually looking up an API's schema, the AI can programmatically fetch and analyze the precise, current specification needed for a task. This dramatically accelerates prototyping, reduces integration errors, and ensures generated code or configurations are built upon the correct, versioned contract. For the AI assistant, this MCP server becomes a critical tool for answering queries about API compatibility, identifying the best-fit service for a described need, and scaffolding client code that is immediately accurate. A developer can instruct the AI coding assistant to perform a wide array of dynamic tasks leveraging this MCP connection. For instance, a developer could ask: "Find the official OpenAPI spec for the Stripe Payments API and generate a TypeScript client with methods for creating charges and refunds." The AI would use the tools to locate the precise `/specs/{provider}/{api}.json` endpoint, fetch the specification, and generate code aligned with its exact endpoints, parameters, and schemas. Another powerful workflow involves comparative analysis: "List all APIs from the 'github' provider and identify which ones support webhooks for repository events." The AI would query `/providers.json` to confirm the provider, then iterate through available APIs using `/list.json` or provider-specific endpoints to analyze each spec's `webhooks` section. This enables automated audits, dependency checks, and intelligent recommendation engines, where the AI agent can state, "Based on the latest specs in APIs.guru, the 'aws-lambda' API supports the following authentication methods..." enabling the developer to make informed choices immediately. While the APIs.guru API itself requires no authentication for public access, developers and AI agents must adhere to responsible consumption practices. The most critical guideline is to respect service availability through rate limiting and efficient caching. Since the data is public but dynamically generated, excessive or naive polling can impact performance. Best practices include caching responses locally, using conditional requests where applicable, and implementing exponential backoff for retries. From a security and principle-of-least-privilege perspective, even though the API is open, the AI agent's tool should be configured with a narrow scope—only querying for data it explicitly needs for the current task rather than performing broad, exploratory crawls. When setting up the MCP server, developers should ensure their client configuration explicitly lists only the required endpoints (like `GET /specs/...`) to minimize the agent's operational surface area and focus its capabilities on precise, task-oriented data retrieval. This architecture guarantees strict process boundary isolation: all sensitive authorization headers and secret tokens remain sandboxed inside the client runtime, never leaking into language model context windows or external logging endpoints.
Hosted Remote Configuration URL
MCP Configuration FileProvide this hosted URL in any client that supports remote MCP schema auto-loading.
https://mcpbridge.org/config/apis-guru.json2. AI Assistant Use Cases & Practical Workflows
Tailored for CommunicationReal-world execution scenarios demonstrating how LLM agents (Claude 3.7, GPT-4o, Cursor Agent) invoke APIs.guru tools to automate developer workflows.
1. Automated Incident Escalation & Notification Routing
Incident CommsBroadcast priority notifications with rich incident context, system health metrics, and on-call engineer assignment details.
"Dispatch a high-priority incident notification via APIs.guru containing the latest stack trace, affected microservice names, and link to the active monitoring dashboard."
2. Knowledge Base & Workspace Documentation Sync
Knowledge SyncSynchronize newly merged pull request documentation and architectural decision records into searchable workspace hubs.
"Fetch updated technical notes from our repository and sync them into APIs.guru. Ensure headers, code blocks, and parameter tables are correctly formatted in markdown."
3. Omnichannel Customer Ticket Triaging & Sentiment Analysis
Support AutomationClassify incoming customer inquiry tickets, detect customer sentiment urgency, and auto-draft contextual solution proposals.
"Retrieve open customer support tickets from APIs.guru. Classify urgency based on customer sentiment and generate drafted reply outlines for Tier-2 engineering review."
4. Scheduled Webhook Dispatch & Event Orchestration
Event OrchestrationAutomate event notification triggers when deployments complete, staging builds pass, or schema changes are detected.
"Configure an event notification hook in APIs.guru to trigger Slack updates whenever a high-severity deployment event is logged in staging."
End-to-End Multi-Step Agent Execution Lifecycle
When an engineer submits a task to Claude Desktop or Cursor, the LLM executes an autonomous 4-phase Model Context Protocol loop:
Schema Introspection
Handshake lists all 7 tools and builds argument validators.
Argument Synthesis
Model extracts parameters from prompt and validates types against OpenAPI rules.
Stdio Execution
Bridge invokes live API with injected local credentials and captures raw HTTP response.
Output Remediation
LLM parses JSON results, handles status codes, and presents synthesized answers.
3. Multi-Client Installation Matrix & Setup Guides
Select your AI assistant below to view exact configuration file paths, JSON installation snippets, and launch commands.
Claude Desktop
claude_desktop_config.json~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json{
"mcpServers": {
"apis-guru": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/apis.guru/2.2.0/openapi.json"
],
"env": {
"APIS_GURU_API_KEY": "your_apis_guru_api_key"
}
}
}
}Cursor IDE
.cursor/mcp.jsonOpen Cursor Settings → Features → MCP Servers, or create .cursor/mcp.json in your project root.
{
"mcpServers": {
"apis-guru": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/apis.guru/2.2.0/openapi.json"
],
"env": {
"APIS_GURU_API_KEY": "your_apis_guru_api_key"
}
}
}
}Saves as .cursor/mcp.json in the download. Move it to your project root.
VS Code / Cline Extension
cline_mcp_settings.jsonPaste into your Cline extension MCP configuration or Roo Code host settings.
{
"mcpServers": {
"apis-guru": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/apis.guru/2.2.0/openapi.json"
],
"env": {
"APIS_GURU_API_KEY": "your_apis_guru_api_key"
}
}
}
}Zed Editor & Docker CLI
Zed / DockerDocker container execution command:
docker run -i --rm -e APIS_GURU_API_KEY="YOUR_SECRET_VALUE" node:20-alpine npx -y @modelcontextprotocol/server-openapi https://api.apis.guru/v2/specs/apis.guru/2.2.0/openapi.json
Zed settings context servers JSON:
{
"context_servers": {
"apis-guru": {
"command": {
"path": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/apis.guru/2.2.0/openapi.json"
],
"env": {
"APIS_GURU_API_KEY": "your_apis_guru_api_key"
}
}
}
}
}Programmatic SDK Integration (TypeScript / Python)
Initialize the APIs.guru MCP client directly in your backend codebase.
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";
// Initialize APIs.guru MCP client transport over stdio
const transport = new StdioClientTransport({
command: "npx",
args: ["-y","@modelcontextprotocol/server-openapi","https://api.apis.guru/v2/specs/apis.guru/2.2.0/openapi.json"],
env: { APIS_GURU_API_KEY: process.env.APIS_GURU_API_KEY || "YOUR_SECRET_KEY" }
});
const client = new Client(
{ name: "apis-guru-client", version: "1.0.0" },
{ capabilities: { tools: {}, resources: {}, prompts: {} } }
);
async function connectAndRun() {
await client.connect(transport);
const tools = await client.listTools();
console.log("Connected to APIs.guru MCP Server.");
console.log("Discovered 7 mapped tools:", tools);
}
connectAndRun().catch(console.error);Raw Stdio Schema Definition
schema.jsonFor standalone CLI wrappers, background daemon daemons, or custom script integrations:
{
"mcpServers": {
"apis-guru": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/apis.guru/2.2.0/openapi.json"
],
"env": {
"APIS_GURU_API_KEY": "your_apis_guru_api_key"
}
}
}
}4. Security, Authentication & Credential Management
Safely configure authentication tokens, isolate execution environments, and implement enterprise security best practices.
Required Environment Keys Reference
| Variable Name | Required | Type | Default | Purpose & Guidance |
|---|---|---|---|---|
| APIS_GURU_API_KEY | REQUIRED | Secret Key / Token | None (Set in env) | your_apis_guru_api_key |
Zero-Downtime Token Rotation Protocol
- Generate Secondary Key: Create a new secret API token with identical scopes in your APIs.guru developer portal.
- Update Client Configuration: Insert the new token inside the
envblock of your MCP client JSON config. - Validate Connection: Issue a test query in Claude or Cursor to ensure handshake and tool calls succeed.
- Revoke Stale Token: Decommission the legacy key on the vendor portal to prevent unauthorized access.
Least-Privilege & Sandboxing Rules
- Read-Only Token Scoping: Whenever your workflow only requires querying data, provision read-only credentials to prevent accidental mutations.
- Local Process Isolation: Stdio transports run in isolated local subprocesses; secret credentials are never sent across the internet to MCP Bridge servers.
- Prompt Injection Defense: AI model responses are sandboxed; verify generated destructive arguments before confirming execution in agent mode.
Enterprise Security Checklist (Mandatory Practices)
- Never commit
claude_desktop_config.jsonor.cursor/mcp.jsoncontaining raw secrets into public GitHub repositories. - Add
.cursor/mcp.jsonand.env.localto your project's.gitignorefile. - Always enforce TLS/HTTPS encryption on outbound network requests initiated by the server process.
5. Tool Parameter Schemas & Natural Language Execution
Mapped OpenAPI operations converted into discrete Model Context Protocol tools with strict JSON-RPC payload validators.
/list.jsonList all APIs
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "apis-guru_get_list_json",
"arguments": {}
}
}"Use APIs.guru to execute List all APIs and output the formatted result."
/metrics.jsonGet basic metrics
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "apis-guru_get_metrics_json",
"arguments": {}
}
}"Use APIs.guru to execute Get basic metrics and output the formatted result."
/providers.jsonList all providers
{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "apis-guru_get_providers_json",
"arguments": {}
}
}"Use APIs.guru to execute List all providers and output the formatted result."
/specs/{provider}/{api}.jsonRetrieve one version of a particular API
{
"jsonrpc": "2.0",
"id": 4,
"method": "tools/call",
"params": {
"name": "apis-guru_get_specs__provider___api__json",
"arguments": {}
}
}"Use APIs.guru to execute Retrieve one version of a particular API and output the formatted result."
/specs/{provider}/{service}/{api}.jsonRetrieve one version of a particular API with a serviceName.
{
"jsonrpc": "2.0",
"id": 5,
"method": "tools/call",
"params": {
"name": "apis-guru_get_specs__provider___service___api__json",
"arguments": {}
}
}"Use APIs.guru to execute Retrieve one version of a particular API with a serviceName. and output the formatted result."
/{provider}.jsonList all APIs for a particular provider
{
"jsonrpc": "2.0",
"id": 6,
"method": "tools/call",
"params": {
"name": "apis-guru_get_provider__json",
"arguments": {}
}
}"Use APIs.guru to execute List all APIs for a particular provider and output the formatted result."
/{provider}/services.jsonList all serviceNames for a particular provider
{
"jsonrpc": "2.0",
"id": 7,
"method": "tools/call",
"params": {
"name": "apis-guru_get_provider__services_json",
"arguments": {}
}
}"Use APIs.guru to execute List all serviceNames for a particular provider and output the formatted result."
6. Interactive Troubleshooting & FAQ Accordion
Diagnose and resolve common JSON-RPC protocol error codes, connection disconnects, and schema refresh issues.
A 401 Unauthorized response indicates that the upstream APIs.guru API rejected the authentication credential supplied in your MCP client's environment configuration. To resolve this: (1) Verify that your secret token is defined inside the "env" block of claude_desktop_config.json or .cursor/mcp.json rather than hardcoded in the command string. (2) Check whether APIs.guru requires a prefix such as "Bearer <token>" in the authorization header. (3) Confirm that your API key has not expired and has been granted sufficient least-privilege scopes on the APIs.guru developer dashboard.
If your MCP client fails to initialize tools for APIs.guru: (1) Test the bridge launcher command ("npx -y @modelcontextprotocol/server-openapi https://api.apis.guru/v2/specs/apis.guru/2.2.0/openapi.json") directly inside your terminal or shell to inspect stdout/stderr diagnostic traces. (2) Verify network connectivity to the schema source (https://api.apis.guru/v2/specs/apis.guru/2.2.0/openapi.json). (3) Ensure Node.js (v18+) is installed and accessible in your system PATH. (4) For authenticated APIs, confirm credentials are configured in your client's "env" mapping rather than command arguments.
MCP clients like Claude Desktop and Cursor query the server's tools list ("tools/list") during startup and cache the resulting JSON Schema for the duration of the application session. If new endpoints or parameters are added to APIs.guru: (1) Fully quit and restart Claude Desktop (Cmd+Q on macOS or File > Exit on Windows). (2) In Cursor IDE, navigate to Settings > Features > MCP Servers, toggle the APIs.guru server off and on, or click the refresh icon to re-execute the initialization handshake.
If the AI model hallucinates parameters or fails to invoke a tool automatically: (1) Add explicit system instructions in your project's .cursorrules or Claude project prompt (e.g., "When querying Communication, always invoke the apis-guru MCP server tools first"). (2) Ensure parameter types match schema specifications (e.g., passing integers as numbers rather than strings). (3) Check that required parameters marked in Section 5 are not omitted from the model's generated payload.
When the APIs.guru upstream endpoint returns an HTTP 429 Too Many Requests response, the MCP server bubbles the structured error payload back to the AI client over stdio. Modern LLMs like Claude 3.7 and Cursor Agent recognize rate-limiting status codes, inspect the "Retry-After" header if present, and will automatically introduce backoff delays or ask the user before retrying the operation.
The Hosted Config URL (https://mcpbridge.org/config/apis-guru.json) provides a static, remote JSON schema definition that cloud-native MCP clients can fetch over HTTPS for dynamic discovery. In contrast, local stdio configurations execute a local subprocess on your workstation. Local stdio processes offer maximum security because secret API keys remain strictly on your local machine and never transit third-party proxy servers.
Similar Communication Configurations
Explore related API bridges with ready-to-use Model Context Protocol schemas.
Slack API
CommunicationSend messages, manage channels, and integrate Slack notifications into your AI agent workflows.
https://mcpbridge.org/config/slack.jsonDiscord API
CommunicationSend messages, manage servers, and integrate Discord bots into your AI agent workflows.
https://mcpbridge.org/config/discord.jsonTwilio API
CommunicationSend SMS, make calls, and manage communication channels through your AI agent.
https://mcpbridge.org/config/twilio.jsonEmail Activity (beta)
CommunicationThe Email Activity (beta) API, provided by [Your Email Service Provider], is a specialized suite of endpoints designed to grant programmatic access to granular email event data and system security configurations. Its core capability revolves around detailed filtering and search across two primary domains: user engagement events (like opens, clicks, and bounces) and security/access control settings. While the event data functionality is limited to a recent two-day window by default, it serves as a powerful tool for real-time monitoring and immediate post-campaign analysis. Typical use cases for enterprise teams include building internal dashboards for marketing performance, automating alerts for campaign anomalies (e.g., a sudden spike in bounces), and developing custom reporting pipelines that feed into business intelligence systems. The associated security endpoints—managing an access whitelist and configuring alert notifications—provide critical administrative control, allowing teams to programmatically define which IP addresses or systems can interact with their email infrastructure and to set up proactive monitoring for potential security or deliverability issues. When exposed as tools to an AI coding assistant via the Model Context Protocol (MCP), the value of the Email Activity API shifts from simple data retrieval to enabling intelligent, context-aware automation and synthesis. An AI agent, such as Claude Desktop or an IDE-integrated assistant, can leverage these endpoints not just to fetch data, but to perform complex reasoning on the results. For instance, instead of a developer manually querying for all "bounce" events, they can instruct the AI to "analyze the last 24 hours of bounce data, group them by recipient domain, and draft an alert for the ops team if the failure rate for our primary domain exceeds 1%." The AI can dynamically combine data from the activity endpoint with the current security whitelist via the `/access_settings/whitelist` endpoint to audit configurations, generating suggestions like "I noticed the marketing automation server's IP is not whitelisted, which may be causing the recent campaign sends to fail. Should I add it?" Practical workflow examples showcase the transformative potential of this integration. A developer can instruct the AI agent to perform dynamic tasks such as: "Query the `/alerts` endpoint, review the current conditions for our 'high bounce rate' alert, and suggest a more sensitive threshold based on the bounce data from the last hour, then propose the corresponding API call to update it." Alternatively, an agent could be tasked to "Audit our security posture by fetching the current whitelist, cross-reference it with recent access logs (if available through a separate log endpoint), and flag any IP addresses that have made numerous requests but are not currently whitelisted, recommending whether to create a new whitelist rule." This allows the AI to act as an operational analyst, continuously monitoring system state and suggesting or implementing administrative actions based on real-time data streams. Critical implementation considerations begin with the "None" authentication method indicated for this beta API, which is a significant security red flag. Developers must assume this is a placeholder or error and seek alternative, robust authentication (like OAuth 2.0 or API key via a secure header) as soon as the API matures. Until then, any integration must treat the endpoints as highly sensitive and be restricted to non-production, sandboxed environments only. When setting up the MCP server, adherence to the principle of least privilege is paramount: the API keys or tokens used should be scoped exclusively to the narrow set of email activity and security endpoints required for the specific workflow, with no unnecessary read/write permissions. Configuration should ensure all API calls are made over TLS, and any locally cached email event data must be treated as confidential, encrypted at rest and in transit to prevent exposure of sensitive user engagement information. Developers must also build in robust error handling for rate limits and the inherent instability of beta endpoints, designing their AI-driven workflows to gracefully manage changes in the API schema without failure.
https://mcpbridge.org/config/sendgrid-com.json