Godot MCP

What it does

• Pure in-engine plugin: drop two addons into the project, enable them, and a Godot MCP dock appears beside the Inspector — no npm, no accounts, no cloud
• Full editor surface over MCP: nodes, scenes, scripts, tilemaps, physics, meshes, shaders, animation, input, UI trees, screenshots and logs
• Drives the running game: launch, stop, restart and diagnose a live play session from the chat
• Universal engine support: Godot 4.1–4.8+ standard and .NET editions; clients connect via a single uvx-run bridge command

When to use it

Godot developers who want the agent to actually touch the editor — build and iterate scenes, paint tilemaps, fit collisions, then run the game and read its logs — instead of only writing scripts the human has to wire in by hand.

Getting started

# 1. download the release archive from GitHub Releases and extract addons/ into your project
# 2. in Godot: Project -> Project Settings -> Plugins, enable "Godot MCP Core" and "Godot MCP Omni"
# 3. point your MCP client at the bridge (README-documented uvx form):
{
  "mcpServers": {
    "godot-mcp": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/bebabinlarsson-blip/Godot-MCP.git", "godot-ai"]
    }
  }
}

Things to know

The README's badge still says v5.0.5 while the latest release is v5.0.14 — grab the newest archive from the Releases page rather than copying the README's filename. Tool-family and operation counts (59 / 1,820+) are the project's own documentation. The reflection and GDScript-evaluation tools can run arbitrary engine code, so scope what you let the agent do in shared projects. The bridge needs the uv toolchain and Python 3.11+. MIT.