ldraw-mcp
<div align="center">
# ldraw-mcp
**Give your MCP client eyes for LEGO® models.**
Render LDraw files (`.ldr` / `.mpd` / `.dat`) to images with _real part
geometry_ — studs, slopes, window glass — using headless Blender and the
ImportLDraw addon. The output looks like a BrickLink Stud.io render, with no
GUI anywhere in the loop.
[](https://pypi.org/project/ldraw-mcp/)
[](https://pypi.org/project/ldraw-mcp/)
[](LICENSE)
[](https://modelcontextprotocol.io)
[](https://github.com/musharna/ldraw-mcp/actions/workflows/ci.yml)
[](https://glama.ai/mcp/servers/musharna/ldraw-mcp)
[](https://doi.org/10.5281/zenodo.21713452)
<img src="docs/hero.png" alt="Two rendered views of a red LEGO car — real studs, transparent glass, rubber tires, steering wheel" width="100%">
<sub>A ~90-line <code>.ldr</code> rendered front-left and rear-right — actual bricks, not a geometric proxy.</sub>
</div>
<!-- mcp-name: io.github.musharna/ldraw-mcp -->
---
Point a vision-capable model at a build and it sees the actual bricks:
crossed rotation matrices, floating plates, sunken windows — the kinds of
export bugs a geometric proxy render will happily hide.
## Quickstart
```bash
# 1. install
pip install ldraw-mcp
# 2. install the LDraw parts library + ImportLDraw addon
ldraw-mcp-setup
# 3. register with Claude Code
claude mcp add ldraw -- ldraw-mcp
```
Then ask things like _"render output/build.ldr and tell me what looks
wrong"_ — the model sees the render, not just the text.
> **Blender is a prerequisite** (see [Requirements](#requirements)); it is
> not installed by `ldraw-mcp-setup`.
## Tools
| tool | what it does |
| ------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| `render_ldraw_file(path, azimuths="-60,120", resolution=640, samples=24)` | Render a model file to a PNG (multi-view, stitched side by side) |
| `render_ldraw_text(ldr, azimuths="-60,120", resolution=640, samples=24)` | Render inline LDraw content without writing a file first |
| `check_renderer()` | Diagnose the Blender / addon / parts-library setup |
| `bill_of_materials(path="", ldr="")` | Part × colour × quantity rows for a model file or inline text |
| `lookup_color(query)` | Colour code ↔ name / RGB / edge / alpha from `LDConfig.ldr` |
| `search_parts(query, limit=50)` | Library parts whose description or file name contains `query` |
`azimuths` is a comma-separated list of view angles in degrees; each is
rendered and the views are stitched horizontally. Elevation is fixed at
22°. Higher `samples` = cleaner but slower.
The three query tools are read-only and need no Blender. `bill_of_materials`
expands MPD sub-models (and sibling `.ldr`/`.mpd` files next to the model) with
their multiplicity, and resolves colour 16 to the colour of the referencing
line; colour 24 (edge) is reported as 24. It counts without a parts library —
descriptions and colour names are then `null`. A colour code `LDConfig.ldr`
does not define is listed under `unknown_color_codes`, a part the library lacks
under `parts_not_in_library`; neither is dropped. A sub-model reference cycle is
an error that names the cycle. `lookup_color` and `search_parts` need the
library (`ldraw-mcp-setup`).
## Requirements
- **Blender 4.x** on `PATH`, or point `LDRAW_MCP_BLENDER` at the binary.
Install it yourself (package manager, blender.org, or a local build);
`ldraw-mcp-setup` does not install Blender.
- **ImportLDraw addon** (`io_scene_importldraw`) in Blender's addons dir —
installed by `ldraw-mcp-setup`.
- **LDraw parts library** at `~/.ldraw` (or `LDRAW_LIBRARY_PATH`) —
installed by `ldraw-mcp-setup`.
### Environment variables
| var | meaning |
| -------------------- | ------------------------------------------------------ |
| `LDRAW_MCP_BLENDER` | Path to the blender binary (overrides `PATH` lookup) |
| `LDRAW_MCP_DISABLE` | Set to `1` to force `is_available()` to `False` |
| `LDRAW_LIBRARY_PATH` | Path to the LDraw parts library (community convention) |
### Manual setup
If `ldraw-mcp-setup` can't detect things automatically:
- **LDraw library:** download
[complete.zip](https://library.ldraw.org/library/updates/complete.zip)
and unzip so that `~/.ldraw/parts/` exists.
- **ImportLDraw addon:** download the latest release from
[TobyLobster/ImportLDraw](https://github.com/TobyLobster/ImportLDraw/releases)
and install it via _Blender > Preferences > Add-ons > Install_, or unzip
into `~/.config/blender/<version>/scripts/addons/io_scene_importldraw/`.
(Launch Blender once first so the config directory exists.)
## Troubleshooting
- **`check_renderer` says NOT FOUND:** run `ldraw-mcp-setup`, or set the
relevant env var above.
- **No GPU / WSL2 / containers:** rendering uses **Cycles on CPU**, which
works headless everywhere — no GPU or display needed. A ~150-part model
takes a few seconds at the default 640px / 24 samples.
- **"no mesh objects imported":** the addon couldn't resolve parts —
usually a wrong or incomplete LDraw library path. Re-run setup or check
`LDRAW_LIBRARY_PATH`.
- **Addon not enabled:** the render script enables it automatically per
run; if a manual Blender session complains, enable `io_scene_importldraw`
in Preferences > Add-ons.
## Provenance
This renderer was extracted from the **prompt2brick** project, where it
started life as the vision critic's "see the actual model" path.
prompt2brick keeps its own vendored copy of the render wrapper and Blender
script, but **this repo is the canonical source going forward** — fixes and
improvements to the renderer should land here first and be ported back into
prompt2brick.
## License
MIT — see [LICENSE](LICENSE).
---
<sub>LEGO® is a trademark of the LEGO Group, which does not sponsor,
authorize, or endorse this project. This tool is not affiliated with the
LEGO Group, BrickLink, or the LDraw.org organization.</sub>
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: file rendering, inline rendering, bill of materials, renderer status check, color lookup, and part search. The two render tools differ only by input source (file vs inline text), and their descriptions make that boundary explicit.
Most tool names follow a clear verb_noun pattern: render_ldraw_file, render_ldraw_text, check_renderer, lookup_color, and search_parts. The exception is bill_of_materials, which is a noun phrase rather than a verb-led action, creating a minor inconsistency.
Six tools is well-scoped for an LDraw-oriented server covering rendering, analysis, and library lookups. Each tool earns its place without redundancy or bloat.
The tool surface covers the primary LDraw workflows: rendering models from files or inline content, generating bills of materials, checking renderer availability, and querying the part and color libraries. No obvious dead ends or critical missing operations are apparent for the intended domain.