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

Open WebUI

Native MCP + OAuthNative agent skill

Self-hosted, multi-user web UI (MCP since v0.6.31). An admin registers the server once with OAuth 2.1 (DCR); every user then connects their own account. Skills are imported natively as markdown via Workspace > Skills.

Step 1 · Tools

Connect the MCP server

  1. Admin: open Settings > Admin > Integrations and, under External Tool Servers, click + Add Connection.
  2. Set Type to MCP (Streamable HTTP) — not OpenAPI — and enter the URL https://aigamelabs.net/mcp.
  3. Set Auth to OAuth 2.1 (the Dynamic Client Registration mode — no client ID/secret to paste). Leave OAuth Scopes on "Use discovered scopes" (the server advertises games:read games:write) and OAuth Resource Parameter on Automatic, then click Register Client and Save.
  4. Each user connects their own account: in a chat, click + > Integrations > Tools, enable the aigamelabs tool, and finish the Google login + consent redirect in the same browser, signed in as that user.
  5. Admins can connect their own account from the saved connection via the Authorize OAuth button (appears once a client is registered and the connection saved).

Settings > Admin > Integrations > External Tool Servers — field values

Type:        MCP (Streamable HTTP)
URL:         https://aigamelabs.net/mcp
Auth:        OAuth 2.1          (DCR — leave Client ID/Secret empty)
ID:          aigamelabs
Name:        AI Game Labs
OAuth Scopes: Use discovered scopes
OAuth Resource Parameter: Automatic
→ Register Client, then Save

Before you connect
  • MCP servers are admin-only in Open WebUI by design; regular users cannot add their own, and the admin scopes who sees the server with Access Control (per user or group).
  • Docker deployments must set WEBUI_SECRET_KEY: without it, stored OAuth tokens fail to decrypt after every container restart ("Error decrypting tokens") and users must re-authenticate.
  • Native MCP support is Streamable HTTP only (no stdio/SSE), and OAuth 2.1 tools must not be set as default/pre-enabled model tools — the interactive consent cannot run mid-request, so users enable the tool per chat.

Step 2 · Workflow

Add the publishing skill

  1. Download the skill file from https://aigamelabs.net/mcp/skills/SKILL.md.
  2. Import: Workspace > Skills → open the chevron menu beside Create → Import JSON → select the downloaded .md. Frontmatter name/description pre-fill the editor; review and save (Skills access is private by default — share via Access if others need it).
  3. Use: type $ in chat to inject the full skill, toggle it per chat under + > Skills, or bind it to a model in Workspace > Models — bound skills lazy-load through view_skill with native function calling.

Download the skill for import, then import it in Workspace > Skills

curl -fL -o aigamelabs-game-publishing.SKILL.md https://aigamelabs.net/mcp/skills/SKILL.md
# Then: Workspace > Skills > chevron beside Create > Import JSON > select the file

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.