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

ChatGPT (web custom apps)

Native MCP + OAuthSkill used as reference

ChatGPT web supports OAuth-protected custom MCP apps through developer mode, subject to plan and workspace permissions. The cited Help Center guide describes write tools for Business/Enterprise/Edu and read/fetch connections for Pro. Here the skill is used as reference material; local Codex-host setup is covered separately under OpenAI Codex.

Step 1 · Tools

Connect the MCP server

  1. Check eligibility first: full MCP support with write actions is a beta rolling out to ChatGPT Business, Enterprise and Edu on ChatGPT web only (no mobile). Business/Edu/Enterprise admins enable developer mode under Workspace Settings > Permissions & Roles > "Connected Data Developer mode / Create custom MCP connectors"; Enterprise/Edu admins can grant it to specific members via RBAC, and enabled users toggle it under Settings > Apps > Advanced Settings. On Business only admins/owners can use developer mode.
  2. Create the connector: with developer mode enabled, go to Workspace settings > Apps > Create (or user Settings > Apps > Create). Name it aigamelabs, enter https://aigamelabs.net/mcp as the MCP endpoint, and pick OAuth as the authentication mechanism.
  3. Click "Scan Tools": when the server's OAuth prompt appears, complete the Google sign-in and consent (games:read, games:write, optional offline_access), then wait for the tool scan to finish and click "Create".
  4. The app appears as a draft under Workspace settings > Apps > Drafts; an admin publishes it (review the write-action warnings), after which it shows up for users under Settings > Apps and can be selected in the tools menu of a chat.
  5. Plan restrictions change: the cited Help Center guide describes Pro connections as read/fetch-only. Check your current plan and workspace controls before expecting write tools or a Create app option.

Custom MCP app values (developer mode)

Workspace settings > Apps > Create   (developer mode required)
Name:    aigamelabs
MCP URL: https://aigamelabs.net/mcp
Auth:    OAuth — complete the Google sign-in and consent during "Scan Tools"

Before you connect
  • ChatGPT keeps a frozen snapshot of a published app's tools: if the server later adds tools (for example upload/release workflow tools), an admin must click Refresh / republish before they appear. Business plans cannot edit apps after publishing — recreate and republish.
  • For durable connections, the OAuth provider should advertise offline_access (or equivalent) in its discovery metadata so refresh tokens are issued; ChatGPT warns users may need to re-authenticate otherwise. This server supports optional offline_access.
  • Deep research can use custom apps for read/fetch only, and agent mode does not use custom apps, so publishing games via those surfaces is not possible — use normal chats with the app selected.

Step 2 · Workflow

Add the publishing skill

  1. This ChatGPT web workflow uses the skill as Project or chat reference material, not as an auto-discovered SKILL.md installation.
  2. Download the Markdown from https://aigamelabs.net/mcp/skills/SKILL.md.
  3. Attach the file to a Project, paste the workflow into Project instructions or custom GPT instructions, or attach it per chat, and ask ChatGPT to follow it when calling the aigamelabs tools.
  4. Treat the instructions as advisory context to request explicitly — nothing auto-discovers or executes them.

Download the skill as reference Markdown

curl -L -o aigamelabs-game-publishing.SKILL.md https://aigamelabs.net/mcp/skills/SKILL.md

Download SKILL.mdRead the skill

Reading or attaching the Markdown is a workflow reference, not automatic native skill discovery. It does not connect MCP or grant account access.

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.