Skip to main content

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.
Fastest path. npx -y summer-engine@latest setup cursor --yes writes the config below into ~/.cursor/mcp.json, installs the skill library to ~/.agents/skills (Cursor reads this agentskills.io folder), and runs summer doctor. It also adds the Summer Games MCP (summer-games: friends, parties and messages as you); choose Connect next to it in Cursor’s MCP settings to sign in. The steps that follow are the manual version of the same thing.

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.json in your project root (recommended, stays with the project)
  • User-level: ~/.cursor/mcp.json (global, applies to all projects)
Create the file if it doesn’t exist. If it does, add the 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

  1. Open Cursor Settings (Cmd+, or Ctrl+,)
  2. Go to MCP (or search for “MCP”)
  3. You should see summer-engine listed, with its tools available
If you don’t see it, check that the JSON is valid (no trailing commas, proper quotes) and that the file path is correct.

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
Engine tools (scenes, scripts, play, screenshots) need the local server above. After 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”
Engine tools need the engine. Open your project in Summer Engine first, or run npx summer-engine run from the project directory. Asset, plan, store and publishing tools do not need it.

Troubleshooting

”Summer Engine is not running” (engine_not_running)

The MCP server can’t connect to the engine. Fix:
  1. Open Summer Engine and load your project
  2. Or run npx summer-engine run from the project folder
  3. Wait a few seconds for the engine to start, then try your request again
Every Summer error names its code and one next step (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.json must 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 ./Root depending on your scene.
  • Engine not ready: Some operations require the game to be stopped. Use summer_stop before making scene changes.
  • Invalid value format: Properties like position need 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.