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

Gemini CLI

Native MCP + OAuthNative agent skill

Google's open-source terminal agent. gemini mcp add --transport http plus OAuth auto-discovery with dynamic client registration, and native skills in .gemini/skills/<name>/SKILL.md.

Step 1 · Tools

Connect the MCP server

  1. Add the server: gemini mcp add --transport http aigamelabs https://aigamelabs.net/mcp. The default --scope project writes .gemini/settings.json in the repo; -s user writes ~/.gemini/settings.json for all your projects.
  2. OAuth is automatic for servers with OAuth discovery: on first use the CLI detects the 401, discovers the authorization/token endpoints from server metadata, performs dynamic client registration, and opens a browser for sign-in (aigamelabs uses Google login + consent). No oauth block, authProviderType, or header is needed.
  3. Manage authentication in the session with /mcp auth: it lists servers requiring authentication, and /mcp auth aigamelabs signs in or re-authenticates when tokens expire.
  4. Verify with /mcp in the session, which shows each server's tools, prompts, and resources.

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

Add the server (shell)

gemini mcp add --transport http aigamelabs https://aigamelabs.net/mcp
# add -s user to write ~/.gemini/settings.json instead of the project file

settings.json entry

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

Before you connect
  • Gemini CLI keys Streamable HTTP servers as httpUrl in settings.json (url is the SSE field) — gemini mcp add --transport http writes httpUrl for you.
  • The OAuth flow requires a local browser and a localhost callback (http://localhost:<port>/oauth/callback), and Gemini CLI enforces RFC 9207: the authorization server must return the iss parameter, which is validated against the discovered issuer.
  • No --trust flag is used here; tool calls stay behind Gemini CLI's normal confirmation prompts, and the mcp.allowed/mcp.excluded settings can restrict which servers connect.

Step 2 · Workflow

Add the publishing skill

  1. Save the skill to .gemini/skills/aigamelabs-game-publishing/SKILL.md in the project — Gemini CLI also discovers the .agents/skills alias, so a folder shared with Codex works unchanged.
  2. Run /skills list in the session to confirm discovery, and /skills reload to refresh the list without restarting; gemini skills list does the same from the terminal.
  3. Ask for a task that matches the description (e.g. publish my game); Gemini asks for permission to activate the skill, then follows its instructions.

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