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

Goose

Native MCP + OAuthNative agent skill

Open-source agent (CLI + desktop) with a native "Remote Extension (Streamable HTTP)" type, automatic OAuth (metadata discovery, DCR/CIMD, PKCE, keyring) and Agent-Skills support.

Step 1 · Tools

Connect the MCP server

  1. Run goose configure and choose Add Extension → "Remote Extension (Streamable HTTP)".
  2. Name it aigamelabs and enter the Streamable HTTP endpoint URI: https://aigamelabs.net/mcp (accept the default 300 s timeout).
  3. First use of an aigamelabs tool triggers OAuth automatically: Goose discovers the authorization server, registers via DCR/CIMD and opens the browser for Google login + consent; tokens are stored in the OS keyring.
  4. Or skip the wizard: run a one-off session with goose --with-streamable-http-extension "https://aigamelabs.net/mcp", or merge the YAML fragment below into your config.yaml.
  5. There is no "goose mcp add" subcommand — configuration lives in config.yaml or the configure wizard.

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

Merge fragment — config.yaml

~/.config/goose/config.yaml
extensions:
  aigamelabs:
    type: streamable_http
    name: aigamelabs
    enabled: true
    uri: "https://aigamelabs.net/mcp"
    timeout: 300

One-off session without editing config

goose --with-streamable-http-extension "https://aigamelabs.net/mcp"

Before you connect
  • OAuth is native and key-based-free: docs state remote streamable_http extensions "normally obtain a client ID automatically, using Client ID Metadata Documents or Dynamic Client Registration", with PKCE and a loopback callback; manual client_id keys only exist (v1.47.0+) for servers rejecting both.
  • Goose takes OAuth scopes from the server's advertised metadata when none are configured, which matches this server's games:read / games:write model.
  • SSE remote extensions are no longer supported — use type streamable_http (this server is Streamable HTTP).

Step 2 · Workflow

Add the publishing skill

  1. Download the skill into a documented skills directory: https://aigamelabs.net/mcp/skills/SKILL.md → .agents/skills/aigamelabs-game-publishing/SKILL.md (project) or ~/.agents/skills/... (global; project discovery exists since v1.18.0).
  2. Goose's built-in skills platform extension auto-discovers SKILL.md folders at session start and activates them when relevant.
  3. List what was picked up with goose skills list (v1.38.0+) or /skills in a session.

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

Verify Goose skill discovery

goose skills list

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.