Goxel-MCP
Related Servers
Alternatives to Goxel-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceVoxel editor with an MCP server: build and edit MagicaVoxel .vox models, add bones and animation clips, run Rhai generator scripts, path-trace PNG previews, and export glTF.9MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to create and edit pixel art and animations through a local-first editor, sharing the same project, editing commands, and undo history with the GUI.-
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to drive Blockbench Desktop locally for Minecraft model, UV, texture, animation, and export workflows. It provides typed operations, high-level task workflows, native controls, and inspection/verification tools over an authenticated loopback connection.3-
- AlicenseCqualityDmaintenanceA voxel editor with MCP bridge enabling AI agents to create and edit 3D models, supporting .vox/.obj formats, layers, and a web editor.27MIT
- AlicenseAqualityBmaintenanceEnables AI agents to procedurally model and sculpt 3D voxel characters, weapons, and scenery, execute custom QuickJS generation scripts, convert/export models between voxel and 3D/image formats, and open results in the desktop GUI for inspection or editing.51MIT
- AlicenseNot gradedqualityDmaintenanceEnables creating, modifying, and managing MagicaVoxel .vox files through natural language, with tools for shape generation, patterns, color operations, and optional ML-powered suggestions.33MIT
TDQS
Scored across 17 tools
Most tools target clear, distinct operations, and the descriptions actively disambiguate the risky pairs (add_voxels vs draw_primitive, save_scene vs export, erase_region vs draw_primitive remove mode). The main residual overlaps are goxel_open_scene vs goxel_open_in_app and the recolor/erase vs draw_primitive paint/remove modes, which an agent could still mix up.
All names are snake_case with a uniform goxel_ prefix and mostly follow verb_noun (draw_primitive, save_scene, erase_region). A few are noun-only namespace multiplexers (goxel_layers, goxel_live, goxel_info, goxel_undo), which is a minor deviation but still readable and predictable.
17 tools is slightly above the comfortable range but each covers a real facet of voxel editing (scene lifecycle, geometry, layers, render, export, live bridge). A couple of entries (open_scene vs open_in_app, save_scene vs export) could be consolidated, but nothing is obviously filler.
The surface covers the full lifecycle: create/open, edit (add, draw, erase, recolor), inspect, layers, undo/redo, preview, validate, save and export across many formats. Remaining gaps are notable but workaroundable: goxel_transform only translates (no rotate/scale/mirror as a standalone op), and there is no explicit palette or region copy/paste management.