threenative-sculpt-mcp
Related Servers
Alternatives to threenative-sculpt-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to procedurally generate, transform, inspect, and export 3D meshes and scenes through MCP tools.MIT
- AlicenseNot gradedqualityDmaintenanceReconstructs a reference image as procedural 3D geometry through a staged pipeline, generating a Three.js model, preview, comparison, and glTF export.MIT
- AlicenseAqualityCmaintenanceEnables AI agents and MCP clients to perform 3D asset creation and verification: exact b-rep CAD, GLB validation with embedded certificates, mesh inspection, and physics scenes, with most tools running without Blender.3648 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM and agent hosts to create and manipulate structured game-art documents through typed deterministic MCP operations, render them to SVG/PNG, validate output, inspect visuals, and make targeted edits toward reproducible, game-ready assets.Apache 2.0
- AlicenseAqualityCmaintenanceEnables generating consistent four-view concept references, textured Meshy 3D models, and Adaptive Low remeshes through an MCP server and resumable command-line workflow.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables autonomous creation, editing, auditing, and visual verification of Minecraft skins with dual-layer 3D depth, via 45 MCP tools, real-time WebGL preview, and procedural healing.MIT
TDQS
Scored across 5 tools
Each tool addresses a distinct phase or concern: planning, spec validation, comparison, pass gating, and resource lookup. There is no ambiguity between them; the descriptions clearly separate their roles.
All tool names share the sculpt_ prefix, but the suffixes mix verbs (compare) and nouns (plan, grimoire) with compound nouns (spec_gate, pass_gate). This is mostly consistent but not a uniform verb_noun pattern.
5 tools is well within the ideal 3-15 range, and each tool serves a necessary, non-redundant function within the workflow.
The core workflow of plan, validate, compare, gate, and fetch resources is well covered. Minor gaps exist, such as no direct way to list all grimoire topics without triggering an error, but the surface is sufficient for the likely use case.