Docs · Endpoint

The MCP endpoint —
one URL, every client.

Point any MCP-compatible AI client at https://ai-game.dev/mcp and authorize over OAuth on first connect — or drop in a Personal Access Token for CI. Then start driving your engine with natural language. Tools, prompts, and resources are negotiated on connect — no client-side schema needed.

Endpoint URL

https://ai-game.dev/mcp

Transport

Streamable HTTPSSE

Auth

OAuth 2.1Bearer (PAT)

Protocol

MCP 2025-06-18

→ How auth works Get a Personal Access Token →Tools catalog →

Authentication

OAuth 2.1 — the default

Most clients authorize over the OAuth 2.1 device flow on first connect, so the config you write is credential-free — nothing to paste. On the first request the client opens your browser to approve the device, then stores its credentials.

{
  "mcpServers": {
    "ai-game-dev": {
      "url": "https://ai-game.dev/mcp"
    }
  }
}

`/mcp` vs `/mcp/p/<pin>`

https://ai-game.dev/mcp is the base endpoint — the server routes to one of your connected editors by fallback. https://ai-game.dev/mcp/p/<pin> is a project-pinned URL that always routes to that exact project’s editor; setup-mcp writes the pinned URL by default. See the Authentication guide for pinning and enrollment.

Personal Access Token — for CI & manual clients

For CI pipelines or a manual client that can’t do an interactive browser login, mint a Personal Access Token from your API keys page and send it as a bearer token. PATs are the manual alternative to OAuth, not the default.

{
  "mcpServers": {
    "ai-game-dev": {
      "url": "https://ai-game.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_PERSONAL_ACCESS_TOKEN"
      }
    }
  }
}

Request anatomy

Every request is a JSON-RPC 2.0 envelope. When a client uses a Personal Access Token (e.g. this raw curl), the Authorization header carries it; OAuth clients send their negotiated token instead. The endpoint streams responses as Server-Sent Events when the response payload is large or progressive.

curl -N -X POST "https://ai-game.dev/mcp" \
  -H "Authorization: Bearer YOUR_PERSONAL_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list",
    "params": {}
  }'

AuthorizationBearer YOUR_PERSONAL_ACCESS_TOKENFrom /app/api-keys (PAT); OAuth clients send their own token

Acceptapplication/json, text/event-streamRequired for SSE upgrade

Content-Typeapplication/jsonJSON-RPC body

Body.method"tools/list" | "tools/call" | "initialize" | …Standard MCP methods

Connect your client

Pick your AI client below and copy the config snippet — the default tab is credential-free OAuth, with a Personal Access Token variant for CI. Anything that speaks MCP works — 13 of the most popular are pre-wired.

Every URL below is the base https://ai-game.dev/mcp. To pin a client to one exact project, replace it with https://ai-game.dev/mcp/p/<pin> — setup-mcp writes the pinned URL for you.

{
  "mcpServers": {
    "ai-game-dev": {
      "url": "https://ai-game.dev/mcp"
    }
  }
}

Endpoint live. /api/status reports current health; subscribe via SSE for real-time updates.

The MCP endpoint —one URL, every client.