godot-assistant
An MCP server that lets an AI coding agent actually work on a project: read scenes, edit node trees, write and validate GDScript, run the game, and .
Power your agent
पब्लिशर की अपनी कमांड। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
npx -y [email protected]Claude Code में लोकल कमांड के लिए इंस्टॉल लिंक नहीं है। नीचे दी गई कमांड कॉपी करें और टर्मिनल में चलाएँ।
claude mcp add godot-assistant -- npx -y godot-assistant@1.0.0टर्मिनल में चलाएँ।
{ "mcpServers": { "godot-assistant": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चपब्लिशर से
Works with Claude Code, Codex, Cursor, Claude Desktop, Cline, Windsurf, or any MCP client.
claude mcp add godot-assistant -- npx -y godot-assistant --project /path/to/your/game
That is the whole installation. No addon to copy, no build step, no project changes.
Existing servers land on one of two extremes. One is command-line only: easy to install, but it cannot see the editor, cannot see the running game, and cannot show you a single pixel, so an agent works blind and finds out something is wrong only when it crashes. The other exposes 175 tools through a mandatory editor plugin, which is enough tool definitions to measurably degrade the model doing the work.
godot-assistant takes the middle path deliberately:
Zero-setup by default. Every core capability (reading scenes, editing nodes, writing scripts, validating, running, and rendering a scene to a PNG) runs through the Godot binary you already have. Nothing is written into your project.
Live features when you want them. One call to bridge_install adds a small optional addon that unlocks inspecting the running game, simulating input, and screenshotting the game and editor. Without it, those tools fail with an explanation instead of a stack trace; everything else is unaffected.
25 tools, not 175. Grouped by intent with batched operations, so the model spends its context on your game instead of on tool definitions. The full set costs about 6.5k tokens.
It refuses to corrupt your scenes. See Safety.
Prerequisites: Godot 4.x (download) and Node.js 18+. Godot is auto-detected on macOS, Windows and Linux, including Homebrew, Scoop, Snap and Flatpak installs.
claude mcp add godot-assistant -- npx -y godot-assistant --project /path/to/your/game
In ~/.codex/config.toml:
[mcp_servers.godot-assistant]
command = "npx"
args = ["-y", "godot-assistant", "--project", "/path/to/your/game"]
In your client's mcp.json:
{
"mcpServers": {
"godot-assistant": {
"command": "npx",
"args": ["-y", "godot-assistant", "--project", "/path/to/your/game"]
}
}
}
--project is optional. Omit it and pass project per tool call instead. Setting it is recommended: it removes an argument from every call.
npx -y godot-assistant doctor --project /path/to/your/game
godot-assistant 1.0.0
node: v22.11.0
godot: 4.7.1.stable.official
path: /Applications/Godot.app/Contents/MacOS/Godot
found via: standard install
C# support: no
project: My Game
path: /path/to/your/game
main scene: res://scenes/main.tscn
language: GDScript
live bridge: not running (optional)
All checks passed.
npx -y godot-assistant install prints ready-to-paste config for every client.
"Add a double jump to the player and show me it working."
The agent reads player.gd, checks CharacterBody2D against the real engine API, edits the script, validates it, runs the game, and screenshots the result.
"The coin pickup isn't firing. Why?"
scene_tree on the level, node_inspect on the coin to see its signal wiring, search for the handler, run_project to read the actual error with a file and line number.
"Build a pause menu."
api_reference for Control and Button, scene_create, node_add for the layout in one batch, signal_connect to wire the buttons, screenshot to check it looks right.
Discovery
Engine API
This one matters more than it looks. Godot's API changed substantially at 4.0 and keeps moving across minors, so a model working from memory invents method names and mixes up signal signatures. api_reference replaces recall with a lookup against the exact engine version in use.
Scenes and nodes
Scripting
Running and debugging
Seeing
Assets, editor, export
JSON has no Vector2, so properties are converted for you:
{
"position": [100, 250], // -> Vector2(100, 250)
"scale": [2, 2, 2], // -> Vector3(2, 2, 2)
"modulate": "#ff8800", // -> Color
"texture": "res://icon.png", // -> loaded Resource
"mouse_filter": "MOUSE_FILTER_IGNORE" // -> enum constant
}
Anything else passes through with the property's declared type. A name that does not exist on the node is reported rather than silently dropped.
bridge_install
Adds addons/godot_assistant/ and enables it. This unlocks:
screenshot(source="game") and source="editor"simulate_input: drive the game with synthetic inputruntime_inspect: the live tree, including inside instanced sceneseditor_control: open scenes, play/stop, read editor stateSecurity posture. The bridge listens on 127.0.0.1 only, requires a token regenerated every session, and refuses to start in non-debug builds so exported games never carry it. The discovery file lives in .godot/, which Godot already git-ignores. Port assignment is dynamic, so several projects can be open at once.
Remove it any time with bridge_install action="uninstall".
Scene files are the crown jewels of a Godot project and a bad write is easy to miss for hours. This server is built around not doing that.
It will not silently drop your scripts. Editing a scene means loading, mutating and repacking it. If a script fails to compile, the engine drops the reference and the save would quietly detach it from your node. That write is refused, with the offending script named and the file untouched. force=true is available when the removal is genuinely intended.
It will not break your uid://. Repacking a scene loses the UID in its header, which breaks every other scene referencing it. The UID is captured before the edit and restored after.
It will not corrupt C# scenes. A non-.NET Godot build cannot resolve CSharpScript, so editing a scene with C# attached strips those attachments. Detected up front and refused, with instructions.
It will not run code you did not ask for. Node types are validated as bare identifiers and checked against ClassDB on both sides, so a res://payload.gd passed as a node type is rejected rather than loaded and executed.
It will not escape your project. Paths are normalised, NUL-checked, and resolved through realpath before the containment check, so symlinks cannot step outside the project root.
It will not hang. Every engine invocation has a hard timeout and a kill escalation. (A headless Godot waiting on a rendered frame waits forever: a real thing this server works around.)
Read-only mode. --read-only (or GODOT_ASSISTANT_READ_ONLY=1) refuses every mutating tool while leaving inspection intact.
MCP responses are billed to the agent's context, so:
node_inspect shows only properties that differ from engine defaults.offset= hint to resume.Commands: godot-assistant (serve), doctor, install, --help, --version.
"Could not find a Godot executable." Set GODOT_PATH in the MCP config's env block. On macOS point at the binary inside the bundle, not the .app folder:
"env": { "GODOT_PATH": "/Applications/Godot.app/Contents/MacOS/Godot" }
"No project.godot found." Point --project at the folder containing project.godot. Any path inside the project also works, because it walks up.
"Godot did not return a result." Usually a script in the project fails to parse. Run script_validate.
Screenshots time out or look stale. The game window must be visible to render; run_project sets always-on-top by default for this reason. On a headless server with no display, scene rendering is unavailable, so use headless=true runs and read the console instead.
C# project. Install the .NET build of Godot and point GODOT_PATH at it. Scene edits touching C# are refused with a standard build rather than silently corrupting the file.
npm install
npm run build
npm test # end-to-end suite against a real Godot binary
The QA suite builds a throwaway project with instanced scenes, sub-resources, exported overrides and signal connections, then drives the server over real MCP stdio: 109 checks covering protocol shape, scene-edit fidelity, path-traversal and code-execution rejection, live-bridge behaviour, graceful degradation, error quality and output size.
MIT
If this saves you time, you can support the work on GitHub Sponsors or Ko-fi.
Production-grade MCP server for the Godot Engine. Lets AI coding agents inspect, edit, run, and visually verify Godot 4 projects.
{ "mcpServers": { "godot-assistant": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Godot Assistant stdio पर लोकल चलता है।
पिछली जाँच 2026-11-16 को हुई। Production-grade MCP server for the Godot Engine. Lets AI coding agents inspect, edit, run, and visually verify Godot 4 projects.