ToolBB-0194

klipper-mcp: watch and drive a Klipper 3D printer from an MCP client

klipper-mcp connects Claude or another MCP client to a Klipper 3D printer through Moonraker's HTTP and websocket APIs. Its 14 tools read status and history and control temperatures, prints and G-code; control tools preview first and act only when confirmed. A separate recorder logs how each print ended. The README names no printer it was tested on.

Open original source github.com · Max Ellis

Claimed
Why this evidence label?

The author describes it but shows no evidence we could check yet.

How we check entries
Preview image for klipper-mcp: watch and drive a Klipper 3D printer from an MCP client
The source's own preview image, from github.com.

Briefing

Four tools are read-only, nine control the printer, among them send_gcode, start_print and emergency_stop, and the last is record_verdict. Every control tool except emergency stop returns a preview first and acts only with confirm=true. Temperatures are capped at 300 C for the extruder and 110 C for the bed.

The recorder, klipper-mcp-capture, runs under systemd and saves each finished print's result, duration, filament grams and slicer settings. Authentication is LAN-only. The code is AGPL-3.0-only.

From the GitHub API

Repository facts

Repository facts for maxellis/klipper-mcp, from the GitHub API
Repositorymaxellis/klipper-mcp
Stars2
LanguagePython
Last push9 Oct 2026 20 d ago

Tags

Agent
Interface

Report a problem with this entry