Cloud MCPfleet
fleet
6 MCP tools on the Hanzo cloud door that call the fleet API.
The 6 tools tools/list names for fleet. Each dispatches to an operation in the fleet API reference.
| Tool | Route | Arguments | Description |
|---|---|---|---|
cancelFleetJob | POST /v1/fleet/jobs/{id}/cancel | 3 | Cancels a queued or running render in the caller's org. |
listFleet | GET /v1/fleet | 0 | Returns every compute unit the caller's org has, from every source, each carrying its latest utiliza |
listFleetJobs | GET /v1/fleet/jobs | 2 | Returns the caller org's gpu-jobs render queue, each row tagged with the GPU it targets (empty = the |
listFleetSamples | GET /v1/fleet/samples | 3 | Returns the caller org's utilization series, oldest first. |
listFleetWorkers | GET /v1/fleet/workers | 0 | Returns the caller org's BYO machines — the ones that dialed in via hanzo link — with everything e |
recordFleetSample | POST /v1/fleet/samples | 7 | Records a BYO worker's live GPU utilization into the SAME series the fleet board overlays. |
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?