Your assistant gets a link to Godot.
With the Coding-Solo server, an assistant can launch a project and read its debug output. Install and configure it in your MCP client first; this page only explains the connection.
Connect your tools, give your assistant better context, or find the script you need. Pick something useful and make it yours.
Explore the resourcesA connection, an instruction file, and a script each do a different job. All three are on this page.
With the Coding-Solo server, an assistant can launch a project and read its debug output. Install and configure it in your MCP client first; this page only explains the connection.
Use this task brief alongside your project context. The full developer agent adds more Godot conventions; neither file connects to the editor by itself.
Help me with one small change in my Godot project.
Before writing code:
- Ask for my exact Godot version and target platform.
- Read the relevant scripts and scene tree I provide.
- Explain which node should own the behavior and why.
When making the change:
- Match the project's language and naming conventions.
- Verify version-sensitive APIs against the official docs.
- Keep the change focused on the requested behavior.
Before calling it done:
- Tell me how to run the scene and what I should see.
- Separate checks you ran from checks I still need to run.
- Explain any errors rather than claiming the scene works. Attach this to a CharacterBody2D. Add a visual and CollisionShape2D, then create left, right, up, and down actions in Project Settings → Input Map.
extends CharacterBody2D
@export var speed: float = 300.0
func _physics_process(delta: float) -> void:
var direction := Input.get_vector("left", "right", "up", "down")
velocity = direction * speed
move_and_slide() Check it in Godot: hold a mapped direction key. The body should move and stop at a StaticBody2D wall with a collision shape on a matching layer. This preview does not run the script.
9 resources
Connect an MCP-capable assistant to a local Godot project. Learn what the server can inspect, run, and change.
Needs Godot, Node.js, and an MCP client.Follow the setupGive your assistant Godot-specific instructions for scene structure, GDScript, and explaining its decisions.
A prompt file; it does not connect to the editor.Preview the agent fileGive the assistant your scene tree, ask for one change, and verify the result in Godot before moving on.
Includes prompt examples and API checks.Build your workflowFind movement, signals, UI, save/load, and other reusable patterns. Adapt each snippet to your scene.
Search by task and open the related guide.Browse scriptsRead a player controller or signal example one section at a time, with explanations beside the code.
Start here if a copied script feels mysterious.Explore explained scriptsExplore scene composition and reusable game systems when a single snippet is no longer enough.
Connect small scripts into a larger feature.Explore patternsLook up syntax while you write: variables, functions, signals, and familiar language patterns.
Keep it nearby while following a tutorial.Open the cheat sheetFind a key combination for the editor action you need, with Windows, Linux, and macOS mappings.
Spend less time hunting through menus.Find a shortcutMake sense of nodes, signals, rendering terms, and the vocabulary you meet in the editor.
Short explanations linked to further learning.Look up a term