ldraw-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LDRAW_MCP_BLENDER | No | Path to the blender binary (overrides PATH lookup) | |
| LDRAW_MCP_DISABLE | No | Set to 1 to force is_available() to False | |
| LDRAW_LIBRARY_PATH | No | Path to the LDraw parts library (community convention) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_rendererA | Report whether the LDraw rendering stack is available and why not. |
| render_ldraw_fileA | Render an LDraw model file (.ldr/.mpd/.dat) to a PNG image. Views are rendered at each comma-separated azimuth (degrees) and stitched side by side. Higher samples = cleaner but slower. |
| render_ldraw_textB | Render inline LDraw content (the text of a .ldr file) to a PNG. Useful for quick experiments without writing a file first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: checking renderer availability, rendering from a file, and rendering from inline text. No overlap or ambiguity.
All tools follow a consistent 'verb_noun' pattern (check_renderer, render_ldraw_file, render_ldraw_text), making them predictable.
With only 3 tools, the set is minimal but appropriate for a focused rendering server. It could benefit from additional utilities like listing supported formats, but the count is reasonable.
The set covers the core rendering workflow (check availability, render from file or text). Minor gaps exist, such as no way to cancel or monitor rendering progress, but overall it feels complete for its stated purpose.