cadloop Slicer MCP server
Find printer profiles, check bed fit, slice to .gcode.3mf and extract the G-code.
1 stars36 downloads/wk
Reviews
Write oneNobody has reviewed cadloop Slicer yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
cadloop Slicer tools (16, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
checkCompile a script without evaluating geometry. Fast syntax and reference check. Returns errors, warnings and any ECHO output.
check_bed_fitCompare an STL's footprint against the machine profile's printable area before slicing. The slicer will happily emit out-of-bounds G-code without complaining, so this is worth doing first.
echoEvaluate a script and return only its ECHO output. Use this to read computed values out of a model without paying for a mesh render.
extract_gcodePull the raw G-code for a plate out of a .gcode.3mf. Creality printers generally want a plain .gcode file, unlike Bambu machines which take the archive directly.
list_filesList files in the workspace matching a glob pattern.
list_profilesFind machine, process and filament profiles. kind is machine, process, filament or all. query filters on the profile name, case-insensitive.
measureRender to a throwaway STL and report bounding box, size, volume and triangle count. Use it to check a part fits the print bed.
model_infoReport what the slicer sees in a model or project file without slicing it. Uses --info.
openscad_infoReport the OpenSCAD binary, its version, and the workspace directory.
previewRender a PNG of the model and return it as an image.
read_fileRead a text file from the workspace.
renderRender a script to a mesh or 2D file in the workspace. The format is taken from the output extension: stl, off, amf, 3mf, dxf, svg, csg.
slice_modelSlice one or more models to a .gcode.3mf and report the result.
slice_summaryRead filament usage, print time estimate and the settings actually used out of a sliced .gcode.3mf, without unpacking it.
slicer_infoReport the slicer binary, its version banner, and the full --help flag surface. Call this first. The Orca-family CLI changes between releases and Creality's fork diverges, so trust this over any assumed flag list.
write_filewrite actionWrite a text file into the workspace, creating parent directories.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- Code scan9 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 51 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
What the publisher says
From the cadloop Slicer repository's README, as published. We do not edit it. Read it on GitHub
cadloop
<!-- mcp-name: io.github.richardofortune/cadloop-openscad --> <!-- mcp-name: io.github.richardofortune/cadloop-slicer -->
A closed loop from parametric source to G-code, with the verification step in the middle that neither the CAD tool nor the slicer can do.
Two MCP servers. A model writes OpenSCAD, compiles it, reads computed values back out, looks at a render, checks it fits the bed, slices it and pulls out the G-code, with every plate proven against the printable area. No GUI at any point.
The verify step in the middle is yours to write. cadloop makes everything around it cheap enough that you get to run it often; it cannot tell you whether the part works.
Every number in that walkthrough is real output. The failing wheel is a real measurement, not an illustration. How it's built and where each number comes from is in docs/walkthrough.
setup_printer once, no arguments: which printer is this for
|
write .scad
|
check syntax and references, about a second
|
echo read computed values without rendering
|
preview look at it
|
verify does it actually work <- yours; nothing here does it for you
|
measure bounding box and volume
|
check_bed_fit against the printer you set up
|
slice_model -> .gcode.3mf
|
extract_gcode -> .gcodeThe ordering is the point. check and echo skip geometry evaluation entirely, so they cost a second against models where a full render takes minutes. Pay for the expensive steps only once the cheap ones pass.
Everything from the bed check down is also one call, make_printable, which renders, packs, slices and proves the result on the bed and reports what it did in a screen of text. See the worked example.
Install
pip install cadloopThe only dependency is mcp. Or from a checkout, which is what you want if you intend to run the worked example or the tests — the verify extra is shapely, needed by the example's own checker rather than by cadloop:
git clone https://github.com/richardofortune/cadloop
cd cadloop
pip install -e ".[verify]"Needs OpenSCAD on PATH or at OPENSCAD_BIN, and for slicing, OrcaSlicer, Bambu Studio, ElegooSlicer or Creality Print. They share a CLI, so any of them works, and all four are auto-detected along with the profiles they ship.
No slicer is preferred over another here. setupprinter probes each one it finds and then proves the winner by slicing a 20mm cube with your profiles, so which one you get is decided by which one works on your machine rather than by the order of a list in this repository. Creality Print's CLI is broken headless on macOS today, and that is something this discovers rather than something it asserts, so it corrects itself when upstream ships a fix; see testing status below. SLICERBIN overrides the choice.
Configure
Copy mcp.json into your client's config and fix the paths. Both servers should point at the same workspace directory, which is the only place either one reads or writes.
The servers
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Install directly
claude mcp add cadloop-slicer -- uvx cadloop
cadloop Slicer: common questions
- Is cadloop Slicer MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the cadloop Slicer safety report
- How do I install cadloop Slicer?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does cadloop Slicer need an API key?
- No secret keys are declared. It reads 4 settings from the environment.
- Is cadloop Slicer maintained?
- The last commit was 52 days ago (2026-08-04). The latest release is v0.1.0.
- What can I use instead of cadloop Slicer?
- Servers from other publishers that do the same job: Brightdata MCP server, Openbrowser AI MCP server and Zenrows MCP server. Compare all cadloop Slicer alternatives.
Alternatives to cadloop Slicer
Same job from other publishers: the closest match first, then the best rated.
- BrightdataBright Data's Web MCP server enabling AI agents to search, extract & navigate the webnot reviewedEstablishedB
- Openbrowser AIAI browser automation. Write async Python to navigate, click, type, and extract data.not reviewedEstablishedB
- ZenrowsZenrows MCP server — Fetch, Extract, Batch, and Browser Sessions for AI coding assistantsnot reviewedEstablishedA
- Design System ExtractorMCP server for Storybook design systems — extract component HTML, styles and metadata.not reviewedGrowingA
- Nutrient DWS MCP ServerNutrient Processor + Data Extraction MCP: convert, OCR, sign, redact, and extract PDFs/Office docs.not reviewedGrowingA