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

AI client

The configuration and skill instructions below change with this selection.

Skill download commands

For clients with a documented project skill directory.

Client configuration

Kiro CLI

Native MCP + OAuthNative agent skill

Kiro CLI connects to remote MCP servers natively with automatic browser OAuth (DCR by default) and auto-discovers Agent-Skills SKILL.md folders in .kiro/skills.

Step 1 · Tools

Connect the MCP server

Edit the user-level MCP config ~/.kiro/settings/mcp.json (or workspace .kiro/settings/mcp.json) and merge in the aigamelabs entry below — kiro-cli mcp add only creates stdio servers, so remote URLs are configured via the file.
Save the file: Kiro hot-reloads mcp.json without restarting the session.
Connect; Kiro opens the authorization page in your browser automatically — most servers use Dynamic Client Registration and need no extra configuration.
Keep the explicit "oauth": { "oauthScopes": [...] } shown below: without it Kiro requests default OIDC scopes (openid, email, profile, offline_access) instead of this server's games scopes.
Inside a session, run /mcp for status, /mcp auth to force re-authentication, and /mcp logout to drop stored credentials.

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

Merge fragment — mcp.json (user or workspace level)

~/.kiro/settings/mcp.json

{
  "mcpServers": {
    "aigamelabs": {
      "url": "https://aigamelabs.net/mcp",
      "oauth": {
        "oauthScopes": ["games:read", "games:write", "offline_access"]
      }
    }
  }
}

Before you connect

OAuth callback is always loopback HTTP (host 127.0.0.1/localhost); leaving oauth.redirectUri unset uses a random free port with path /oauth/callback, which works with dynamically registered clients.
Do not set oauth.clientId here — setting it makes Kiro skip DCR for a pre-registered client, and there is no aigamelabs-registered client ID to use.
Workspace .kiro/settings/mcp.json entries override global ones for the same server name; config hot-reload requires CLI v2.10.0+.

Step 2 · Workflow

Add the publishing skill

Download the skill into a documented skills directory: https://aigamelabs.net/mcp/skills/SKILL.md → .kiro/skills/aigamelabs-game-publishing/SKILL.md (workspace) or ~/.kiro/skills/... (global).
Kiro follows the Agent Skills standard: skills auto-activate when relevant to your task and are also exposed as /aigamelabs-game-publishing slash commands.
No kiro-cli skill import command exists for URLs — copy the file into place manually (the IDE has GitHub/URL import; the CLI does not).

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='.kiro/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.md Read 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.