
Summer Engine MCP
Make real gamesin Claude Code.
Connect a supported AI agent or local model to Summer Engine. Use the AI plan you already have to build, run, and test a Summer game locally; exports still depend on the target templates and toolchains you install.
Agent guides
How to make games in Claude Code, Cursor, and more
What it is
A desktop engine your agent can actually operate.
How it works
1. Download the engine
Install the Summer Engine desktop app. This is where the scene tree, runtime, assets, and exports live.
2. Set up MCP
Run the CLI setup command. It writes the agent config, installs skills, and connects to the local engine API.
3. Build with your agent
Claude Code, Cursor, and other MCP clients get 44 engine tools for real game development.

Playable, not pretend
Your AI subscription writes. Summer shows the game.
Why it feels different
Your agent stops guessing and starts using the engine.
Claude Code, Cursor, and Devin Desktop already write code. Summer gives that code a real game engine: open the scene, place objects, run the project, inspect errors, and repeat until the loop is playable.
Agent guides
How to make games in Claude Code, Cursor, and more.
Each guide gets its own page so the setup and SEO match what people are actually searching for.
How to make games in Claude Code with Summer Engine
How to make games in Cursor with Summer Engine
How to make games in Codex with Summer Engine
How to make games in Devin Desktop with Summer Engine
How to make games in Gemini CLI with Summer Engine
How to make games in Cline with Summer Engine
How to make games in Kilo Code with Summer Engine
How to make games in OpenCode with Summer Engine
How to make games for free with local LLMs in Summer Engine
How to make games with Ollama and Summer Engine
How to make games in LM Studio with Summer Engine
How to make games in Goose with Summer Engine
FAQ
Practical answers.
- What is Summer Engine?
- Summer Engine is a real desktop game engine for agent-led game development: an editor, scene tree, runtime, assets, exports, and local diagnostics. You build and run a Summer game inside the engine instead of stopping at files generated in a chat window.
- What does MCP add?
- MCP gives your AI agent a controlled bridge into the running engine. Through 44 tools, it can create scenes, add nodes, set properties, run the game, inspect errors, and import or generate assets instead of only editing files blindly.
- What does the CLI do?
- The summer-engine CLI downloads the desktop app, signs you in, writes the MCP config for Claude Code, Cursor, Codex CLI, Devin Desktop, Gemini CLI, LM Studio, Kilo Code, and other agents, installs the game-dev skills, creates projects, runs them, and checks that everything is connected.
- Can I use a free local model instead of a subscription?
- Yes. Run a model on your own GPU with Ollama or LM Studio and connect it through the same MCP server. Engine control and asset search stay free; cloud generation uses credits. See the Ollama, LM Studio, and Goose guides for the setups that actually work in 2026.
- Can games made with Summer be exported?
- Summer projects can be run and tested locally. Export availability depends on the installed target templates and toolchains; signing, store review, and submission remain creator-controlled.
- Is Summer Engine free?
- Yes. Summer Engine is free to download and start using. The CLI, MCP server, skills, hooks, and plugin manifests are MIT open source. Heavy hosted AI and cloud generation features use credits. See /source-status for the exact open, free, and paid split.
Build the first playable version in the engine, not in a chat box.
Download Summer Engine for free, connect MCP, and tell your agent what to make.