Summer

Name: Summer
Author: Summer - The AI Game Engine

Drives the Summer Engine game editor, with Summer's cloud assets and store reached by search

Official · Summer - The AI Game Engine TypeScript Remote (hosted) · Streamable HTTP Local · stdio Developer tools Media

GitHub npm Website

64 popularity score ★ 93 ↓ 1.8k/wk

Connect your client

Remote (hosted)

Add in one click

Add to LM Studio Add to Goose

Opens the app, which asks before it adds the server.

Or add it by command or config

Claude Codeterminal, then /mcp in Claude Code to sign in

claude mcp add --transport http summer-cloud https://mcp.summerengine.com/mcp

Codexterminal, then codex mcp login summer-cloud

codex mcp add summer-cloud --url https://mcp.summerengine.com/mcp

Cursorunder mcpServers in ~/.cursor/mcp.json

"summer-cloud": { "url": "https://mcp.summerengine.com/mcp" }

VS Codeterminal

code --add-mcp '{"name":"summer-cloud","type":"http","url":"https://mcp.summerengine.com/mcp"}'

devin desktop~/.config/devin/mcp_config.json

"summer-cloud": { "serverUrl": "https://mcp.summerengine.com/mcp" }

Claude (desktop and web)Settings, Connectors, Add custom connector

https://mcp.summerengine.com/mcp

Local (npm)

Add in one click

Add to Cursor Add to VS Code Add to LM Studio Add to Goose

Opens the app, which asks before it adds the server.

Or add it by command or config

Claude CodeTerminal

claude mcp add summer -- npx -y summer-engine mcp

Claude Desktopclaude_desktop_config.json

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

Cursor~/.cursor/mcp.json

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

VS Code.vscode/mcp.json

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

Codex~/.codex/config.toml

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

Gemini CLITerminal

gemini mcp add --scope user summer npx -- -y summer-engine mcp

Settings 6

Set together: tool selection
`SUMMER_PROFILE`	Optional: Tool profile: full, engine (kept under 128 tools for VS Code Copilot) or assets (no engine tools). Same as --profile. Default `full`.
`SUMMER_TOOLSETS`	Optional: Comma list of toolsets to add to the profile, or legacy to list the 3.x tool names. Same as --toolsets.
`SUMMER_SURFACE`	Optional: v4 lists engine tools plus summer_search and summer_call, v3 the 3.x tools. Same as --surface. Default `v4`.
`SUMMER_ENGINE_PROJECT`	Optional: Path of the project whose running editor the engine tools bind to. Same as --project. For engine tools.
`SUMMER_ENGINE_INSTANCE_ID`	Optional: Binds the engine tools to one exact editor instance. Same as --instance. For engine tools.
`SUMMER_MCP_DEBUG`	Optional: Set to 1 for verbose per-call logs.

What it does

This is the local MCP server in the `summer-engine` npm package, made by the team behind Summer Engine, a desktop game engine built on Godot. Your client starts it with `summer mcp` and it talks over stdio to the engine app's local API. That gives an agent the editor itself. It can open a project, patch scripts and scene files with sha256 guards, add and move nodes, and run GDScript in the live editor. When the game runs, it can send input and read live node state alongside screenshots.

Version 4 changed how the list looks. Engine tools keep their old names, but Summer's cloud work now sits behind two entry points. You describe a job to `summer_search`, which answers with matching operations and their input schemas (five by default and twenty at most, per src/mcp/ops-surface.ts). Then `summer_call` runs the chosen one. That covers asset generation, store uploads and pricing, and it still accepts any 3.x tool name. Calls that spend money, publish or change something live return `needs_approval` with a link for the person to open. Once you sign in, some hosted tools are mounted into the list directly as well.

The same team runs a hosted server at mcp.summerengine.com/mcp that carries only the cloud side. It has no engine tools at all. For assets or store work without the 660 MB engine download, that address is the lighter choice.

What it needs

To run it yourself	Node.js 22+
Runs on	macOS, Windows, Linux
Summer	Free tierEngine tools work signed out. Cloud operations need a Summer account, and generation spends prepaid credits.
Also	Summer Engine app running with a project open, for the engine tools Blender installed, for summer_fabricate_3d

Get the CLI with `npm install -g summer-engine` or `brew install summerengine/tap/summer`. Running `npx -y summer-engine@latest dev` then fetches the engine app (about 660 MB) if it is missing and opens a starter project. `summer login` signs in to the account in the browser and then to the store. `summer login --store` repeats only the store step. Codex users of the hosted address finish sign-in with `codex mcp login summer-cloud`.

Limits

Limit The README's install playbook still checks for Node.js 20, while package.json at 4.8.0 requires Node 22 or newer
Not covered Engine tools answer engine_not_running until the engine app is open with a project
Early release Editor UI tools are a preview and need Summer Engine 0.5.66 or newer. Older builds answer engine_lacks_op
Cost Generation and paid builds spend Summer credits, and calls fail with no_credits when the balance runs out
Platform On Linux the engine app installs only on x86_64
Not covered Store uploads, going live and most cloud work are not listed tools by default. They run through summer_call, or as 3.x names with --toolsets legacy
Size cap jobs.wait waits at most 50 seconds per call, so a long generation job needs repeated waits
Not covered The hosted endpoint at mcp.summerengine.com/mcp has cloud operations only and no engine tools
Limit Version 4.9.0 on main, where games go live once their checks pass, is not yet released

Engine tools fail until the engine's local API answers; `summer run` waits up to 20 seconds and the docs give a polling loop for slower starts. The editor UI tools are marked preview and need Summer Engine 0.5.66 or newer; older engines return `engine_lacks_op`, and the engine refuses quit, project reload and delete-without-confirm actions. On the first tool listing the server waits up to 5 seconds for the hosted tools to mount; a slower mount adds them later through a list-changed notice. The README on main describes an `--assets-only` setup flag that the published 3.8.0 does not mention. Publishing is a preview and the Grow analytics stage is planned, not in the package.

Who it suits

It suits people building games in Summer Engine who want an agent working inside the editor, from scene edits to play tests to a store upload. Node 22 and the engine app are the cost of entry, and the engine tools alone need no account. For Godot projects outside Summer Engine it has nothing to offer. Someone who only wants generated assets or store and pricing work can add the hosted address instead and skip the local install. Chat with friends on summer.games is a separate server, summer-games, which setup adds next to this one.

Tools 49 of 130

18 only read, 28 change things, 3 can delete or overwrite. A ? marks an optional parameter.

summer_search: Finds a Summer operation from a plain description and returns its input schemaquery: stringarea?: stringlimit?: integer
summer_call deletes: Runs any Summer operation or 3.x tool by name, with approval links for paid or live changesop?: stringname?: stringinput?: objectdryRun?: booleanidempotencyKey?: string
summer_docs_search: Searches Summer's library of skills, templates and references by task
summer_docs_read: Loads one library entry, such as a skill's instructions or a tool recipe
summer_get_project_context: Summarises the open project, its scene and the notes kept under .summer
summer_projects_create_local changes: Writes a new project to disk from a starter template
summer_projects_open_local changes: Opens a project in the engine in the background and waits for it to connect
summer_write_file deletes: Creates a file or replaces one whole, guarded by the sha256 of the last read
summer_get_scene_tree: Reads the node tree of the current scene
summer_open_scene changes: Opens a given .tscn in the editor
summer_create_scene changes: Creates a new scene file
summer_instantiate_scene changes: Adds a scene or 3D model as a child node at a given position
summer_inspect_node: Reads one node's properties, optionally only named fields
summer_add_node changes: Adds a node to a scene file
summer_remove_node deletes: Removes a node from a scene file
summer_replace_node changes: Swaps a node for another scene or type while keeping its place and transform
summer_set_prop changes: Sets a typed property on a node in a scene file
summer_connect_signal changes: Wires a signal between two nodes and saves it in the scene
summer_project_setting changes: Changes a setting in project.godot
summer_input_map_bind changes: Binds an input action in the project's InputMap
summer_import_from_url changes: Downloads a model or image and runs it through the engine's import pipeline
summer_run_script changes: Runs a GDScript inside the live editor against the open scene
summer_run_editor_script changes: Runs an EditorScript in a headless editor against the project on disk
summer_api_docs: Looks up engine classes, methods and signals offline
summer_fabricate_3d changes: Runs a Blender Python script in the user's Blender and imports the model it exports
summer_ui_tree: Reads the live editor's interface as a tree of controls
summer_ui_activate changes: Presses, toggles or focuses one editor control
summer_get_runtime_tree: Reads the node tree of the running game
summer_snap_to_surface changes: Drops a node onto the first surface along a ray and saves
summer_place_adjacent changes: Places one node's bounds flush against another's
summer_play changes: Starts the game, optionally with a fixed seed or frame rate
summer_stop changes: Stops the running game
summer_game_probe: Reads live properties and a screenshot from one frame of the running game
summer_game_input changes: Sends timed key, mouse or action input to the running game
summer_runtime_set changes: Sets a property on a live node without touching the scene file
summer_screenshot: Captures the editor viewport or the game as an image
summer_shot_sheet: Renders several saved camera views as one labelled grid
summer_scene_audit: Checks a built scene for holes, gaps and other layout faults
summer_get_diagnostics: Sums up current errors and warnings
summer_get_console: Reads the engine's output panel
summer_get_debugger_errors: Reads runtime errors with stack traces
summer_import_asset changes: Searches Summer's asset library and imports the top match
summer_import_hdri changes: Finds a free Poly Haven sky and imports it into the project
summer_batch changes: Runs several scene operations as one transaction
summer_export_game changes: Exports the game in the bundle format the Summer Games store takes
summer_capture_gameplay: Records real gameplay frames without a running editor
summer_api_estimate: Quotes the exact price of one Summer API job without charging
summer_api_run changes: Runs one paid Summer API job into the person's assets
summer_enable_plugin changes: Enables an editor plugin and reports whether it loaded

Prompts 1

summer_agent_playbook: The working routine Summer expects an agent to follow in a session

Popularity

64 popularity score, on our list (the bar is 36)

★ 93 ↓ 1.8k/wk

GitHub stars	93	23.7 points
Stars in 30 days	+18	6.4 points
npm downloads, last week	1,774	26 points
Official server	Yes	8 points

Measured 2026-11-07. How the score works.

Where it is published

Code	summerengine/summer ★ 93
npm	summer-engine 4.9.1, 2026-10-28
Hosted	`https://mcp.summerengine.com/mcp` Streamable HTTP · OAuth sign-in

What it can reach

Runs	On your machine, or on the maker's servers
Reaches	Files on your machine, The internet, Your code, Your account at a service, Money or payments
Changes things	Yes: it can write, send, create or delete
Sign-in	OAuth sign-in for the hosted endpoint; none to run it yourself
Licence	MIT (npm)
Usage data	Sends it unless you turn it off (`SUMMER_NO_TELEMETRY=1 or DO_NOT_TRACK=1`) A first-run line with install id, command, client and OS, then tool name, outcome, error code and duration per call when signed in. No prompts, code, paths or arguments.
Last code change	2026-11-06

The server runs on your machine and reaches the Summer Engine app through its local API. Its tools read and write files in the open project and run GDScript in the editor. One of them runs Blender Python in your own Blender. Engine work needs no sign-in. After `summer login`, the session files sit in ~/.summer/, and cloud operations go to Summer's servers with them. Those can spend credits, upload builds and change store prices. Studio's agent permissions decide which of these run at once: deleting for good and contacting people are off by default, so such calls come back as needs_approval. No agent can change auto top-up.

Over time

GitHub stars 93 +18 (+24 %)

9375

13 Oct 20267 Nov 2026

npm downloads a week 1.8k +1.6k (+839 %)

5.8k5

9 Mar 20267 Nov 2026

Before the site measured it, read from npm's daily download counts.

Popularity score 64 +12 (+24 %)

6452

13 Oct 20267 Nov 2026

What is rising across the directory

Sources

Page checked 2026-10-26.

Badge for your README

Shows this server's rank in its category, and stars for a server that runs on your machine. It updates every hour.

MarkdownREADME.md

[![Summer on EveryMCPServer](https://everymcpserver.com/badge/summer-2.svg)](https://everymcpserver.com/servers/summer-2)

Connect your client

Add in one click

Or add it by command or config

Add in one click

Or add it by command or config

Settings 6

What it does

What it needs

Limits

Who it suits

Tools 49 of 130

Prompts 1

Similar servers

Summer

ai-rulez

Unity MCP

UE-MCP

EngineWire

Serena