bricky-mcp
The MCP server for bricky, a compiler for LEGO® models, built for AI agents.
The server serves bricky to any agent harness over the Model Context Protocol, on stdio.
The command uvx, which comes with uv, runs it straight from PyPI.
With Claude Code, one command adds it:
claude mcp add bricky -- uvx --python 3.14 bricky-mcp
The option --python 3.14 runs the server on the Python bricky recommends: on 3.15, installing compiles the solver HiGHS, which needs a C++ compiler.
Other harnesses start it from a project's .mcp.json:
{
"mcpServers": {
"bricky": {
"command": "uvx",
"args": ["--python", "3.14", "bricky-mcp"]
}
}
}
The server renders in Chromium, which Playwright installs once per machine:
uvx --python 3.14 --from bricky-mcp playwright install chromium
The guide Connect an agent covers every front end, and the documentation covers bricky itself.
Tools
| Tool | Does |
|---|---|
build_model |
Runs a build script in its own process, then saves, checks and renders the model |
render_model |
Renders a saved model again: other views, highlights, clips |
check_model |
Checks a saved model |
write_instructions |
Writes building instructions: a page that shows a model's steps in 3D |
export_model |
Exports a saved model for another tool, such as a BrickLink Wanted List |
search_parts |
Searches the catalog's parts |
show_part |
Describes one part, and can render it |
search_colors |
Searches the catalog's colors |
explain_rule |
Gives the exact condition behind a rule, its level and its pass |
Each tool takes the same arguments as its command on the command line.
Each tool answers with the text the command prints and with the result as structured content.
The tools build_model and render_model also return their images, so the agent sees the model without another call.
Disclaimer
LEGO® is a trademark of the LEGO Group, which does not sponsor, authorize or endorse this project.
1 maintainer
Metadata
1 maintainer
Release files for bricky-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bricky_mcp-0.1.0.tar.gz | 10.3 kB | Without provenance | Details for bricky_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bricky_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for bricky_mcp-0.1.0-py3-none-any.whl |
Total release size: 21.9 kB
Release files / bricky_mcp-0.1.0.tar.gz
| Download URL | bricky_mcp-0.1.0.tar.gz |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
648ea394da9bb788277f0244052a1d5a0e3fa4270f5ffafd06ae5be4317432c8
|
|
BLAKE2b-256 checksum How to use checksums |
7fc9dae817b92e118ee20df4e49780e38f1235ce6591dbae0f9ff3939019791d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / bricky_mcp-0.1.0-py3-none-any.whl
| Download URL | bricky_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 11.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2f2407a5ee14a1163dfe1f85b30c34406d51f9504f04a81bc53c5fca4260de35
|
|
BLAKE2b-256 checksum How to use checksums |
62330d8f6b29d16fb54cd6ba59a5d3502c60b885be4a6172799c98ffa8edaf00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for bricky-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
