Summer Engine MCP
The summer-engine package links an agent to the Summer game engine: MCP server, game-dev skills and a CLI to build and publish.
- 103 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- After sign-in an agent can spend credits, publish games and change prices until you turn those rights off in Studio.
- The local server runs the engine, scripts and builds on your machine.
Install
- Works in
Manual install
npx -y summer-engine@latest devThe first README command: creates a starter project and asks before installing the engine app.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- After sign-in an agent can spend credits, publish games and change prices until you turn those rights off in Studio.
- The local server runs the engine, scripts and builds on your machine.
This is third-party code. Review the repository files before installing.
What it does
The repository has three parts. The `summer mcp` MCP server drives a running editor: builds scenes, writes scripts, plays the game, takes screenshots and reads errors. Skills cover game-dev techniques: movement, combat, multiplayer, effects, audio, UI and level design. The `summer` CLI installs the engine, signs in, sets up the agent, creates projects from templates and publishes games. After `summer login` cloud operations open up: asset generation, plans, the summer.games store, prices and analytics. A hosted server at `https://mcp.summerengine.com/mcp` needs no install. The `.summer/` folder holds project memory so a fresh agent resumes where the last stopped.
Who it is for. Indie game developers and hobbyists who ask an agent to build, test and release a game on the Summer engine.
Good fit when
- An agent builds a scene and scripts in the editor and runs the game to check them.
- A multiplayer mode with matchmaking, leaderboards and world saves is added to a game.
- Assets such as sound effects, music and 3D models are generated through the cloud server.
- A game is published to the store with a private preview link.
Not a fit when
- The game is built on Godot or Unity rather than Summer Engine.
- An agent must not spend credits or publish without your approval.
- You cannot install the engine app of about 660 MB.
Example request
Create a platformer with a double jump, run it, take a screenshot and show console errors.MCP
- Transport
- stdio, http
- Authentication
- OAuth
Limitations
The engine itself is not in the repository: the CLI downloads the free Summer Engine app. Needs Node 22 or newer. Cloud operations require a Summer account and credits, and generation and paid builds spend them. The Studio permission switches by default let an agent build, spend credits, publish and change prices without asking. ChatGPT and the Claude directory use separate reviewed versions with a fixed tool list, without publishing or billing links.
How to disable. Run `claude mcp remove summer-cloud` for the cloud server and remove the local `summer` entry from the agent configuration. In Studio, under Agent permissions, turn off publishing and spending.
FAQ
How do I connect Summer Engine to Claude Code?
For the cloud run `claude mcp add --transport http summer-cloud https://mcp.summerengine.com/mcp` and sign in through `/mcp`. For the local engine use `npx -y summer-engine@latest setup <agent> --yes`.
Can I skip MCP?
Yes. `summer setup --cli` installs the skills and the agent calls `summer` as ordinary shell commands. Needs summer-engine 4.2.0 or newer.
What can an agent do without asking?
Six Studio switches decide that. Permanent deletion and emailing people are off by default and require approval through a link.
How does operation search work?
`summer ops search "publish my game"` finds any operation, including when not signed in.
Which agents can connect?
Claude Code, Codex, Cursor, VS Code, Devin Desktop (formerly Windsurf), Claude Desktop and claude.ai through a custom connector.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server and plugin for Godot 4.4+: the agent edits scenes and scripts in the editor, runs the game and reads errors
An MCP server for Unreal Engine: control assets, actors, the editor, sequencer and blueprints
An MCP server that lets an agent control the Unreal Engine editor in words: actors, blueprints, node graphs, camera
A Unity plugin with an MCP server, skills and CLI: the agent drives scenes, assets, scripts and tests in the Unity Editor
An MCP server inside the Unity Editor: the agent builds scenes and scripts, enters play mode and checks the game with screenshots
Official PlayCanvas Editor MCP server: 130 tools for scenes, entities, scripts, assets and runtime checks with screenshots
README in short
One npm package, `summer-engine`, bundles the server, skills and CLI. Software installs only after explicit user confirmation, and a linter bars library entries from sending agents to the network, credentials or package managers.