Register and manage a printer camera through Prusa Connect's Camera API
domain: connect.prusa3d.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
GET /api/v1/cameras on the printer (or the equivalent Prusa Connect camera endpoint) to list known cameras and their linked/connected/detected/stored status.
POST to the camera's config endpoint with path, driver, resolution, and trigger_scheme to register or reconfigure it.
POST to the camera's connection endpoint to link it to Prusa Connect for cloud snapshot delivery, or DELETE the same endpoint to unlink it.
GET the camera's snap endpoint to retrieve the latest captured image/png.
Known gotchas
Several camera endpoints return 503 Service Unavailable when the camera subsystem isn't ready, and 403 if the request lacks permission for that camera.
trigger_scheme controls when automatic snapshots fire (e.g. EACH_LAYER, THIRTY_SEC, MANUAL) — a MANUAL camera produces no timelapse frames unless snapshots are explicitly requested.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?