Connect Agents · MCP + agent skills

Connect your AI client.

Give your agent the tools to manage your games, and the instructions to package and publish them. Choose your client for its exact configuration.

MCP server

The connection that reads and changes your game entries.

MCP server URL

https://aigamelabs.net/mcp

Streamable HTTP · OAuth sign-in and consent · no shared API key

Publishing skill

The workflow for metadata, artwork, WebGL packaging, Unity exports and Unreal limitations.

Publishing skill URL

https://aigamelabs.net/mcp/skills/SKILL.md

One SKILL.md file · installing it does not authorize an agent

29 client guides

Choose your client

The configuration and skill instructions below change with this selection.
For clients with a documented project skill directory.

Client configuration

Cursor

Native MCP + OAuthNative agent skill

Adds https://aigamelabs.net/mcp to .cursor/mcp.json as a remote Streamable HTTP server. Cursor speaks OAuth for remote servers via dynamic client registration, and discovers Agent Skills from .agents/skills/.

Step 1 · Tools

Connect the MCP server

  1. Create or merge .cursor/mcp.json in the project (project scope) or ~/.cursor/mcp.json (global scope) with the aigamelabs entry below. Remote servers need only a "url" — Cursor connects over Streamable HTTP.
  2. Save the file, then open Customize in the sidebar: the server is listed there and can be toggled on or off. Cursor asks for approval before an MCP tool runs by default.
  3. On first use Cursor starts the documented OAuth flow: it registers itself with the server (dynamic client registration), opens a browser for Google sign-in and consent to games:read / games:write (plus optional offline_access). The desktop app answers the flow on the loopback URL http://localhost:8787/callback.
  4. If tools misbehave, open the Output panel (Cmd+Shift+U) and pick "MCP Logs" from the dropdown to see connection and auth errors.

Choose the example for your platform and merge the aigamelabs entry into the existing configuration. Keep unrelated servers and settings.

Merge into .cursor/mcp.json (project) or ~/.cursor/mcp.json (global)

.cursor/mcp.json
{
  "mcpServers": {
    "aigamelabs": {
      "url": "https://aigamelabs.net/mcp"
    }
  }
}

Before you connect
  • Cursor documents a static "auth" block (CLIENT_ID / CLIENT_SECRET) only for providers without dynamic client registration; aigamelabs.net/mcp supports DCR + PKCE, so keep the entry url-only and never add a bearer Authorization header.
  • The documented desktop OAuth redirect is the loopback URL http://localhost:8787/callback (web and cloud agents use https://www.cursor.com/agents/mcp/oauth/callback). The server accepts loopback callback registrations, so no pre-registration is needed; arbitrary custom schemes are not part of this flow.
  • Enterprise admins can restrict remote servers through Team Settings > MCP Configuration allowlists — a URL entry pattern must cover this server there.

Step 2 · Workflow

Add the publishing skill

  1. Download the skill as raw Markdown from https://aigamelabs.net/mcp/skills/SKILL.md and save it as .agents/skills/aigamelabs-game-publishing/SKILL.md (the folder name must match the skill "name" frontmatter).
  2. Cursor discovers skills automatically when it starts; confirm under Customize > Skills, where project skills appear in the "Agent Decides" section.
  3. Invoke it with /aigamelabs-game-publishing in Agent chat, or describe a publishing task — the agent automatically applies skills whose description matches the request.

Run from your project root. This downloads Markdown only, does not execute it, and will not overwrite an existing skill. Review the file before using it.

Download the skill with Bash

skill_dir='.agents/skills/aigamelabs-game-publishing'
mkdir -p "$skill_dir"
if [ -e "$skill_dir/SKILL.md" ]; then
  printf '%s\n' 'SKILL.md already exists. Review or back it up before replacing it.'
else
  curl --fail --show-error --location 'https://aigamelabs.net/mcp/skills/SKILL.md' --output "$skill_dir/SKILL.md"
fi

Download SKILL.mdRead the skill

After setup

Try a read-only first request

First prompt for your agent

Read the aigamelabs-game-publishing skill, then use AIGameLabs list_games to show my game entries. Do not create, publish or remove anything yet.

Once the connection works, the agent can use add_game, update_game and remove_game, plus build, artwork and release tools. Removing a game archives it and revokes delivery; publishing still requires an approved release. Publication is manual by default; explicitly opt in when freezing a release only if you want that exact snapshot to publish automatically on approval.

Your approval remains in control

Sign in on aigamelabs.net and inspect the client's name, callback and requested scopes. Grant games:read for reading and games:write for changes; offline_access permits refresh tokens. Never paste browser cookies, Google credentials or an access token into shared configuration. Creator access, upload limits and human review still apply.

Manage or disconnect an agent in Settings → Connected agents. A recent sign-in is required to disconnect. Review game metadata and ask for confirmation before destructive actions, rights attestations or automatic-publication opt-ins.

Connection help

The URL shows “missing authorization header”

That is the expected OAuth challenge, not a page to sign in on. Add the URL in your client's MCP settings, then use its Connect or Authenticate action to open the consent flow.

The sign-in link expired or the callback was rejected

Reconnect from the MCP client to request a fresh authorization link. Do not bookmark a signed consent URL. Older clients that omit the native application type are inferred from loopback or private-use callbacks; explicitly configured web clients must use HTTPS callbacks. Unsafe callbacks remain rejected.

The client has HTTP support but cannot authenticate

HTTP transport alone is insufficient: this server requires OAuth. Follow the selected guide's native OAuth or documented bridge instructions. A stdio bridge runs locally and stores its own authorization state; do not share that cache or use one person's login for a multi-user server. This server uses dynamic client registration, not URL-based client metadata discovery.

The skill is not listed

Keep the exact filename SKILL.md inside the directory shown for your client, preserve its frontmatter, then reload or start a new session as that client's instructions require. A reference-only app will not show it as an installed native skill.

A game operation is denied after connection

OAuth grants access only to your own workspaces. Creator enrollment, quotas and human review gates remain in force. Read-only consent cannot authorize writes. Ask for the required scope rather than copying a token into configuration or trying to bypass review.