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

Claude (web, Desktop & Cowork)

Native MCP + OAuthNative agent skill

Adds https://aigamelabs.net/mcp as a custom connector using native OAuth dynamic client registration. One setup covers claude.ai, Claude Desktop and Cowork because remote connectors are brokered through your Claude account. Skills install natively via ZIP upload.

Step 1 · Tools

Connect the MCP server

  1. Individual plans (Free, Pro, Max): go to Customize > Connectors, click "+" then "Add custom connector", and enter https://aigamelabs.net/mcp as the remote MCP server URL.
  2. Team and Enterprise plans: an Owner must add the connector first under Organization settings > Connectors ("Add" > hover "Custom" > "Web" > paste the URL). Members then open Customize > Connectors and click "Connect" on it.
  3. Complete the OAuth flow: Claude registers itself with the server via dynamic client registration (PKCE, browser callback https://claude.ai/api/mcp/auth_callback), you sign in with Google and consent to the games:read and games:write scopes (plus optional offline_access). Do not fill the optional "Advanced settings" client ID/secret fields — the server supports dynamic registration.
  4. Enable the connector per conversation via the "+" button under the chat input, then "Connectors", and toggle aigamelabs on.

Custom connector values

Customize > Connectors > + > Add custom connector
Remote MCP server URL: https://aigamelabs.net/mcp
Advanced settings (OAuth client ID / secret): leave empty — the server
supports dynamic client registration, so Claude registers itself.

Before you connect
  • Free accounts are limited to one custom connector in total; Pro, Max, Team and Enterprise have no such cap. On Team/Enterprise only Owners can add the connector, and admins can disable specific tool calls afterwards.
  • Claude connects from Anthropic cloud infrastructure, not your machine, so the server must be publicly reachable (https://aigamelabs.net/mcp is). The same connector then works on web, Desktop, Cowork and mobile; local claude_desktop_config.json servers are a separate mechanism and irrelevant here.
  • Research mode invokes connector tools automatically without per-tool approval — disable the aigamelabs write tools (add_game / update_game / remove_game) for research runs, and review tool-approval prompts in normal chats.

Step 2 · Workflow

Add the publishing skill

  1. Skills upload requires code execution to be enabled: Settings > Capabilities > "Code execution and file creation" (Free/Pro/Max), or Organization settings > Plugins & skills > Policy tab (Team/Enterprise).
  2. Download the skill as raw Markdown from https://aigamelabs.net/mcp/skills/SKILL.md — the URL is not a ZIP; you package it yourself.
  3. Create a folder named exactly aigamelabs-game-publishing (folder name must match the skill name) containing SKILL.md at its root, and zip that folder.
  4. Go to Customize > Skills, click "+ Create skill", choose "Upload a skill", upload the ZIP, then toggle the skill on. Use the skill snippets below to build the archive.

Build the skill ZIP (bash)

mkdir -p aigamelabs-game-publishing
curl --fail --show-error --location -o aigamelabs-game-publishing/SKILL.md https://aigamelabs.net/mcp/skills/SKILL.md
zip -r aigamelabs-game-publishing.zip aigamelabs-game-publishing
# Upload aigamelabs-game-publishing.zip in Customize > Skills > + Create skill

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.