3d-texture-toolkit-mcp
Related Servers
Alternatives to 3d-texture-toolkit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables processing, validation, optimization, and analysis of 3D models with glTF/GLB support, including format conversion, compression (Meshopt/Draco), texture optimization, and detailed model statistics.17 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables creating layered 3D reliefs from selected parts of a photo, producing GLB files and a self-contained HTML viewer that tilts with the pointer, with interactive approval of the segmentation before writing files.8 npmMIT
- AlicenseAqualityCmaintenanceEnables local image-driven displacement of STL/OBJ meshes, STL/3MF export, and agent-driven texturing workflows without remote services.3AGPL 3.0
- FlicenseAqualityDmaintenanceEnables working with 3D models by converting GLTF/GLB files into React Three Fiber JSX components and analyzing model structures, hierarchies, and properties for debugging and optimization.215 npm26-
- AlicenseNot gradedqualityAmaintenanceEnables local glTF/GLB asset validation against versioned profiles via MCP, returning actionable reports.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
TDQS
Scored across 1 tool
With only one tool, there is no possibility of selecting the wrong tool or confusing overlapping purposes. Its purpose is clearly scoped to extracting PBR maps.
The single tool name follows a clear verb_noun snake_case pattern: extract_pbr_maps. Although consistency across a larger set cannot be assessed, the available name is predictable and readable.
A single tool is borderline thin for a server named as a texture toolkit. It may be adequate for narrow PBR extraction, but the name implies broader texture-processing capability.
The surface covers extraction and channel splitting of existing PBR maps, but lacks complementary operations such as packing maps, validating inputs, or handling other texture workflows. For a toolkit, this leaves significant gaps.