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

Cline

Native MCP + OAuthNative agent skill

VS Code coding extension. Native remote MCP over Streamable HTTP with built-in OAuth 2.1 (PKCE + Dynamic Client Registration), and native SKILL.md skills loaded from .cline/skills/.

Step 1 · Tools

Connect the MCP server

  1. Open the MCP Servers view in the Cline panel and use the Remote Servers tab: Server Name aigamelabs, Server URL https://aigamelabs.net/mcp, Transport Type Streamable HTTP, then Add Server. JSON editing via the Configure tab works too.
  2. Use the Configure tab to open the installed version's MCP settings file, then merge the fragment under mcpServers. Current shared settings use ~/.cline/data/settings/cline_mcp_settings.json.
  3. First connection returns 401 with an Authenticate button: click it, complete the aigamelabs Google login + consent (scopes games:read, games:write, optional offline_access) in the browser, and Cline redirects back and connects — OAuth 2.1 with PKCE and Dynamic Client Registration.
  4. Verify the aigamelabs server is enabled and its tools (add_game, update_game, list_games, get_game, upload/release workflow) are listed; keep autoApprove empty so every tool call still asks before running.

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

cline_mcp_settings.json — merge into the existing mcpServers object

~/.cline/data/settings/cline_mcp_settings.json
{
  "mcpServers": {
    "aigamelabs": {
      "type": "streamableHttp",
      "url": "https://aigamelabs.net/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Before you connect
  • Use a current Cline release. Its current MCP OAuth manager runs an HTTP loopback callback server shared with the CLI; older versions used host-specific callbacks. The current flow matches this server's native callback rules.
  • Cline requires the authorization server to support Dynamic Client Registration (RFC 7591) — this server does. Against servers without DCR Cline reports "Incompatible auth server".
  • Do not add an Authorization header manually: there is no shared API key, and Cline obtains the per-user access token through OAuth.

Step 2 · Workflow

Add the publishing skill

  1. Download https://aigamelabs.net/mcp/skills/SKILL.md and save it as SKILL.md inside the project folder .cline/skills/aigamelabs-game-publishing/ — the frontmatter name aigamelabs-game-publishing must match the directory name exactly.
  2. Cline detects skills automatically; verify in the Skills menu (scale icon next to the model selector → Skills tab). Skills are enabled by default when discovered.
  3. Invoke explicitly by typing /aigamelabs-game-publishing in chat, or let Cline auto-activate it via the use_skill tool when a request matches the skill description.
  4. Global alternative: ~/.cline/skills/ (Windows: C:\Users\<you>\.cline\skills\). When both exist the global skill takes precedence over the project one.

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='.cline/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.