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

Qwen Code

Native MCP + OAuthNative agent skill

CLI-first coding agent with HTTP-transport MCP, automatic OAuth discovery (401 → metadata → dynamic client registration) and native project/user skills.

Step 1 · Tools

Connect the MCP server

  1. Add the server with the CLI (writes ~/.qwen/settings.json user scope by default): qwen mcp add --transport http aigamelabs https://aigamelabs.net/mcp
  2. Restart Qwen Code in your project and run /mcp to open the MCP management dialog; aigamelabs appears with its 15 tools.
  3. On the first authenticated call Qwen Code detects the 401, discovers the OAuth endpoints from server metadata and performs dynamic client registration, then opens the browser for Google login + consent.
  4. Use the /mcp dialog to inspect connection state and manage authentication interactively; tokens refresh automatically when expired.
  5. Alternatively define the server by editing settings.json directly — both approaches produce the same mcpServers entry.

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

Add via CLI (user scope)

qwen mcp add --transport http aigamelabs https://aigamelabs.net/mcp

Merge fragment — settings.json (user or project scope)

~/.qwen/settings.json
{
  "mcpServers": {
    "aigamelabs": {
      "httpUrl": "https://aigamelabs.net/mcp"
    }
  }
}

Before you connect
  • OAuth endpoint URLs, client ID and scopes are auto-discovered (the docs mark authorizationUrl/tokenUrl "auto-discovered if omitted" and clientId "optional with dynamic registration") — do not add --oauth-* flags for this server.
  • The OAuth callback defaults to the loopback URL http://localhost:7777/oauth/callback; remote/cloud sessions need a reverse-proxied public /oauth/callback per the docs.
  • Tokens are stored in ~/.qwen/mcp-oauth-tokens.json (plaintext, mode 0600) by default; set QWEN_CODE_FORCE_ENCRYPTED_FILE_STORAGE=true for encrypted/keychain storage on shared machines.

Step 2 · Workflow

Add the publishing skill

  1. Download the skill into the documented project skills directory: https://aigamelabs.net/mcp/skills/SKILL.md → .qwen/skills/aigamelabs-game-publishing/SKILL.md.
  2. Skills are model-invoked: the agent loads the skill automatically when your request matches its description.
  3. Invoke explicitly with the slash form /aigamelabs-game-publishing, or browse with the /skills panel.
  4. For all-projects availability, place the folder under ~/.qwen/skills/ instead (user scope).

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