Kiln MCP Server

If you already use Kiln, the kiln mcp server is the piece that lets your assistant work with it directly. AI agent control of 3D printers — 273 tools for OctoPrint, Moonraker, Bambu, Prusa, Elegoo.

What the server does

Kiln lets AI agents (Claude Desktop, Claude Code, Codex, or any custom MCP client) drive real 3D printers end to end — Bambu Lab, Creality, Prusa, Elegoo, Voron, Sovol, AnkerMake, Artillery, FlashForge, QIDI, RatRig, and SparkX, over OctoPrint, Moonraker/Klipper, PrusaLink, and Direct USB.

• One control plane, any printer — — OctoPrint, Moonraker, Creality, Bambu Lab, Prusa Link, Elegoo, Serial. Manage a mixed fleet from one place
• No printer? No problem — — Outsource jobs to Craftcloud's 150+ manufacturing services through the hosted proxy, or use direct mode with your own provider credentials
• AI-native — — 894 MCP capabilities and 235 CLI commands built for AI agents. Not a web UI with an API bolted on
• Describe it, print it — — Natural-language to physical object pipeline: text or sketch → AI generation → validation → slice → print
• Decorate anything — — QR codes, photos, logos, text, SVGs, and procedural textures (tiger stripe, marble, camo, wood grain, honeycomb) embossed or debossed onto any model with one command
• Manuals included — — Multi-part prints can generate printable PDF assembly manuals with Bill of Materials, isometric step renders, mating arrows, and pause-and-check verification gates. (Business)

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: KILN_PRINTER_HOST, KILN_PRINTER_API_KEY, KILN_PRINTER_TYPE, KILN_OPENROUTER_KEY, KILN_SLICER_PATH, KILN_BAMBU_TLS_MODE, KILN_BAMBU_TLS_FINGERPRINT, YOUR_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

| Printer | --type | What you need | |---------|----------|---------------| | Prusa MK4/XL/Mini+ | prusalink | IP + API key (Settings › Network › PrusaLink on the LCD) | | OctoPrint (any printer) | octoprint | OctoPrint URL + API key (Settings › API) | | Klipper/Moonraker | moonraker | Moonraker URL (usually http://<ip>:7125) | | Creality K1/K2/Hi/Ender V4/V3 KE |

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by codeofaxel; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.