Connect your agent

This page connects Claude Code or Codex to the platform. It assumes you finished Install and are in the game-platform folder. When you finish, your agent can create a game, run it, and read this wiki on its own.

What you get

The studio plugin gives your agent an MCP server and two skills. The server runs from the checkout you installed, and it gives the agent the following tools:

• Scaffold: create a game from a template, and add a behaviour, an entity, a scene, a panel or a shader to it.
• Playtest: run the game in Chromium with no window, press keys, take screenshots, and read the console.
• Simulate: step the game’s world headless and read its state.
• Wiki: read and search this wiki, and list the engine’s components, the assets and the templates.
• Jev: ask TypeSafe’s Jev typed questions, on your own API key.

The MCP server’s README lists every tool.

The plugin adds the following commands and skills:

• /studio:new-game creates a game from a template.
• /studio:game-builder builds a game with you one step at a time, asking one question per step.
• /studio:wiki answers a question from this wiki and names the pages it read.

Claude Code

The repository is a plugin marketplace. Add it once, then install the plugin from it:

claude plugin marketplace add "$PWD"
claude plugin install studio@game-platform

Start a new Claude Code session in the game-platform folder, so that it loads the plugin. An agent that ran these commands for you asks you to do this, then to say continue. The new session picks up at Verify the connection and does not clone again.

To try the plugin in one session without installing it, start Claude Code with the plugin loaded:

claude --plugin-dir packages/plugin

Codex

Start Codex in the game-platform folder, and trust the folder when Codex asks. The repository’s .codex/config.toml then runs the server, with no more setup. An agent that cloned the repository for you asks you to restart Codex there, then to say continue.

To use the skills from any folder, link them into your own skills folder once:

mkdir -p ~/.agents/skills
ln -s "$PWD/packages/plugin/skills/game-builder" "$PWD/packages/plugin/skills/wiki" ~/.agents/skills/

Outside the repository, Codex also needs the server added. Copy codex.toml into your ~/.codex/config.toml. That entry runs @daniel-zarinski/mcp from the registry. The registry does not hold that package yet, so start Codex in the game-platform folder instead.

Verify the connection

Ask your agent the following:

List the game templates.

The agent calls the list_templates tool, and its answer names the example template. If the agent says it has no such tool, see Troubleshooting. Once it answers, make your game.

Troubleshooting

The following table lists what goes wrong most often:

What you see	What to do
The agent has no list_templates tool.	Build the server with pnpm nx build @daniel-zarinski/mcp, then start a new session.
A tool fails with an error about $schema or another field.	The server is older than the repository. After each git pull, build it again with pnpm nx build @daniel-zarinski/mcp, then start a new session.
Claude Code does not list studio in /plugin.	Run the two claude plugin commands again from the game-platform folder.
A playtest fails and names a missing browser.	Run pnpm exec playwright install chromium in the game-platform folder.
pnpm install in a new game fails with a 401 from GitHub Packages.	Add a token with the read:packages scope to ~/.npmrc, as Install shows.
Codex outside the repository cannot find @daniel-zarinski/mcp.	Start Codex in the game-platform folder until the package publishes.