MCP Setup

One Command, Any Agent

npx -y summer-engine@latest setup <agent> --yes

Replace <agent> with the id from the table below (cursor, claude-code, codex, …). The command does three things:

Writes the MCP server entry into the agent’s own config file, in that agent’s file shape. Existing servers in the file are kept.
Installs the Summer skill library where that agent reads skills (see Skills). Most agents share one folder, ~/.agents/skills, so one setup covers several agents.
Runs summer doctor so you see immediately whether Node, the engine and the login are in place.

Add --scope project to write project-level files that travel with the game, --print to see the config without writing, --dry-run to see the plan. Re-run with --force after upgrading Summer to refresh the skills.

What You Get

Summer Engine’s MCP (Model Context Protocol) server lets the agent control the engine directly: read the scene tree, add nodes, set properties, import assets, run the game, capture screenshots, read errors. Instead of switching between your editor and Summer Engine, you stay in one place and describe what you want. The MCP tools use the same engine operations as Summer Engine’s built-in chat (AddNode, SetProp, SaveScene, ImportFromUrl). The difference is where you type. Undo works the same. Changes are just as safe. Lazy connection. The MCP server starts immediately and connects to the engine on the first tool call. If the engine is not running you get a clear error: “Summer Engine is not running. Open it first, or run: npx summer-engine run.” Start the engine, try again.

Prerequisites

Summer Engine: the desktop app from summerengine.com or npx summer-engine install
Node.js 18+: the MCP server runs with npx
A Summer Engine project open in the engine, so the local API server is active

The engine runs a local HTTP server on localhost:6550 while it is open and writes a token to ~/.summer/api-token. No API keys to manage.

Supported Agents

Every id summer setup accepts, with the file it writes and where the skills land. Agents with their own guide are linked; the rest are on Every Supported Agent with the exact snippet.

Agent	`summer setup` id	MCP config it writes	Skills folder
Claude Code	`claude-code`	`~/.claude.json` / `.mcp.json` (project)	`~/.claude/skills` / `.claude/skills`
Claude Desktop	`claude-desktop`	`~/Library/Application Support/Claude/claude_desktop_config.json`	none (MCP only)
Codex	`codex`	`~/.codex/config.toml` / `.codex/config.toml` (project)	`~/.agents/skills` (shared) / `.agents/skills`
Cursor	`cursor`	`~/.cursor/mcp.json` / `.cursor/mcp.json` (project)	`~/.agents/skills` (shared) / `.agents/skills`
Devin Desktop (formerly Windsurf)	`windsurf`	`~/.codeium/windsurf/mcp_config.json`	`~/.agents/skills` (shared) / `.agents/skills`
Antigravity	`antigravity`	`~/.gemini/config/mcp_config.json` / `.agents/mcp_config.json` (project)	`~/.gemini/config/skills` / `.agents/skills`
Cline (VS Code)	`cline`	`~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`	`~/.cline/skills` / `.cline/skills`
Cline CLI	`cline-cli`	`~/.cline/data/settings/cline_mcp_settings.json`	`~/.cline/skills` / `.cline/skills`
Kilo Code	`kilo-code`	`~/.config/kilo/kilo.json` / `kilo.json` (project)	`~/.kilo/skills` / `.kilo/skills`
GitHub Copilot CLI	`github-copilot`	`~/.copilot/mcp-config.json` / `.mcp.json` (project)	`~/.copilot/skills` / `.github/skills`
GitHub Copilot in VS Code	`vscode-copilot`	`~/Library/Application Support/Code/User/mcp.json` / `.vscode/mcp.json` (project)	`~/.agents/skills` (shared) / `.agents/skills`
GitHub Copilot in Visual Studio	`visual-studio`	`~/.mcp.json` / `.mcp.json` (project)	none (MCP only)
GitHub Copilot in JetBrains IDEs	`copilot-jetbrains`	`~/.config/github-copilot/intellij/mcp.json`	none (MCP only)
OpenCode	`opencode`	`~/.config/opencode/opencode.json` / `opencode.json` (project)	`~/.agents/skills` (shared) / `.agents/skills`
Zed	`zed`	`~/.config/zed/settings.json`	`~/.agents/skills` (shared) / `.agents/skills`
Kiro	`kiro`	`~/.kiro/settings/mcp.json` / `.kiro/settings/mcp.json` (project)	`~/.kiro/skills` / `.kiro/skills`
Goose	`goose`	`~/.config/goose/config.yaml`	`~/.config/agents/skills` / `.agents/skills`
Hermes Agent	`hermes`	`~/.hermes/config.yaml`	`~/.hermes/skills` / `.agents/skills`
Trae	`trae`	`.trae/mcp.json` (project)	none (MCP only)
Qwen Code	`qwen-code`	`~/.qwen/settings.json` / `.qwen/settings.json` (project)	`~/.qwen/skills` / `.qwen/skills`
Kimi Code CLI	`kimi-code`	`~/.kimi-code/mcp.json` / `.kimi-code/mcp.json` (project)	`~/.agents/skills` (shared) / `.agents/skills`
Crush	`crush`	`~/.config/crush/crushrc` / `.crushrc` (project)	`~/.agents/skills` (shared) / `.agents/skills`
Amp	`amp`	`~/.config/amp/settings.json`	`~/.agents/skills` (shared) / `.agents/skills`
Factory Droid	`factory`	`~/.factory/mcp.json` / `.factory/mcp.json` (project)	`~/.agents/skills` (shared) / `.agents/skills`
Junie	`junie`	`~/.junie/mcp/mcp.json` / `.junie/mcp/mcp.json` (project)	none (MCP only)
Warp	`warp`	`~/.warp/.mcp.json` / `.warp/.mcp.json` (project)	`~/.agents/skills` (shared) / `.agents/skills`
Rovo Dev CLI	`rovo-dev`	`~/.rovodev/mcp.json`	`~/.agents/skills` (shared) / `.agents/skills`
Qoder CLI	`qoder`	`~/.qoder/settings.json` / `.mcp.json` (project)	`~/.qoder/skills` / `.qoder/skills`
Grok Build	`grok-build`	`~/.grok/config.toml` / `.grok/config.toml` (project)	`~/.agents/skills` (shared) / `.agents/skills`
Mistral Vibe	`mistral-vibe`	`~/.vibe/config.toml` / `.vibe/config.toml` (project)	`~/.vibe/skills` / `.agents/skills`
LM Studio	`lm-studio`	`~/.lmstudio/mcp.json`	none (MCP only)

Legacy ids still work but warn: gemini (Gemini CLI, retired for individual accounts on 2026-06-18; use antigravity) and roo-code (shut down 2026-05-15). Aliases: claude → claude-code, devin → windsurf, agy → antigravity, copilot → github-copilot, vscode → vscode-copilot, droid → factory, kilo → kilo-code, qwen → qwen-code, kimi → kimi-code.

Manual Configuration

If you would rather edit files yourself, or your agent is not listed, these are the shapes in use. summer setup <agent> --print prints the exact one for any agent.

{
  "mcpServers": {
    "summer-engine": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "summer-engine@latest", "mcp"]
    }
  }
}

{
  "servers": {
    "summer-engine": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "summer-engine@latest", "mcp"]
    }
  }
}

{
  "mcp": {
    "summer-engine": {
      "type": "local",
      "command": ["npx", "-y", "summer-engine@latest", "mcp"],
      "enabled": true
    }
  }
}

{
  "context_servers": {
    "summer-engine": {
      "command": "npx",
      "args": ["-y", "summer-engine@latest", "mcp"],
      "env": {}
    }
  }
}

[mcp_servers.summer-engine]
command = "npx"
args = ["-y", "summer-engine@latest", "mcp"]

extensions:
  summer-engine:
    type: stdio
    name: summer-engine
    cmd: npx
    args: ["-y", "summer-engine@latest", "mcp"]
    enabled: true
    timeout: 300

Windows. npx is a shell shim, and hosts that spawn it directly fail with ENOENT. summer setup writes "command": "cmd.exe", "args": ["/c", "npx", "-y", "summer-engine@latest", "mcp"] on Windows; do the same by hand.

No global install required. npx -y summer-engine@latest mcp runs the current release on demand. For faster startup install globally (npm install -g summer-engine) and use "command": "summer", "args": ["mcp"].

Verify It Works

Start Summer Engine: open your project in the engine (or run npx summer-engine run from the project directory).
Restart the agent so it reloads its MCP config. summer setup prints the exact step for your agent.
Check the MCP list: in Cursor, Settings > MCP; in Claude Code, /mcp. You should see summer-engine connected with its tools.
Ask the AI: “Use Summer Engine to add a MeshInstance3D with a BoxMesh to the scene root. Name it TestCube.”
Confirm in the engine: the node appears in the scene tree.

summer doctor checks all of this from the terminal, including whether the agent’s recorded config still points at a current Summer release.

What the AI Can Do

The MCP server exposes tools in these categories:

Category	What they do
Scene	Add nodes, set properties, save/open scenes, connect signals, instantiate prefabs, inspect nodes and resources
Debug and Play	Run the game, read console output, get diagnostics, script and debugger errors
Visual Verification	Screenshot the viewport or the running game
Project	Project context, settings, input mappings, scene tree, import assets from URLs
Project Files	Read, write, and patch script and resource files inside the bound project
Asset Library	Search the public library and your assets, then import
Generation	Generate images, 3D models, audio, video, and motion clips, slice sprite sheets, and poll job status
Navigation	Open the right page on summerengine.com or the right surface in the editor for the user (`summer_open`)
Publishing	Export the game, upload builds, edit the store page and ask the owner to publish

For a full reference with parameters and examples, see the Tools Reference. For a step-by-step guide on how an AI agent builds a complete game using these tools, see Building a Game with MCP.

Next Steps

Every Supported Agent

Config file, file shape and skills folder for all agents

Skills

The skill library and where each agent reads it

CLI Reference

All CLI commands: setup, doctor, install, run, create, and more

Tools Reference

Every MCP tool with parameters and usage examples

Need help or have questions? Reach out to our founders at founders@summerengine.com or join our community on Discord for fast responses.

Overview

Summer Games MCP

Setup

CLI

Reference

One Command, Any Agent

What You Get

Prerequisites

Supported Agents

Manual Configuration

Verify It Works

What the AI Can Do

Next Steps

Every Supported Agent

Skills

CLI Reference

Tools Reference

​One Command, Any Agent

​What You Get

​Prerequisites

​Supported Agents

​Manual Configuration

​Verify It Works

​What the AI Can Do

​Next Steps

Every Supported Agent

Skills

CLI Reference

Tools Reference

One Command, Any Agent

What You Get

Prerequisites

Supported Agents

Manual Configuration

Verify It Works

What the AI Can Do

Next Steps