Godot MCP vs Summer Engine
A side-by-side look at the Godot MCP and Summer Engine MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Godot MCP for gaming work as a local process; choose Summer Engine for gaming as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Godot MCP when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- You want tools like
launch_editor, run_project, get_debug_output.
Choose Summer Engine when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 69/100 · Great | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 498 | 88 |
| Directory activity | 8 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 154 | Not listed |
| Full listing | View Godot MCP | View Summer Engine |
Tools & capabilities
Godot MCP tools 154
launch_editorLaunch Godot editor for a specific projectrun_projectRun the Godot project and capture outputget_debug_outputGet the current debug output and errorsstop_projectStop the currently running Godot projectget_godot_versionGet the installed Godot versionlist_projectsList Godot projects in a directoryget_project_infoRetrieve metadata about a Godot projectcreate_sceneCreate a new Godot scene fileadd_nodeAdd a node to an existing sceneload_spriteLoad a sprite into a Sprite2D nodeexport_mesh_libraryExport a scene as a MeshLibrary resourcesave_sceneSave changes to a scene file- +142 more on the listing page
Summer Engine tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Godot MCP
{
"mcpServers": {
"godot-mcp-4": {
"command": "npx",
"args": [
"-y",
"@tugcantopaloglu/godot-mcp"
]
}
}
}
Summer Engine
{
"mcpServers": {
"summer-2": {
"command": "npx",
"args": [
"-y",
"summer-engine@latest"
]
}
}
}
Frequently asked questions
Godot MCP is categorized under Gaming and uses a local stdio subprocess. Summer Engine belongs to Gaming and uses a local stdio subprocess. Pick Godot MCP for gaming work and Summer Engine for gaming.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Godot MCP has no declared pricing — check the project's own site. Summer Engine has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add godot-mcp-4 and summer-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Godot MCP has a quality signal of 69/100 (Great) with 8 views, 0 installs and 498 GitHub stars. Summer Engine has 45/100 (Fair) with 0 views, 0 installs and 88 GitHub stars.