BumpMesh MCP
Related Servers
Alternatives to BumpMesh MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables people and general-purpose AI agents to inspect, model, edit, verify, and export local 3D projects through MCP tools, including print preparation, without requiring a hosted 3D service key.10MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to turn a single image into a textured 3D mesh (GLB, OBJ with vertex colours, plus a turntable PNG) entirely on local hardware. Exposes capability reporting, dry-run planning, job queuing, and status/result retrieval so quality presets, hardware tiers, and consented model downloads can be driven through natural language.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to prepare and inspect STL/3MF files and run offline slicing on an isolated Windows desktop while leaving the mouse, keyboard, and visible desktop usable; also supports an X2D dual-nozzle workflow with offline validation of sliced 3MF archives and nozzle assignments.GPL 2.0
- FlicenseAqualityBmaintenanceEnables AI assistants to perform high-performance 3D CAD design, ultra-fast multi-view rendering, immutable versioned project management, and geometry/mesh verification for 3D printing on Windows.17-
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to generate 3D models through natural language, including text-to-3D and image-to-3D, with tools for checking balance, refining models, converting formats, and a local 3D viewer that works without external network access.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to turn text prompts and 2D photos into watertight 3D-printable figurines, keyed multi-part assemblies, and game-ready PBR assets entirely on local consumer hardware within a 16 GB RAM/VRAM budget. It exposes 16 native tools covering image-to-3D generation, pose canonicalization, auto-split assembly, retopology, texture baking, and hardware tier detection over stdio.MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: listing supported formats/configuration, inspecting a model, and applying a texture operation. There is no overlap or ambiguity in their purposes.
All tool names follow a consistent snake_case verb-first pattern: list_supported_formats, inspect_model, apply_texture. The naming style is uniform and predictable.
Three tools is a well-scoped set for a focused single-purpose server. Each tool occupies a necessary step in the local mesh texturing workflow with no redundant additions.
The tool surface covers the full intended pipeline: discover supported formats, inspect the input model, and apply a heightmap texture with export options. There are no obvious dead ends or missing operations for the stated domain.