Make a multiplayer game with Claude Code

01Why this path is different

Most backends expect you to read documentation, copy a snippet and wire it up. That is fine, and it is also the slowest part of building a small game.

Because the platform exposes a tool interface rather than only a docs site, an agent can do the wiring: create the game, define the room's shape, generate a client that matches it, and hand you a file to open. You review the result instead of assembling it.

02Connecting it

Sign up, copy your studio's secret key from the dashboard, and add the tool server to your agent's configuration. The dashboard shows a paste-ready configuration block with your key already in it.

The secret key is not the same as the publishable key that ships in your game. Keep the secret one out of your game's source and out of chat.

03What to ask for

Describe the game, not the API. The useful prompts sound like a brief:

• "Make a two-player tic-tac-toe I can share with a friend: take turns, show who won."
• "Build a top-down arena where everyone is a coloured square, arrow keys to move, and a leaderboard for eliminations."
• "Add saved progress so a returning player keeps their unlocks."

04Review the parts that matter

Agents are good at this and still worth checking on two points. First, whether anything that decides a winner runs on the server rather than in the browser, ask directly if the score can be edited by the client. Second, whether the client leaves the room on unload, because that omission shows up as duplicate players and is easy to miss when testing alone.

05Then share it

The output is an ordinary web page. Open it, open it again in a second window, and you are two players. Send the file or host it anywhere; there is no deployment step on our side, because the room already exists.

Common questions