Moonraker for Meta Muse
Control a Klipper-based 3D printer through the Moonraker API server (the backend behind Mainsail, Fluidd and RatOS): read server and print status, list and upload gcode files, start/pause/resume/cancel prints, trigger the emergency stop, toggle smart-plug devices, and (gated) run raw G-code. Use when the user mentions Moonraker, Klipper, Mainsail, or Fluidd.
View original source ↗How to set it up
Paste a promptDraft — these instructions come from the linked source and have not been independently live-tested by OpenTools.
Before you start
- no credential needed on most LAN installs (optional API key via the secure credential flow)
Steps
- Paste the install prompt into a chat with Muse.
- Muse fetches the pinned SKILL.md and the 2 files in its manifest.
- Authorize your own account through Muse’s secure credential flow.
- Have Muse run the status check shown in the source skill.
Prompt to paste into Muse
Install this connector: https://raw.githubusercontent.com/bluman1/muse-connectors/6e31fd44a71f9f28377a1460e64cd7483c3cce22/connectors/moonraker/SKILL.md Read its Files manifest and install exactly those files. Collect credentials through Muse's secure credential flow; never ask me for raw keys in chat. Run the skill's status check and report the result.
Account access: Moonraker has no auth on the LAN by default, so most installs need nothing stored at all. If the printer enables `[authorization]` API keys, store the key via the secure credential flow (`credentials.request_api_access`) as `custom.moonraker` and pass `--api-key` on each call. The key is never passed on the command line, in the environment, or in a file: `--api-key` is a flag that takes no value.
Allowed hosts: the host you pass via --host
Confirm it works: `bin/moonraker.py auth` (must return `"ok": true`; also reports whether an API key is stored)
Services it connects with
These are the services the connector uses. The publisher is identified separately.
Moonraker