Skip to main content
Glama
ldraw-mcp

ldraw-mcp

by musharna

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LDRAW_MCP_BLENDERNoPath to the blender binary (overrides PATH lookup)
LDRAW_MCP_DISABLENoSet to 1 to force is_available() to False
LDRAW_LIBRARY_PATHNoPath 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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. Bounds: resolution 32..2048 px per view, samples 1..1024, 1..8 azimuths, and resolution^2 x samples x views at most 2**27. A referenced file the LDraw library lacks is left out of the picture and named in a text block after the image.

render_ldraw_textA

Render inline LDraw content (the text of a .ldr file) to a PNG.

Useful for quick experiments without writing a file first. Same bounds as render_ldraw_file.

bill_of_materialsA

Bill of materials for an LDraw model: part x colour x quantity rows.

Give path (a .ldr/.mpd file) or ldr (inline LDraw text), not both. MPD sub-models are expanded with their multiplicity, and colour 16 inherits the colour of the line that referenced the sub-model. Part descriptions and colour names come from the LDraw library when one is installed; without it the counts are the same and those fields are null. A colour code that LDConfig.ldr does not define is listed in unknown_color_codes, and a part the library lacks in parts_not_in_library.

lookup_colorA

Look up LDraw colours in the library's LDConfig.ldr.

query is a colour code (4, or a direct colour 0x2FF8800) or part of a name (dark blue, Trans_Red). Returns code, name, RGB, edge colour, alpha and finish for each match; an unknown code returns no matches.

search_partsA

Search the LDraw library's parts by description or file-name substring.

Case-insensitive, runs of spaces collapsed (brick 2 x 4 matches the header Brick 2 x 4). Returns at most limit parts (max 200) plus the total number of matches.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 6 tools

Disambiguation5/5

Each tool occupies a clearly distinct niche: rendering (file vs inline text), BOM analysis, colour lookup, part search, and environment diagnostics. The closest pair, render_ldraw_file and render_ldraw_text, is cleanly separated by input form (path vs inline LDraw text) in both name and description. No tool overlaps another's job.

Naming Consistency4/5

Five of six names follow a consistent snake_case verb_noun pattern (check_renderer, lookup_color, render_ldraw_text, render_ldraw_file, search_parts). bill_of_materials deviates as a bare noun phrase, though it is still immediately readable and unambiguous.

Tool Count5/5

Six tools is well within the sweet spot and each one earns its place: two render entry points, two query tools (parts, colours), one analysis tool, and one diagnostic. Nothing feels padded or redundant for a focused LDraw rendering/inspection server.

Completeness4/5

The read-only lifecycle is well covered: render a model or raw text, extract a bill of materials, search parts, look up colours, and verify the rendering stack. Minor gaps remain — no model validation/parse-error reporting tool and no way to list library categories or discover models — but agents can work around these.

Maintenance

ActivityNo data
ResponsivenessOutdated data