> ## Documentation Index
> Fetch the complete documentation index at: https://docs.summerengine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Build Games in Devin Desktop with Summer Engine MCP

> Connect Summer Engine's MCP server to Devin Desktop (formerly Windsurf) and build games with Devin Local controlling your engine.

## Summer Engine in Devin Desktop

Devin Desktop (formerly Windsurf) is an AI-powered IDE that supports MCP (Model Context Protocol). With Summer Engine's integration, Devin Local (formerly Cascade) — Devin Desktop's agent panel — 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

* **Devin Desktop**: The Cognition-powered IDE (formerly Windsurf)
* **Node.js**: For running the MCP server (Node 18+)
* **Summer Engine**: Installed and running with your project open

## Configuration

Devin Desktop uses the same MCP config format as Cursor. The config file location may vary by version; common locations include:

* **Project-level:** `.cursor/mcp.json` or `.windsurf/mcp.json` in your project root
* **User-level:** `~/.cursor/mcp.json` or `~/.windsurf/mcp.json`

<Note>
  **Check Devin Desktop docs.** MCP config paths can change between versions. If the paths above don't work, check Devin Desktop's documentation or the in-app MCP settings for the correct config file location.
</Note>

### Step 1: Create or Edit the Config File

Create the MCP config file in your project root or user config directory. If the file already exists (e.g., for other MCP servers), add Summer Engine to the existing `mcpServers` object.

### Step 2: Add Summer Engine

Use the one-line setup command:

```bash theme={null}
npx -y summer-engine@latest setup windsurf --yes
```

`setup devin` works as an alias and produces the same result.

Or add the config manually:

<CodeGroup>
  ```json New file theme={null}
  {
    "mcpServers": {
      "summer-engine": {
        "command": "npx",
        "args": ["summer-engine", "mcp"]
      }
    }
  }
  ```

  ```json Adding to existing mcpServers theme={null}
  {
    "mcpServers": {
      "other-server": { ... },
      "summer-engine": {
        "command": "npx",
        "args": ["summer-engine", "mcp"]
      }
    }
  }
  ```
</CodeGroup>

### Step 3: Restart Devin Desktop

Close and reopen Devin Desktop so it loads the new MCP config. The Summer Engine MCP server starts when Devin Desktop starts; it connects to the engine on the first tool call.

### Step 4: Verify

Check Devin Desktop's MCP or AI settings to confirm "summer-engine" appears and its tools are listed. Then try a prompt:

* "Use Summer Engine to add a MeshInstance3D with a BoxMesh to the scene"

If the node appears in Summer Engine, the setup is working.

## Using Summer Engine with Devin Desktop

Once configured, Devin Local 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"

<Tip>
  **Engine must be running.** Devin Local talks to Summer Engine over localhost. Open your project in the engine first, or run `npx summer-engine run` from the project directory.
</Tip>

## Troubleshooting

### "Summer Engine is 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.

### MCP server not appearing

* **Config path:** Verify you're using the config file Devin Desktop actually reads. Check the app's MCP settings or documentation.
* **JSON validity:** Ensure no trailing commas, proper quotes, and valid JSON structure
* **Restart:** Fully quit and reopen Devin Desktop

### Tools return errors

See the [Tools Reference](/mcp/tools-reference) 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

<CardGroup cols={2}>
  <Card title="Tools Reference" icon="wrench" href="/mcp/tools-reference">
    Every MCP tool with parameters and examples
  </Card>

  <Card title="Building a Game" icon="gamepad-2" href="/mcp/building-a-game">
    How an AI builds a full game using MCP
  </Card>

  <Card title="MCP Setup Overview" icon="plug" href="/mcp/setup">
    Architecture, prerequisites, and other IDEs
  </Card>

  <Card title="CLI Reference" icon="terminal" href="/mcp/cli-reference">
    summer install, run, create, and more
  </Card>
</CardGroup>

***

Need help or have questions? Reach out to our founders at [founders@summerengine.com](mailto:founders@summerengine.com) or join our community on [Discord](https://discord.gg/yUpgtxnZky) for fast responses.