How to make a game with Claude Code and ship it

Step 01Create the app

Create the app once on Create or in the dashboard. The agent works with apps that already exist in your account and finds them by name. You can skip the AI coder there and go straight to Claude Code. The agent can also create a new app itself with create_title, if you allow "Create new apps" when signing in.

Step 02Connect the two MCP servers

In a terminal:

claude mcp add --transport http idosgames https://site.idosgames.com/api/v2/mcp
claude mcp add idosgames-registry -- npx -y @idosgames/mcp

The first one is remote: it reads and changes your apps, generates assets and deploys builds. The second one runs on your machine: it gives the agent the project scaffold, ready modules and a skill for every part of the SDK.

Restart Claude Code, run /mcp and sign in to "idosgames" in the browser window that opens. You choose which apps the agent may touch. No API keys, nothing to paste into config files. All options are in building with AI agents over MCP.

Step 03Start the project with a skill

Ask Claude Code:

Load the skill idosgames-getting-started and build my app "Coin Arena": a top-down arena where the player dodges projectiles and collects coins. Phaser, neon style.

The agent finds the app, scaffolds the project from the SDK and puts the game inside the lobby. Sign-in, profile, inventory, friends, invites, quests and mail are already there. How the pieces fit: SDK overview.

A tip from our own use: keep the first request to one mechanic, exactly like in the AI coder. Claude Code will happily build five systems in one go, and you will spend the evening finding which one broke the other four.

Step 04Add game systems in plain words

When you ask for something the platform has, the agent installs the ready system instead of writing a backend:

• "Add a leaderboard by best score with weekly resets."
• "Add a store with three coin packs and a daily deal."
• "Let friends play together in a room."
• "Give a reward for logging in seven days in a row."

Settings such as prices, rewards and quest goals live on the server and are changed over MCP, without a new build. That is handy later: you can retune the economy of a live game with one sentence.

Step 05Generate art, sound and 3D

The remote server generates images, sound effects, music, video and 3D models, and puts them where the game needs them:

Generate a sprite for the player ship, an enemy drone and a looping synthwave background track, and use them in the game.

Generations spend the AI credits of your plan, then your Aspis. Ask the agent to run estimate_media_cost first if you want the price before anything is spent. For a 3D game it can also make a model, give it a skeleton and put ready idle, walk and run animations from the platform library on it.

Step 06Test, then deploy

Build the game, upload the build to the test copy and give me the link.

The test copy opens at {id}-dev.idos.games. Play it on your phone, fix what feels wrong, then:

Deploy the tested build to players.

The game goes live at {id}.idos.games. The build you tested is the build players get: nothing is rebuilt on deploy, and a rollback is one click in the dashboard. When you are ready for strangers, publish the game to the idosgames.com catalog. Details: publishing.