Summer Engine in Cursor
Summer is the game engine built for AI. Cursor is an AI code editor that supports MCP. With Summer Engine’s MCP integration, you can build games without leaving Cursor: the AI adds nodes to your scenes, sets properties, imports assets, runs the game, and debugs errors, all through the same chat you use for code. This guide walks you through two setup options: a one-click install link (when supported) and manual configuration, which always works.Option 1: One-Click Install
Cursor supports MCP install deeplinks. Click the link below to add Summer Engine to your MCP servers:Add Summer Engine to Cursor
Click to install Summer Engine MCP (opens Cursor)
If the link doesn’t work: Cursor’s deeplink format may change. Use Option 2 (manual config). It takes about 30 seconds and is reliable.
Option 2: Manual Configuration
Manual setup gives you full control and works in all Cursor versions.Step 1: Create or Edit MCP Config
Cursor reads MCP servers from one of these locations:- Project-level:
.cursor/mcp.jsonin your project root (recommended, stays with the project) - User-level:
~/.cursor/mcp.json(global, applies to all projects)
summer-engine entry to the existing mcpServers object.
Step 2: Add the Summer Engine Config
Step 3: Restart Cursor
Close and reopen Cursor so it loads the new MCP config. The MCP server starts when Cursor starts; it doesn’t connect to the engine until you first use a Summer Engine tool.Step 4: Verify
- Open Cursor Settings (Cmd+, or Ctrl+,)
- Go to MCP (or search for “MCP”)
- You should see summer-engine listed, with its tools available
Cloud work only: connect by URL
For assets, plans, the store, publishing and Grow, with nothing to install, add the hosted Summer server with Add to Cursor, or add it to~/.cursor/mcp.json yourself, then sign in when Cursor asks:
~/.cursor/mcp.json
summer login, the local server also runs the cloud tools, so use one of the two.
Using Summer Engine in Cursor
Once configured, the AI has access to Summer Engine’s tools. You don’t need to mention “Summer Engine” in every message. If the AI knows you’re building a game and the tools are available, it will use them when appropriate. Example prompts:- “Add a Camera3D and DirectionalLight3D to the scene”
- “Get the current scene tree so I can see the structure”
- “Import this model: https://example.com/tree.glb and add it under the World node”
- “Run the game and take a screenshot of what the player sees”
- “Set the main scene to res://main.tscn”
Troubleshooting
”Summer Engine is not running” (engine_not_running)
The MCP server can’t connect to the engine. Fix:
- Open Summer Engine and load your project
- Or run
npx summer-engine runfrom the project folder - Wait a few seconds for the engine to start, then try your request again
next). not_signed_in: run npx -y summer-engine@latest login. no_credits: add credits at https://www.summerengine.com/studio/credits. All codes: How Summer answers.
MCP server not appearing
- Check the config path:
.cursor/mcp.jsonmust be in the project root (the folder you opened in Cursor) - Validate JSON: Use a JSON validator. A single missing comma or extra comma will break it
- Restart Cursor: Fully quit and reopen, not just reload the window
Tools return errors
If a specific tool fails, its error names one next step (next): do that step. retry says if the same call can run again. Common causes:
- Wrong node path: Paths use
./prefix (e.g.,./World/Player). The root is./or./Rootdepending on your scene. - Engine not ready: Some operations require the game to be stopped. Use
summer_stopbefore making scene changes. - Invalid value format: Properties like
positionneed engine string format:"Vector3(0, 10, 0)"not{x: 0, y: 10, z: 0}. See Value formats for format details.
Next Steps
Operations reference
Every operation with its inputs and an example
Building a Game
Step-by-step: how an AI builds a full game with MCP
MCP Setup Overview
Prerequisites, architecture, and other IDEs
CLI Reference
summer install, run, create, and more
Need help? Ask in Discord first. That is where you get the fastest reply and support. For concrete help, email support@summerengine.com or founders@summerengine.com.

