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

LM Studio

Native MCP + OAuthSkill used as reference

LM Studio is an MCP host with native OAuth: add the server URL in mcp.json, log in via the browser window, and LM Studio registers itself through the server's dynamic client registration — no static tokens or bridge needed. It has no native skills feature, so the publishing skill is reference-only.

Step 1 · Tools

Connect the MCP server

  1. Use a current LM Studio build: MCP hosting ships since 0.3.17, and OAuth-backed MCP ("add your integration, log in via browser") is documented in the current integrations docs.
  2. In the app, switch to the "Program" tab in the right-hand sidebar, click Install > "Edit mcp.json", and merge the aigamelabs entry into the existing mcpServers object (LM Studio follows Cursor's mcp.json notation — copy only the inner entry, not a whole new file).
  3. Save the file. LM Studio opens a browser window for the server's authorization page; sign in with Google and consent to the games:read and games:write scopes. LM Studio registers itself via dynamic client registration and stores the token securely.
  4. The server's tools then appear like any other MCP server — enable them for your chat and use a local model that supports tool calling.

mcp.json entry (merge fragment)

{
  "mcpServers": {
    "aigamelabs": {
      "url": "https://aigamelabs.net/mcp"
    }
  }
}

Before you connect
  • No "auth" object is needed because the server supports dynamic client registration. Only if a server lacks DCR does LM Studio's documentation say to add auth credentials, with the OAuth app callback http://127.0.0.1:33389/mcp-oauth-callback — do not paste static bearer tokens into headers for this server.
  • The docs route setup through the in-app mcp.json editor rather than documenting a fixed on-disk path; edit it there so LM Studio picks up the change.
  • Tool calls consume real tokens: the docs warn that MCP servers can overflow small local-model contexts, so prefer a tool-capable model with adequate context.

Step 2 · Workflow

Add the publishing skill

  1. LM Studio documents no native agent-skills system (no SKILL.md discovery or skill import), so the skill cannot be installed natively.
  2. Download the Markdown from https://aigamelabs.net/mcp/skills/SKILL.md.
  3. Attach the file to the chat, or paste the relevant workflow as chat context, and instruct the model to follow it when calling the aigamelabs tools.
  4. This is on-demand reference context only — the instructions are not auto-loaded and the model may ignore them unless you point at 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.