MCP server that connects AI coding assistants to the Godot 4.2+ editor (scenes, nodes, scripts, ClassDB, playtests) via the companion
MCP server that connects AI coding assistants to the Godot 4.2+ editor (scenes, nodes, scripts, ClassDB, playtests) via the companion godot-mcp-toolkit plugin.
The number that says the most is 150+ operations. That is the real work on offer: create a node, paint a tilemap cell, key an animation track, read a live node mid-playtest, and roughly a hundred and fifty more. Those operations are packaged into up to 112 tools (an always-on core plus 28 on-demand groups), because a tool is a slot in your client's tool budget and an operation is a thing you can actually do. Related actions sit behind one tool, which keeps the list short while the operation count tells the honest story of breadth. Some operations are version-gated, so older Godot versions (down to
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| animation_authoring | Keyframes, tracks, and AnimationTree state machines |
| asset_ops | Asset listing, dependency queries, binary imports |
| audio | Audio buses, effects, and volume settings |
| classdb | Godot class hierarchy: properties, methods, signals, inheritance |
| cleanup | Deleting files, scripts, scenes, resources, folders; closing scenes |
| debugger | Debugger state, breakpoints, execution flow |
| editor_advanced | Editor screenshots, filesystem refresh, wait-for-idle |
| input_map | Input actions and their key/controller bindings |
| layer_naming | Physics, render, and navigation layer names |
| lsp_code_analysis | GDScript diagnostics, symbols, hover, project-wide compile check |
| lsp_code_navigation | Completion, go-to-definition, find references |
| navigation | Navigation regions, meshes, obstacle avoidance |
| particles | GPU particle systems |
{
"mcpServers": {
"godot-2": {
"command": "npx",
"args": ["-y", "@npgamedev/godot-mcp-server"],
"env": {
"GODOT_MCP_LSP_HOST": "your-value",
"GODOT_MCP_PROJECT_PATH": "your-value",
"GODOT_MCP_TOKEN_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| GODOT_MCP_LSP_HOST | Endpoint or connection string the server talks to. | Optional |
| GODOT_MCP_PROJECT_PATH | Filesystem location the server is allowed to use. | Optional |
| GODOT_MCP_TOKEN_PATH | Credential the server authenticates with. | Yes |
Enables AI agents to interact with Minecraft using the Model Context Protocol via Mineflayer.
Automates Unity workflows and manipulates assets using local large language models via Ollama.
Analyze chess positions and get professional evaluations using Stockfish within Claude.
Facilitates a trivia game where AI models generate content and manage gameplay through the Model Context Protocol.
Building a daily briefing for a human is mostly about sourcing the parts you can't write personally — the joke, the history snippet, the puzzle, the
Daily content for AI agents. History, chess, investing, wrongology, more. 10 channels. Free trial.