BumpMesh MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUMPMESH_ROOT | Yes | Required explicit file root. All inputs and outputs must remain inside this directory. Equivalent to the --root command line argument. | |
| BUMPMESH_HTTP_TOKEN | No | Optional bearer token for authenticating HTTP requests when running in Streamable HTTP mode. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_supported_formatsA | List supported model/texture/export formats, processing limits, units, and the configured local file root. |
| inspect_modelA | Inspect a local STL/OBJ before texturing: triangles, millimeter bounds, open and non-manifold edges. Does not modify the model. |
| apply_textureA | Subdivide a local STL/OBJ, displace its surface using a PNG/JPEG/WebP height map, optionally decimate, and export a new STL/3MF. Use after inspect_model. Preserves input coordinates. Never overwrites files. Negative amplitude engraves. No network downloads or browser automation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| license | GNU AGPL v3 license and upstream attribution. |
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.