Godot Editor MCP 2026.08.26b1 Tools 4.4 Community

Submitted by user NetErr418; MIT; 2026-08-27

Godot MCP bridges a live Godot editor to an AI agent over the Model Context Protocol. Instead of editing files blindly on disk, the AI drives the editor directly — inspecting scenes, creating nodes, writing scripts, running the game, and exporting builds — all through 180 typed, structured tools.

Key features:
- 180 tools across 29 categories — inspection, scene editing, scripts, physics, runtime, testing, debugging, and more
- Game-agnostic — generic Godot editor control, no built-in game vocabulary
- Safety classes — every tool is tagged read_only, mutating (with dry_run), destructive (requires confirm), or runtime
- Auto-reconnecting — the addon dials out to the MCP server and reconnects on its own; editor and server can start in either order
- Status panel — bottom panel shows connection state, server version, active scene, and a recent-command log with timing stats
- GUT support — run GDScript test suites headlessly through the run_tests tool (GUT 9.3–9.7+ compatible)

How it works: The addon connects out via WebSocket to an MCP server (Python, runs on localhost). An AI client (Claude Code, OpenCode, or any MCP client) sends commands to the server, which routes them to the addon, which calls the Godot Editor API.