HARDWARE CONTROL LAYER
Print-farm MCP
A Python MCP server that puts a heterogeneous seven-machine printer fleet and a slicer CLI behind a single agent-operable interface.
Employment work. Architecture only; the company owns the code.
MECHANISM
Five protocols, one interface
The fleet has no two machines alike and each sits on a different control stack. Adapters cover Moonraker, PrusaLink, Elegoo SDCP, Flashforge and Creality LAN, with network discovery and camera capture, so an agent sees one fleet rather than five vendors.
- AGENT Any MCP client sees one fleet, not five vendors
- MCP SERVER One interface Python, with a slicer CLI behind it discoverobservecameraslice
- GATE Dispatch is confirmed committing filament and machine hours is a separate, explicit act
- ADAPTERS Five wire protocols MoonrakerPrusaLinkElegoo SDCPFlashforgeCreality LAN
- FLEET Seven printers no two alike
DESIGN
A gate between decision and action
An agent can slice a model and send it to a machine, but the step that commits filament and machine hours is a separate, explicit act. That is the difference between a model deciding something and a model doing it, and it is the same boundary the public evaluation suite makes reproducible.
EVIDENCE
Evidence from the machines themselves
A verification harness exercises every adapter against the live hardware, read-only, so adapter health is measured against the actual fleet rather than against mocks.
IN AN INTERVIEW
The two-minute walkthrough
-
0:00
Name the boundary first: employment IP, so architecture only.
A boundary an employer will need respected too.
-
0:15
Walk the diagram from agent to fleet.
Heterogeneity is the hard part: seven machines, five protocols, one interface.
-
0:50
Stop at the gate.
The difference between deciding and doing: dispatch commits material and machine hours, so it is a separate, confirmed act.
-
1:30
Bridge to the public evals.
The same concern, made reproducible in public with a clean-room simulator.