MCP: Connect AI to Your API

Use the OpenAPI Schema to connect to this website.

What is MCP?

The Model Context Protocol (MCP) is a standard that allows AI systems, code editors, and other tools to discover and use your API through a standardized interface. Instead of manually documenting endpoints, MCP exposes your OpenAPI specification as tools the AI can call directly.

Quick Start with Claude Desktop

1. Open your Claude Desktop configuration:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

2. Add this configuration under mcpServers:

{
  "mcpServers": {
    "api": {
      "command": "npx",
      "args": ["-y", "@ivotoby/openapi-mcp-server"],
      "env": {
        "API_BASE_URL": "https://favicon.media",
        "OPENAPI_SPEC_PATH": "https://favicon.media/openapi.json",
        "API_HEADERS": "Authorization:Bearer YOUR_API_TOKEN"
      }
    }
  }
}

3. Replace YOUR_API_TOKEN with your API credentials token (see Settings → Credentials)

4. Restart Claude Desktop and your API endpoints will appear as tools

Configuration Options

API_BASE_URL

Base URL for API requests: https://favicon.media

OPENAPI_SPEC_PATH

URL or local path to OpenAPI spec: https://favicon.media/openapi.json

API_HEADERS

Comma-separated authentication headers:
Authorization:Bearer token,X-API-Key:key

TOOLS_MODE

all (default) - expose all endpoints | dynamic - expose only meta-tools for exploration

Filtering Endpoints

Control which API endpoints are exposed as MCP tools:

{
  "mcpServers": {
    "api": {
      "command": "npx",
      "args": [
        "-y",
        "@ivotoby/openapi-mcp-server",
        "--exclude-tag", "admin",
        "--exclude-tag", "internal"
      ],
      "env": { ... }
    }
  }
}

Flags: --tool, --tag, --exclude-tag, --resource, --operation

Using with Other Tools

Beyond Claude Desktop, the OpenAPI MCP Server works with:

• Cursor – IDE integration with AI features
• VS Code – With MCP client extension
• HTTP Clients – Using HTTP transport instead of stdio
• Custom Applications – Use as a library in Node.js

HTTP Transport

For web applications and HTTP-only environments, run the server with HTTP transport:

npx @ivotoby/openapi-mcp-server \
  --api-base-url https://favicon.media \
  --openapi-spec https://favicon.media/openapi.json \
  --headers "Authorization:Bearer YOUR_TOKEN" \
  --transport http \
  --port 3000

Then send MCP requests to http://localhost:3000/mcp

Dynamic Tool Discovery

For large or evolving APIs, use dynamic mode to discover endpoints on-the-fly:

{
  "mcpServers": {
    "api": {
      "command": "npx",
      "args": [
        "-y",
        "@ivotoby/openapi-mcp-server",
        "--tools", "dynamic"
      ],
      "env": { ... }
    }
  }
}

This provides list-api-endpoints, get-api-endpoint-schema, and invoke-api-endpoint meta-tools instead of loading all endpoints upfront.

Authentication

Generate API credentials in your account settings:

Go to Settings → Credentials
Click "Create Credential" and give it a name (e.g., "MCP Server")
Copy the secret immediately
Use it in the API_HEADERS configuration as the Bearer token