Get started
Two ways to get running. Pick whichever fits.
Option 1 — Let your AI assistant do it (easiest)
You use an AI assistant (Claude, Codex, ChatGPT…) and would rather not touch a terminal. Hand it the setup:
→ Start with your AI agent — one copy-paste prompt installs the server, the addon, and the skill; you do one click and start building.
Option 2 — Set it up yourself
You're comfortable with installs and MCP. Five steps:
- Install the MCP server — PyPI, Docker, or from source.
- Install the Godot addon — from the Godot Asset Store (Godot Editor MCP - Addon), or copy it in; then enable it.
- Configure your client — OpenCode, Claude, or any MCP host.
- Install the skills — this is what makes your assistant enable toolsets on its own, read the honesty fields, and avoid the common Godot pitfalls. Do it before your first session.
- Run your first session — the orient → enable → preview → act → verify rhythm.
Running several clients against one editor, or driving Godot remotely? See Remote & multi-client.
Requirements
| Component | Minimum | Recommended |
|---|---|---|
| Godot | 4.4 | 4.7 (validated target) |
| Python | 3.11 | 3.13 |
| Package manager | uv | uv |
| OS | macOS / Linux / Windows | Any desktop |
Godot 4.4 is the floor
The addon checks the editor version on enable and warns if it's older. A few toolsets (scene_edit, input_map, tilemap, scene_3d) are version-gated and refuse to enable on older editors.
New to the ideas behind any of this? Concepts explains the mental model in five short ideas.