Kiln for print farms

The control layer for AI-ready printer rooms.

Kiln gives agents using MCP, plus CLI and CI workflows, one safe local control path for mixed printer fleets: discover, validate, slice, upload, start, monitor, and stop jobs through adapter-aware guardrails.

Install Kiln See Business options
7 printer backends
MCP agent-native control
LAN local-first operation
CI fleet checks ready

The actual farm problem

More printers usually means more control surfaces.

A serious print room rarely standardizes forever. One team adds a Bambu Lab printer for speed, a Creality machine for large-format throughput, a Prusa for reliability, a Klipper machine for tuning, and an OctoPrint box for the older workhorse. Kiln turns that pile of interfaces into one local printer-control layer an agent can reason about.

Operating model

Built around the room, not one brand.

01

One control contract for the room

Agents using Kiln's MCP server, plus CLI and CI workflows, can inspect printer state, temperatures, files, jobs, materials, and snapshots instead of hopping between vendor tools.

02

Safety before motion

Starts route through preview confirmation, printer profiles, bed-fit checks, material guidance, and adapter-aware upload flows. Kiln gives agents a responsible path to physical hardware.

03

Real mixed-fleet coverage

Bambu Lab, Creality, Prusa Link, Elegoo, OctoPrint, Moonraker/Klipper, and direct USB can live behind the same local control layer.

04

Automation without moving private code

Public Kiln exposes the local MCP and CLI contract. Business and Enterprise workflows can stay in private infrastructure without shipping private code.

Printer coverage

Farm-ready because the adapters are real.

Kiln does not need every printer to speak the same protocol. It needs each adapter to expose the same safe operations to the agent.

Bambu Lab

MQTT + local network

A1, P1, and X1 families through the dedicated Bambu adapter.

Creality

Moonraker / Klipper

K1, K2, Hi, Ender V3 KE, and CrealityOS machines when local Moonraker is reachable.

Prusa Link

REST

Prusa printers through Prusa Link with adapter-level safety handling.

Elegoo

SDCP WebSocket

Supported Elegoo SDCP/WebSocket printers such as Centauri Carbon; Neptune printers use Moonraker when exposed.

OctoPrint

REST

A stable path for many older, modified, and farm-managed printers.

Moonraker / Klipper

HTTP / WebSocket

Generic Klipper-class machines when their Moonraker API is reachable on the local network.

Direct USB

USB serial

Marlin and RepRapFirmware printers when a direct cable is the right control path.

Clean public/private boundary

Open infrastructure below. Business and Enterprise fleets above.

This is the line that lets the public package stay useful while Business and Enterprise workflows remain protected.

Pro is intentionally limited to one printer. Fleet features belong to Business and Enterprise.

Public Kiln

Local printer adapters

Connect and normalize supported printer backends on the same LAN or USB host.

MCP and CLI tools

Expose printer operations, validation, slicing, monitoring, and model workflows to agents and scripts.

Safety profiles

Keep printer-specific dimensions, temperature limits, material guidance, camera support, and multicolor capabilities close to the adapter layer.

Business and Enterprise layer

Hosted account workflows

Keep account-aware execution outside the public package when teams need Business or Enterprise controls.

Fleet and recovery workflows

Business and Enterprise routing, recovery, and team operations live privately in kiln-pro. Pro is for a single printer.

Commercial controls

The public package can discover and proxy eligible pro tools without moving proprietary implementations into the public repo.

Who this is for

Rooms where print failure has a real cost.

Kiln is useful for a hobby bench. This page is for rooms where printers are production equipment, and the team needs an MCP and CI path that keeps up with the room.

Custom merch and short-run production

Repeated designs, mixed materials, and tight turnaround need printer status that an agent can trust before every job.

Prototype and product teams

Different printer types can share one validation and launch path while engineering keeps control over approved profiles.

Education and research labs

Shared fabrication rooms get a local MCP and CI command path that staff can document once and agents can respect every time.

In-house manufacturing

Jigs, fixtures, replacement parts, and low-volume production benefit from predictable setup across brands and teams.

Start local, scale cleanly

Give every agent the same printer surface.

Install Kiln, connect the printers already in the room, and make the local control layer solid before layering on Business workflows.

Install Kiln Check integrations Pricing