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

Windsurf

Native MCP + OAuthNative agent skill

Adds https://aigamelabs.net/mcp to the Cascade mcp_config.json via the "Open MCP config file" button. Windsurf supports OAuth for HTTP/SSE remote servers, and Cascade discovers skills from .windsurf/skills/ (legacy, still read) and .agents/skills/.

Step 1 · Tools

Connect the MCP server

  1. Open the Cascade panel, click the "..." (Actions) menu in the top right, and click the "Open MCP config file" icon in the MCPs section — this opens the mcp_config.json your installation actually reads.
  2. Merge the aigamelabs entry under the existing "mcpServers" object (remote HTTP entries use "serverUrl" or "url"; no headers are needed because auth is OAuth).
  3. Save the file and toggle the server on in the MCPs list of that same menu. Windsurf supports OAuth for each transport type, so the first connection opens a browser for Google sign-in and consent to games:read / games:write (plus optional offline_access).
  4. Ask Cascade to use a tool or mention the server by name; per-tool toggles and the "disabledTools" array can restrict individual tools.

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

Merge into Cascade mcp_config.json (open via Cascade panel > ... > Open MCP config file)

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "aigamelabs": {
      "url": "https://aigamelabs.net/mcp"
    }
  }
}

Before you connect
  • Cascade has a limit of 100 total tools across all configured servers at any given time, so other servers may need trimming.
  • Windsurf (Cognition) docs were merged into the Devin Desktop docs: the same pages now also live under docs.devin.ai/desktop/cascade, and current docs list mcp_config.json at ~/.config/devin/mcp_config.json or %APPDATA%\devin\mcp_config.json. The panel button opens the correct file; VS Code's discovery reference still documents Windsurf at ~/.codeium/windsurf/mcp_config.json.
  • Enterprise users must enable MCP manually in settings before remote servers connect; Cascade has no one-click marketplace, so file-based setup is the documented path.

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 — Cascade discovers .agents/skills/ for cross-agent compatibility, and the product-specific .windsurf/skills/ (legacy) also still works.
  2. Only the skill name and description are loaded until invoked (progressive disclosure); trigger it by @mentioning @aigamelabs-game-publishing in the Cascade input or let matching descriptions activate it.
  3. For a personal copy across projects, use the global skills folder ~/.codeium/windsurf/skills/ instead (or ~/.config/devin/skills/, which is shared with the Devin CLI).

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.