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

Continue

OAuth bridge requiredSkill used as reference

Open-source VS Code/JetBrains coding assistant. Documents Streamable HTTP remote MCP but no OAuth for mcpServers, so OAuth needs a labeled bridge; it has no SKILL.md skills feature — Markdown rules are the documented equivalent.

Step 1 · Tools

Connect the MCP server

  1. MCP tools work in Agent mode only. Install Node.js 18+ (the bridge runs via npx) and create the block file .continue/mcpServers/aigamelabs.yaml at the top level of your workspace.
  2. Use the fragment below: the aigamelabs entry is a local stdio server that mcp-remote bridges to https://aigamelabs.net/mcp.
  3. Connect: mcp-remote opens the aigamelabs sign-in in your browser (Google login + consent for games:read, games:write, optional offline_access) and caches tokens under ~/.mcp-auth.
  4. Verify in Agent mode that the aigamelabs tools (add_game, update_game, list_games, get_game, upload/release workflow) appear, or run the standalone check command below.

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

.continue/mcpServers/aigamelabs.yaml — standalone block file (name/version/schema required)

.continue/mcpServers/aigamelabs.yaml
name: Aigamelabs MCP
version: 0.0.1
schema: v1
mcpServers:
  - name: aigamelabs
    type: stdio
    command: npx
    args:
      - -y
      - mcp-remote
      - https://aigamelabs.net/mcp

One-off login / connectivity check (runs the full OAuth flow and lists tools)

npx -p mcp-remote@latest mcp-remote-client https://aigamelabs.net/mcp

Before you connect
  • Continue has no documented OAuth support for MCP servers: the config.yaml reference lists only name, command, args, env, cwd, requestOptions and connectionTimeout for mcpServers, so a direct Streamable HTTP connection to this OAuth-only server is not documented as usable. The bridge below is explicitly third-party; revisit if Continue documents MCP OAuth.
  • mcp-remote is a locally run third-party Node package (Node ≥ 18) that performs MCP OAuth discovery with DCR + PKCE over a loopback HTTP callback (accepted by this server for native clients) and caches tokens in ~/.mcp-auth.
  • Do not set apiKey or Authorization headers manually: the bridge obtains and refreshes a per-user OAuth access token; there is no shared API key.

Step 2 · Workflow

Add the publishing skill

  1. Continue has no SKILL.md / Agent Skills discovery; its documented mechanism for reusable instructions is Markdown rules, joined into the system message for Agent, Chat and Edit requests.
  2. Download https://aigamelabs.net/mcp/skills/SKILL.md and save it as .continue/rules/aigamelabs-game-publishing.md at the project root. The file's frontmatter (name, description) is valid rule frontmatter; add alwaysApply: false so the agent pulls it in based on the description instead of attaching it to every request.
  3. Be clear about what this is: a rule used as reference material, not an auto-loaded skill — there is no on-demand metadata + load-on-match behavior like Cline, Roo Code or Kilo Code skills.
  4. Ask in Agent mode to follow the aigamelabs-game-publishing rule when publishing games.

Save the skill Markdown as a Continue rule (bash)

.continue/rules/aigamelabs-game-publishing.md
mkdir -p .continue/rules && curl -fsSL https://aigamelabs.net/mcp/skills/SKILL.md -o .continue/rules/aigamelabs-game-publishing.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.