Skip to main content
The Summer Engine MCP gives an agent 189 tools: 93 run only in the summer-engine npm MCP on your computer, 84 only on the hosted MCP at https://mcp.summerengine.com/mcp, and 12 on both. The npm MCP mounts the hosted tools after summer login --store, so a local agent sees one server. The hosted tools listed are the ones every signed-in Summer account gets; tools the hosted server adds only behind a deployment setting are left out. Set it up in MCP setup; for publishing step by step, see Create and publish your game.
Generated from the tools’ own definitions: the summer-engine npm package 3.4.1 (its MCP server’s tools/list, library/tools/*/resource.yaml and registry/generated/index.json in SummerEngine/summer) and the hosted Summer Engine MCP (src/lib/mcp/hosted at commit cfcdc04b75). If something here is wrong, the tool definition is wrong.

What a tool needs

Hosted tools that spend credits say so in their description. Cost depends on the models and voices you choose. Your dashboard shows spend as it happens, and your limits cap it.

Value formats

Engine properties such as position, rotation_degrees and mesh take engine string syntax, not JSON objects. Node paths start with ./ from the scene root: ./World/Player is the Player child of World. Every scene change names its scene with scenePath, such as res://main.tscn; the scene does not need to be the open editor tab.

Tools by task

Build

Scenes, nodes, scripts, project files, the planning board and Summer Studio. All 75 tools in detail.

Create assets

Generate and find images, 3D models, audio, video and motion, then import them into the project. All 43 tools in detail.

Run and test

Play the game, drive input, read the runtime, take screenshots and read errors. All 34 tools in detail.

Publish

Export, upload builds, write the store page and ask the owner to publish. All 29 tools in detail.

Grow

See how your published game is doing. All 8 tools in detail.

Prompts

MCP prompts the servers offer next to the tools.