Summer Engine MCP guide
How to make games in Kilo Code with Summer Engine
Connect Kilo Code to Summer Engine and give it local engine tools for scenes, scripts, assets, Play mode, and errors. Works with cloud or local models. Summer Engine is the desktop game engine; Kilo Code is the agent that drives it through MCP.
Summer is free for MCP use
Download the desktop engine and connect it to your agent. You are not paying Summer for the AI calls your existing subscription already covers.
Open Kilo Code
Use the AI editor you already have. The setup command writes the MCP config and installs the Summer game-dev skills.
Run a Summer game
The agent writes code. Summer Engine shows the Summer game, runs Play mode, and helps inspect errors. Export still requires the target templates and toolchains.
Install
Connect Summer to Kilo Code
- 1
Install Summer Engine
Downloads the desktop engine app, about 1 GB. Skip it if Summer Engine is already installed, or if you only need assets and video for a game built in another engine.
- 2
Sign in
Opens your browser once. The CLI and the engine share the session.
- 3
Connect Kilo Code
Writes the summer-engine MCP config and installs the Summer game-dev skills.
- 4
Restart and build
Restart Kilo (CLI or the VS Code extension) so it reloads kilo.json.
Setup notes
The 2026 specifics.
Coming from Roo Code?
Roo Code shut down in May 2026; Kilo Code is the maintained successor. The setup command writes the Summer server to Kilo’s MCP config (project scope uses .kilocode/mcp.json). Kilo also runs local models through Ollama — set the context window to 32k or higher in the provider settings.
Why this matters
Kilo Code writes with your subscription. Summer Engine shows the game.
A chat agent alone can write files. With MCP, Kilo Code gets tools for the running game engine, so it can inspect the project, run commands, and make changes that become playable inside Summer.