# Claude Code game development with a real engine attached

> Claude is a strong programmer, but it cannot see your game. Connect it to Summer and it can build scenes, write scripts, run the game, read the errors and look at the result.

- URL: https://www.summerengine.com/claude-code-game-development
- Keyword: claude code game development

**The short answer:** Claude Code game development works best when Claude can operate the engine, not just write files. The Summer MCP gives Claude Code more than 80 tools to inspect and edit scenes, write GDScript, play the game, send input, read runtime state and errors, take screenshots, and generate 3D, image and audio assets. Setup is one command, `npx -y summer-engine@latest setup claude-code --yes`.

Claude Code can write a player controller in seconds. What it cannot do on its own is open your project, see that the character falls through the floor, and fix the collision layer. Without an engine connection, you become the eyes, running the game, describing what broke and pasting errors back.

Summer closes that loop. It is a desktop game engine compatible with Godot 4 projects, with an MCP server that exposes the editor and the running game to your agent. Claude edits the scene tree, attaches scripts, presses play, sends input, reads frame-stamped state and screenshots, and reads the debugger. Then it fixes what it finds.

You keep your Claude subscription and your terminal. Summer adds the engine, the game-specific skills and the asset generators.

## What it does

- **Scenes and nodes:** Read the scene tree, add and remove nodes, set properties, instance scenes, connect signals and save.
- **Scripts and errors:** Write and edit GDScript files, then read script errors, debugger errors and warnings before claiming a fix works.
- **Run and probe the game:** Play and stop the game, send scripted input, step frames, and read frame-stamped runtime state and screenshots.
- **See the result:** Editor and game screenshots, world snapshots and before and after diffs, so Claude checks visuals instead of guessing.
- **Generate assets:** Images, sprite sheets, 3D models with rigs and motion, voice, sound effects and music, imported straight into the project.
- **Game skills library:** Searchable skills, examples and templates that teach Claude engine-specific patterns, from platformer movement to multiplayer state.

## How it works

1. **Install Summer:** Download the free Summer desktop app for macOS (Apple silicon) or Windows and open or create a project.
2. **Connect Claude Code:** Run `npx -y summer-engine@latest setup claude-code --yes`. It registers the Summer MCP with Claude Code. Sign in with `npx summer-engine login` when asked.
3. **Describe the game:** Ask Claude for a feature in plain language. It reads the project context and the relevant skill before building.
4. **Let it verify:** Claude runs the game, checks diagnostics and screenshots, and iterates until the feature works. You review the diff.

## In Studio, or from the agent you already use

### In Summer Studio

Prefer not to use a terminal? The Summer desktop app has its own built-in agent with the same engine tools, and Studio on the web covers asset generation. Claude Code and the in-app agent work on the same project files.

[See the Claude Code setup guide](https://www.summerengine.com/mcp/how-to-make-games-in-claude-code)

### From Claude, Cursor or Codex via MCP

After setup, Claude Code sees the summer_* tools automatically. A good first request asks Claude to read the project context, build something small, run it and report what it verified.

Example prompt for your agent:

```text
Read the Summer project context, then add a double jump to the player with coyote time. Run the game, send a jump input twice, check the player reaches the upper ledge in the probe, and show me a screenshot.
```

[Set up the Summer MCP](https://www.summerengine.com/mcp)

## What Claude Code can and cannot do with Summer today

| Task | Status | Notes |
| --- | --- | --- |
| Edit scenes, nodes and scripts | Yes | Needs the Summer desktop app open on the same machine |
| Run the game and read errors | Yes | Play, stop, input, frame stepping, diagnostics |
| Look at the game | Yes, as still frames | Screenshots and snapshots; no video recording tool yet |
| Generate 3D, images and audio | Yes | Works without the engine open; needs a paid plan or top-up |
| Use from claude.ai in the browser | Not yet | The Summer MCP runs locally; there is no hosted web connector today |
| Sign and submit to stores | You do this | Exports depend on installed templates; signing and store submission stay with you |

## What it costs

- Image, Nano Banana 2 Lite (1K): $0.04 (estimate)
- 3D model, Hunyuan 3D v3.1 Pro: $0.53
- Sound effect, 5 seconds: $0.01

Engine and project tools through the MCP are free. You pay Anthropic for Claude as usual. Only asset generation draws on a Summer plan or top-up.

Prices are charged from your Summer usage balance. Generating assets needs a paid plan or a top-up: Pro is $20 a month and includes $20 of usage, and top-ups start at $5. The desktop engine itself is free to download.

## Prompts that work, and what comes back

Requests that show what an engine-connected Claude can do in one session.

### Fix a physics bug

- Prompt: The player sometimes falls through moving platforms. Reproduce it, find the cause and fix it.
- What you get: Claude runs the game with scripted input, reads the runtime state at the failing frame, adjusts the collision setup and reruns to confirm.

### Build a feature end to end

- Prompt: Add a shop NPC with three items, a coin counter in the HUD and a buy sound.
- What you get: New scenes and scripts, a generated sound effect, HUD nodes, and a playtest to check the purchase flow.

### Populate a level

- Prompt: Generate five low poly rocks and two trees and scatter them around the spawn area without blocking the path.
- What you get: Generated 3D assets, placed on the terrain with collision checks, plus a screenshot of the result.

### Tune game feel

- Prompt: The jump feels floaty. Make it snappier and show me before and after.
- What you get: Adjusted gravity and jump values with probe readings and screenshots from both versions.

[Browse Summer skills](https://www.summerengine.com/skills)

## Why an engine connection beats file edits alone

Games fail in ways that are invisible in code, such as a node in the wrong place, a signal never connected, a sprite scaled to zero, a script that compiles but never runs. An agent that can only edit files has to guess. An agent that can run the game and read its state can check.

Summer's tools are built around that check. Runtime probes return frame-stamped state, so Claude can compare before and after an action. Diagnostics surface runtime errors that never reach the console. Screenshots confirm the visual result.

## Open source agent layer

The Summer CLI, MCP server, skills and plugin manifests are MIT open source. The desktop app is free to download. Hosted AI, asset generation and cloud features are paid Summer services.

## Frequently asked questions

### Can Claude Code make a full game?

Claude Code can build and iterate on a complete game when it can operate an engine. With Summer it edits scenes and scripts, runs the game and fixes what breaks. You still direct the design and review the result.

### How do I connect Claude Code to Summer?

Install the Summer desktop app, then run `npx -y summer-engine@latest setup claude-code --yes` in a terminal. The command registers the MCP server with Claude Code; sign in with `npx summer-engine login`.

### Does it work with Godot projects?

Summer is compatible with Godot 4 projects, so Claude works with standard scenes and GDScript. Check the compatibility guidance for your project before a large migration.

### Do I need a Summer subscription?

Not for engine work. The engine and the project tools are free. Asset generation needs a paid Summer plan or a top-up. Claude itself is billed by Anthropic.

### Does it work in Cursor or Codex too?

Yes. The same MCP installs into Cursor, Codex, Gemini CLI, Cline and other agents. See the MCP guides for each.

### Can Claude see the game running?

Yes, through screenshots, runtime probes and snapshots of the running game. It works with still frames; there is no video recording tool yet.

### Can I use it from claude.ai in the browser?

Not today. The Summer MCP runs locally next to the engine, so it works with desktop and terminal agents such as Claude Code.

## Related tools and guides

- [How to make games in Claude Code](https://www.summerengine.com/mcp/how-to-make-games-in-claude-code)
- [Claude for Godot](https://www.summerengine.com/blog/claude-for-godot)
- [Godot MCP servers guide](https://www.summerengine.com/blog/godot-mcp-servers-guide)
- [Cursor for Godot](https://www.summerengine.com/cursor-for-godot)
- [Godot copilot](https://www.summerengine.com/godot-copilot)
- [Summer CLI](https://www.summerengine.com/cli)
- [Summer for AI agents](https://www.summerengine.com/for-ai)
- [AI 3D model generator for games](https://www.summerengine.com/ai-3d-model-generator-for-games)

[Set up the Summer MCP](https://www.summerengine.com/mcp)

---

## Machine-readable resources

- Site index for agents: https://www.summerengine.com/llms.txt
- Full inlined content: https://www.summerengine.com/llms-full.txt
- Porting catalog: https://www.summerengine.com/llms-porting.txt
- Structured catalog: https://www.summerengine.com/agent-catalog.json
- Sitemap: https://www.summerengine.com/sitemap.xml
- Developer resources: https://www.summerengine.com/docs
- Summer API (assets from any agent or code; public per-call model prices): https://docs.summerengine.com/api