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

Kiro IDE

Native MCP + OAuthNative agent skill

Adds https://aigamelabs.net/mcp to .kiro/settings/mcp.json with an oauthScopes hint; Kiro runs the browser OAuth flow automatically with dynamic client registration (the IDE supports public PKCE clients), and discovers workspace skills from .kiro/skills/. The Kiro CLI is documented separately.

Step 1 · Tools

Connect the MCP server

  1. Open the command palette and run "Kiro: Open workspace MCP config (JSON)" (project scope, .kiro/settings/mcp.json) or "Kiro: Open user MCP config (JSON)" (global scope, ~/.kiro/settings/mcp.json); alternatively use the "Open MCP Config" icon in the Kiro panel. If MCP is not yet enabled, turn on the MCP support setting in Settings.
  2. Merge the aigamelabs entry below into the existing "mcpServers" object.
  3. Save the file (Cmd+S / Ctrl+S): configuration hot-reloads and the server reconnects automatically. Kiro handles the browser-based OAuth flow itself — most servers need no extra OAuth config thanks to DCR, so Kiro just opens the authorization page for Google sign-in and consent to games:read / games:write plus offline_access.
  4. Confirm the connection in the MCP servers tab of the Kiro panel; logs are under the Output tab as "Kiro - MCP Logs", and an expired token shows a Re-authenticate button in the MCP panel.

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

Merge into .kiro/settings/mcp.json (workspace) or ~/.kiro/settings/mcp.json (user)

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

Before you connect
  • Keep the explicit game scopes shown above: Kiro otherwise requests its default openid/email/profile scopes, which this server does not support. An empty scope list is not a substitute for games:read. The IDE supports public PKCE clients without a client secret; never add a clientSecret here.
  • If an OAuth-protected server fails to connect, check the RFC 8414 issuer mismatch: the authorization server URL advertised by the MCP server must match the issuer in its metadata character-for-character.
  • This profile covers the Kiro IDE desktop editor. Kiro CLI shares the same agent harness and .kiro configuration model but has its own setup surface (kiro-cli commands), documented separately on kiro.dev.

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 .kiro/skills/aigamelabs-game-publishing/SKILL.md (workspace scope; commit it so the team shares it — ~/.kiro/skills/ is the global alternative).
  2. Kiro discovers available skills when a chat session starts; view and manage them in the "Agent Steering & Skills" section of the Kiro panel, which can also import skills from a local folder.
  3. Invoke it with /aigamelabs-game-publishing or let Kiro activate it automatically when the request matches the skill description.
  4. Custom agents do not load skills by default: add "skill://.kiro/skills/*/SKILL.md" to the agent config "resources" array to opt in.

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.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.