Cavi Godot MCP
Related Servers
Alternatives to Cavi Godot MCP
No user-submitted related servers found.
Related Servers
- 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.187 npm5MIT
- AlicenseBqualityCmaintenanceEnables MCP-compatible clients to render, inspect, and diagnose OpenMoonRay scenes through a local MoonRay runtime, with support for interactive viewing, scene validation, and render comparisons.25Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP hosts and coding agents to model, inspect, measure, and deliver real Blender scenes through 15 tools and 217 catalog operations, returning actual rendered images after key edits. Works against a live Blender GUI via addon or a persistent headless worker, producing editable .blend files, GLB exports, previews, and acceptance records.1BSD 3-Clause
- AlicenseNot gradedqualityBmaintenanceEnables a coding agent to build Three.js modules into GLBs or inspect existing GLBs, returning a six-view render sheet and a plain-language report on size, parts, materials, validation, and animation defects.MIT
- AlicenseNot gradedqualityCmaintenanceTurns a single image of an object into a textured 3D model (GLB with web-ready copy and six-view previews) on your own NVIDIA GPU, returning the written files and a preview. Runs locally as an MCP tool or, optionally, offloads the job to hosted GPUs with an API key.3AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables local Blender-based product modeling and photography by exposing project management, scene editing, rendering, image inspection, and asset publishing tools to MCP hosts like Claude Code, with versioned .blend revisions and PNG renders.GPL 3.0
TDQS
Scored across 4 tools
The four tools map to distinct stages of a review workflow: status checks configuration, prepare creates a review, capture runs it in a browser, and inspect verifies hashes. The only mild overlap is prepare vs. capture, which both concern the same review object, but the descriptions make the ordering and intent clear enough to avoid misselection.
All names share a consistent godot_ prefix and use snake_case, with a predictable godot_review_<verb> pattern for three of the four tools. godot_status breaks the pattern by omitting the review_ segment, a minor deviation that is still readable.
Four tools is on the low end but appropriate for a narrow, staged review pipeline where each tool corresponds to a pipeline step. Nothing feels redundant or like padding.
The lifecycle status → prepare → capture → inspect is covered, but godot_review_inspect only reports pending cleanup without any tool to actually perform cleanup or dispose of a review. There is also no way to list or fetch an individual review's details, leaving a notable dead end in the surface.