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.7MIT
- 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.1MIT
- AlicenseAqualityCmaintenanceEnables agents to drive native CAD operations in a local Plasticity session on macOS, including scene inspection, precise B-rep measurement, geometry creation and editing, import/export, and screenshots. An optional Workbench adds model review, validated dimensional feedback, and Creality Print slice-and-print preparation with explicit user confirmation.112MIT

GoModelHub 3D MCPofficial
AlicenseAqualityCmaintenanceEnables 3D model generation via natural language, supporting text-to-3D and image-to-3D with remote or local deployment options.3MIT- AlicenseNot gradedqualityAmaintenanceEnables AI agents to model, sculpt, rig, animate and bake particle effects by editing a semantic scene document, with built-in software rendering, measurable critics that flag floating or broken geometry, and game-ready glTF export. It exposes templates, atomic edit batches, motion and effect previews, undo history, and no GPU, browser, or Blender required.23 npmApache 2.0
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.