MCP endpoint

One URL for every AI client

Point any MCP-compatible AI client at https://ai-game.dev/mcp and it reaches the game engine you have open — Unity, Unreal Engine or Godot. Tools, prompts and resources are negotiated when the client connects, so there is no schema to copy.

Endpoint URL
https://ai-game.dev/mcp
Transport
Streamable HTTP
Sign-in
OAuth 2.1Project keyAccess token
Protocol
MCP · JSON-RPC 2.0

The fastest way: let setup-mcp write it

Every engine CLI writes the right config file for your client: the project-pinned URL plus a project key, so the client connects at once with nothing to sign in. Add --oauth for a URL-only config that signs in through the browser instead. The desktop app does the same when it sets up a project.

# Unity — writes the pinned URL + a project key for Claude Code
unity-mcp-cli setup-mcp claude-code ./MyUnityProject

# Unreal Engine (the project path is a flag)
unreal-mcp-cli setup-mcp cursor --path ./MyUnrealProject

# Godot, URL-only config that signs in over OAuth
godot-cli setup-mcp gemini ./MyGodotProject --oauth

Install guides with the exact command for each client: Unreal Engine · Unity · Godot

Signing in

OAuth 2.1 — a browser sign-in, nothing to paste

Clients that support MCP authorization sign in through your browser on first connect (authorization code with PKCE and dynamic client registration), then keep their own tokens. The config holds only the URL. The engine CLIs’ own login command uses the device-code flow instead: it prints a code you approve in the browser.

Project keys — what setup-mcp writes

A project key (agd_pk_…) belongs to one project and is sent as a bearer token with the pinned URL. setup-mcp creates it and writes it into the client’s config, so the client works without a browser sign-in. Remove a project from your account and its key stops working.

/mcp or /mcp/p/<pin>

https://ai-game.dev/mcp is the base endpoint: the server routes to one of your connected editors. https://ai-game.dev/mcp/p/<pin> is pinned to one project and always reaches that project’s editor, even when several are open. setup-mcp writes the pinned URL. More in the authentication guide.

Personal access tokens — for CI and scripts

For CI or a client that cannot open a browser, create a personal access token on your access tokens page and send it as a bearer token.

What a request looks like

Every request is a JSON-RPC 2.0 message over Streamable HTTP. A large or progressive answer streams back as Server-Sent Events, so send both content types in Accept. This curl lists the tools of your connected editor with an access token:

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_TOKENA personal access token or project key; OAuth clients send their own token
Acceptapplication/json, text/event-streamBoth types: answers may stream
Content-Typeapplication/jsonThe JSON-RPC body
method"initialize" | "tools/list" | "tools/call" | …Standard MCP methods

Config for your client

Pick your client and copy its config. The first tab signs in over OAuth; the access-token tab is for CI. Anything that speaks MCP works — 14 clients are listed here.

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

Settings → Connectors → Add custom connector
Name: ai-game-dev
URL:  https://ai-game.dev/mcp
Endpoint live. /api/status reports the endpoint’s current health.