Summer Engine in Zed
Zed is a fast, AI-powered code editor that supports MCP (Model Context Protocol) through its Agent Panel. With Summer Engine’s integration, Zed’s AI can control your game engine: add nodes to scenes, set properties, import assets, run the game, and debug, all from within your coding workflow. This guide covers the configuration. Setup takes about a minute.Prerequisites
- Zed: The high-performance editor with built-in AI
- Node.js 22+: For running the MCP server
- Summer Engine: Open with your project, for engine work only
- Sign in once:
npx -y summer-engine@latest login. One browser sign-in also connects the store, publishing and Grow tools
Configuration
Zed usescontext_servers in its settings. You can add Summer Engine via:
- Settings file:
~/.config/zed/settings.json(or$XDG_CONFIG_HOME/zed/settings.jsonon Linux) - Project-level:
.zed/settings.jsonin your project root (create via zed: open project settings) - UI: Agent Panel → Settings → Add Custom Server
Step 1: Open Settings
PressCmd+, (Mac) or Ctrl+, (Linux/Windows), or run zed: open settings from the Command Palette. For project-specific config, run zed: open project settings to create .zed/settings.json.
Step 2: Add Summer Engine
Add thecontext_servers entry. If it already exists, add summer-engine to the object:
Step 3: Restart Zed
Close and reopen Zed so it loads the new config. The Summer Engine MCP server starts when Zed starts; it connects to the engine on the first tool call.Step 4: Verify
- Open the Agent Panel (top-right menu or Command Palette)
- Go to Settings and check the context servers list
- A green dot next to summer-engine means it’s active
- Try a prompt: “Use Summer Engine to add a MeshInstance3D with a BoxMesh to the scene”
Using Summer Engine with Zed
Once configured, the AI can use Summer Engine’s tools when you ask for game-related changes. Example prompts:- “Add a Camera3D and DirectionalLight3D to the scene root”
- “Get the scene tree from Summer Engine”
- “Import this model and add it to the World node: [URL]”
- “Run the game and capture a screenshot”
- “Set the project’s main scene to res://main.tscn”
Troubleshooting
”Summer Engine is not running” (engine_not_running)
Start Summer Engine and open your project. The MCP server connects to the engine’s local API on port 6550. The engine writes a token to ~/.summer/api-token when it starts.
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 or red dot
- Config path: Verify settings are in
~/.config/zed/settings.jsonor.zed/settings.jsonin your project - JSON validity: Ensure no trailing commas, proper quotes, and valid JSON structure
- Restart: Fully quit and reopen Zed
Tools return errors
See Value formats for parameter formats. Common issues: wrong node path format (./World/Player), invalid property values (use engine string format like "Vector3(0, 10, 0)"), or the game running when scene edits are attempted (stop it first with summer_stop).
Next Steps
Operations reference
Every operation with its inputs and an example
Building a Game
How an AI builds a full game using MCP
MCP Setup Overview
Architecture, prerequisites, 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.

