integrations/coding agent/MCP (Model Context Protocol)

MCP (Model Context Protocol) + AIgateway

Mount AIgateway as an MCP server inside any compatible host.

Anthropic's MCP standard lets agents discover and call tools through a typed protocol. AIgateway exposes the catalog and primitives via MCP at api.aigateway.sh/mcp — Claude Code, Cursor agents, and any MCP-aware client can list models, call them, mint sub-accounts, and tag spend.

MCP (Model Context Protocol) homepage →

Setup

Three steps or fewer.

STEP 01

Add to your MCP client (Streamable HTTP, MCP 2025-03-26)

Preferred transport. One POST endpoint, no session management. Add this to your MCP host's config.

{
  "mcpServers": {
    "aigateway": {
      "type": "http",
      "url": "https://api.aigateway.sh/mcp",
      "headers": { "Authorization": "Bearer sk-aig-..." }
    }
  }
}

STEP 02

Or use legacy SSE (MCP 2024-11-05)

If your client only supports the older SSE transport, use these endpoints instead.

{
  "mcpServers": {
    "aigateway": {
      "type": "sse",
      "url": "https://api.aigateway.sh/mcp/sse",
      "headers": { "Authorization": "Bearer sk-aig-..." }
    }
  }
}

STEP 03

Inspect the server

Open https://api.aigateway.sh/mcp/inspect in a browser to list tools, schemas, and sample invocations without leaving the URL.

Notes

Tools available include list_models, call_chat, call_image, mint_sub_account, replay_request, and more.
Both transports are live in production. Streamable HTTP is the recommended transport per the current MCP spec.

MCP (Model Context Protocol) + AIgateway

Three steps or fewer.

Add to your MCP client (Streamable HTTP, MCP 2025-03-26)

Or use legacy SSE (MCP 2024-11-05)

Inspect the server

Same key. Every other tool.