Connect your AI to your arcade

1. Add Arcade Boss to your AI by its address (recipes below). There is nothing to copy but the URL.
2. Your AI opens the Arcade Boss sign-in page. Sign in with your email or Google — a new email makes a new account and its arcade — and press Allow.

A sign-in can see your arcade and its games, start projects and publish drafts to your Builds. It cannot spend your energy, change your account, email or friends, or ship to the floor. Every signed-in app is listed under 🗃 Builds → 🔌 Connect → Connected with Revoke, and Sign out everywhere ends them all at once.

No browser? A plugin key

On a machine that can't open a sign-in page (CI, a container), use a plugin key instead: 🔌 Connect → your AI → In Terminal → No browser? Use a key makes one and copies the whole command. A key is shown once and is a password: keep it out of chat text and shared documents. Keys are listed and revoked in the same place.

Claude (chat, desktop and phone)

1. In Claude, open Settings → Connectors → Add custom connector.
2. Name it Arcade Boss, enter https://arcadeboss.com/mcp as the URL, and press Add.
3. Press Connect beside it. Claude opens the Arcade Boss sign-in; sign in and press Allow.

Then, in any chat with the connector on: “Build me a one-button runner for my arcade.”

Claude Code

The Arcade Boss plugin lives in the public marketplace jbmatter/arcadeboss-plugins. It brings the build skill and the /arcade:… commands, and signs in with OAuth.

In the Claude app

Install in Claude

If that button doesn't open Claude, add it by hand:

1. In Claude, open Customize → Plugins.
2. Choose Add marketplace, pick GitHub repo, and enter jbmatter/arcadeboss-plugins.
3. Find Arcade Boss in the list and press Install.
4. In a new Claude Code chat, type /arcade:connect. Claude sends you a sign-in link: open it, sign in and press Allow. (Claude Code's own /mcp → arcade → Authenticate does the same.)

In Terminal

claude plugin marketplace add jbmatter/arcadeboss-plugins
claude plugin install arcade@arcadeboss

Then in Claude Code type /arcade:connect and open the sign-in link Claude sends. With no browser on the machine, add the server with a key instead:

claude mcp add --transport http arcade-key https://arcadeboss.com/mcp --header "Authorization: Bearer <your plugin key>"

Updating

claude plugin marketplace update arcadeboss
claude plugin update arcade@arcadeboss

Then “/arcade:build a one-button runner where you jump over saws”. /arcade:revise changes a game you already have, and /arcade:convert ./my-game brings in a game you made somewhere else.

Codex (the ChatGPT app, CLI, IDE)

Same marketplace, jbmatter/arcadeboss-plugins.

In the ChatGPT app

1. Open Plugins in the left sidebar.
2. Press Add → Add a marketplace. Under Source enter jbmatter/arcadeboss-plugins and press Add marketplace.
3. Open the Personal tab, find Arcade Boss, and press +. Installing opens the Arcade Boss sign-in; sign in and press Allow.

In Terminal

codex plugin marketplace add jbmatter/arcadeboss-plugins
codex plugin add arcade@arcadeboss
codex mcp add arcade --url "https://arcadeboss.com/mcp?via=codex"

The last line detects the sign-in and opens it in your browser (codex mcp login arcade --no-browser prints the link for a browser on another machine). With no browser at all, use a key:

export ARCADE_PLAYER_TOKEN=<your plugin key>
codex mcp add arcade-key --url "https://arcadeboss.com/mcp?via=codex" --bearer-token-env-var ARCADE_PLAYER_TOKEN

Updating

codex plugin marketplace upgrade
codex plugin add arcade@arcadeboss

Then “$arcade build me a one-button runner where you jump over saws”. $arcade-convert ./my-game brings in a game you made somewhere else.

ChatGPT

1. Turn on Developer mode in ChatGPT's settings.
2. Open Plugins → Add → Create MCP App. Enter https://arcadeboss.com/mcp as the Server URL, choose OAuth for authentication, and press Create.
3. ChatGPT opens the Arcade Boss sign-in; sign in and press Allow.

Then add the app from a chat's tools menu and describe a game. Builds arrive as a card with Walk in and Playtest buttons.

Meta Muse (the app)

Muse builds the connector itself on its own machine, and its credential store is made for a key: make one under 🔌 Connect → Meta Muse. Say this to Muse, and paste the key into its secure credential prompt when it asks — never into the chat:

Build a custom connector to my Arcade Boss arcade. It is a remote MCP server over
streamable HTTP at https://arcadeboss.com/mcp?via=muse — authenticate with a Bearer
token I'll give you in the credentials prompt. Docs: https://arcadeboss.com/docs/mcp
Save it as a skill so I can ask you to build and revise games in my arcade later.

Then: “Build me a one-button endless runner for my arcade.” Muse writes the game on its VM, verifies and publishes it through the connector, and hands you the walk-in link.

Muse Code (Meta's terminal agent)

Add the server to ~/.config/muse/settings.json, with a key from 🔌 Connect → Muse Code:

{
  "schema_version": 1,
  "mcp_servers": {
    "arcade": {
      "transport": "streamable_http",
      "url": "https://arcadeboss.com/mcp?via=muse-code",
      "headers": { "Authorization": "Bearer ${ARCADE_PLAYER_TOKEN}" },
      "enabled": true
    }
  }
}

Muse Code reads Claude Code skill folders, so muse skills import --from claude after installing the Claude Code plugin brings the build workflow across.

Arcade Boss is its own authorization server, built to the MCP authorization spec (2026-07-28).

Tool	What it does
get_arcade	Your arcade's name, visit link and counts. Creates the arcade on first call if you have none.
list_games	Every game you own, grouped by lineage: title, developer, score, current version, what is on a bench.
get_game_source	A game's files plus the contract it was built under (multiplayer, saves, orientation), a version stamp for safe revisions, and demo: whether the cabinet's demo still fits.
create_project	Starts a new game from a brief and its contract declarations. Writes no files.
verify_game	The dry run: a contract lint, then a real boot on desktop and on a phone viewport. With attract, it also plays the cabinet's demo for two seconds. Never writes.
look_game	Screenshots of the game in play at several viewports, for the AI to look at its own work.
publish_game	The one writer: verifies and lands the files as the next version of a game, as a draft in your 🗃 Builds and on a free developer's bench. Takes the cabinet's demo as attract.

When a game ships, the arcade records a few seconds of it playing itself and shows the clip on its cabinet. The AI that wrote the game can write that demo too. The demo is a patch, never part of the game. The arcade applies it only to a private copy it records from.

• attract (on verify_game and publish_game): search/replace blocks against the game's files, in the form <<<<<<< SEARCH … ======= … >>>>>>> REPLACE. A FILE: <path> line goes before the blocks for any file other than index.html. The patched game must declare window.ATTRACT = function () { … }, which starts a round at once with an autopilot playing. 64 KB at most.
• verify_game with attract applies it, calls ATTRACT, plays about two seconds and answers attract: { applies, ok, started, reachedPlay, pictureMoved, screens, distinctFrames, reason?, note }. These are the same checks the launch recording makes. The answer never changes the game's own ok.
• publish_game with attract stores a demo that applies beside the new version (demoSaved: true). A demo that doesn't apply gets demoSaved: false and demoRefused with the reason, and the publish still lands.
• demo ("fits", "stale" or "none") is on every get_game_source and publish_game reply, and on a verify_game with a gameId and no attract. It answers whether a demo the arcade holds still applies to those files. On "fits" no new demo is needed. With none, the arcade writes one itself when the game ships.

• Own arcade only. A sign-in or a key reaches the arcade of the account it belongs to. There is no access to anyone else's games.
• Every publish is a draft. A published game lands on a bench for you to playtest. A game that other players are already playing keeps serving until you ship the new version yourself, inside the arcade.
• There is no ship tool. Releasing a game to your floor, the critic's review and the store listing all happen in the arcade, by you. The connector ends at the walk-in link.
• Publishing is never unverified. A game that fails its checks still lands as a draft, and the result says so in capitals, so the AI cannot report it as done.
• Every game must be playable with touch alone and with keyboard and mouse. The verify step tests both.

A free Arcade Boss account bound to a verified email. One arcade per account. Building spends credits: new accounts receive a starter grant when they verify their email, and more can be bought as credit packs. During the pre-launch period sign-ups are admission-gated by a daily quota and invite codes. No regional restrictions.

Questions, or a reviewer's invite code: hello@arcadeboss.com.