Godotwright
Related Servers
Alternatives to Godotwright
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to read and edit Godot 4.x scenes and resources, introspect the class API, run the game in a managed headless process with frame stepping, input injection and screenshots, validate scripts, and diagnose code via a built-in GDScript LSP plus a bridge to an already open editor.23MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect, edit, and run Godot 4 projects — scenes, nodes, signals, resources, animations, tile maps, audio buses, visual shaders, project settings, input actions, and exports — with GDScript language-server diagnostics, offline class reference, live in-game debugging, and GUT/GdUnit4 test runs. It works through a live editor bridge so every edit can be undone with Ctrl+Z, and falls back to headless execution when the editor is closed.2MIT
- AlicenseBqualityCmaintenanceEnables AI agents to inspect, modify, run, and debug Godot projects, including scene and script analysis, editor and project management, and visual verification through screenshots.2211 npm14MIT
- AlicenseCqualityCmaintenanceEnables AI agents to interact with the Godot game engine, including project inspection, scene/script parsing, headless exports, runtime control with live scene-tree inspection and evaluation, and API documentation search.1005MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect, author, debug, simulate, and visually verify Godot 4.x projects through standard MCP tools, including scene editing, runtime control, and viewport capture.5MIT
- AlicenseCqualityBmaintenanceEnables AI assistants to drive the Godot game engine through 157 tools covering project creation, scene and resource editing, runtime GDScript execution, node and property inspection, signals, physics, audio, UI, animation, networking, and error/log capture. It works both headlessly on project files and live against a running game for debugging and testing.157MIT
TDQS
Scored across 43 tools
Many tools target distinct workflows, and descriptions explicitly point to alternatives such as godot_review versus godot_check versus godot_doctor. However, the diagnostics/verification cluster and the model-authoring cluster are large enough that an agent must read descriptions carefully to avoid misselection.
All tool names are snake_case with a godot_ prefix, giving a predictable overall style. Most use a consistent domain_noun or verb_noun structure, but some are noun phrases while others are verb phrases, so it is not strictly verb_noun throughout.
At 43 tools, the surface is well past the 25-tool threshold and is unwieldy even for a broad Godot development server. Many workflows could be consolidated or tiered into a smaller default set with optional advanced tools.
The surface covers a very broad Godot lifecycle: project mapping, API lookup, safe edits, rename/migrate/fix, static and runtime checks, tests, play/session, performance/leaks, export, models, shaders, and undo. Minor gaps remain around direct script/scene creation and specialized animation/audio/UI authoring, but core workflows are well represented.