No user-submitted related servers found.
Scored across 22 tools
Most tools occupy distinct niches (scan, usages, rename, review, check, play, test), and descriptions actively route the agent between them ('for engine classes use godot_api', 'for a picture use godot_screenshot'). A few clusters blur at the edges: godot_api vs godot_api_search (search vs exact lookup), godot_review vs godot_check vs godot_checklist, and especially godot_model_brief vs godot_model_identify vs godot_model_spec, plus godot_model_view vs godot_model_inspect vs godot_screenshot. These are separable but require reading long descriptions to choose correctly.
Every tool is prefixed godot_ with snake_case, and the 3D model family (godot_model_*) is grouped predictably. Deviations are minor: several names are bare nouns or verbs without an object (godot_scan, godot_review, godot_check, godot_api) rather than a uniform verb_noun pattern, and godot_check/godot_checklist sit close enough to invite confusion.
22 tools is at the heavy end of the range and effectively covers two surfaces: project/code work (scan, review, edit, run, test, rename, migrate) and 3D model authoring (identify, brief, spec, build, lint, view, inspect, screenshot). Each tool does have a job, but the model subfamily alone is eight tools, several of which are thin conveniences (brief, spec, identify) an agent could absorb.
Lifecycle coverage is strong: discovery (scan, usages, api, api_search, checklist), analysis (review, check, play, test), mutation (rename, project_edit, scene_edit, migrate) and a full model pipeline from identification through build, lint, view, inspect and screenshot. Gaps are mostly around asset/script file authoring — no tool to create or delete a .gd/.tres, and scene_edit covers node add/remove/set/connect but not duplication, reorder or scene creation.