Supervisor MCP Reference

// 1. Name the signal.
events {"action": "create", "payload": {
  "name": "qa_passed",
  "payloadGuidelines": "Include the build number and the pass/fail counts."
}}  // -> { id: "0hNRmEWoU5Z", ... }

// 2. Say what should happen when it fires.
events {"action": "createTrigger", "payload": {
  "eventId":     "0hNRmEWoU5Z",
  "workspaceId": "0eCTDeDXETx",
  "title":       "Ship the release",
  "body":        "QA signed off:\n{{EVENT_PAYLOAD}}",
  "emitEventId": "0hDXw48jLfd"   // publishes deploy_finished on completion
}}

// 3. Check the system is actually running.
events {"action": "listTasks", "payload": {"eventId": "0hNRmEWoU5Z"}}

// 1. Create the graph around a start event.
workflows {"action": "create", "payload": {
  "name":         "release-pipeline",
  "startEventId": "0hNRmEWoU5Z"   // qa_passed
}}  // -> { id: "0hWfK92pXqL", ... }

// 2. Add a step: when the start event fires, create a task here.
workflows {"action": "createStep", "payload": {
  "workflowId":  "0hWfK92pXqL",
  "eventId":     "0hNRmEWoU5Z",
  "workspaceId": "0eCTDeDXETx",
  "title":       "Ship the release",
  "body":        "QA signed off:\n{{EVENT_PAYLOAD}}",
  "emitEventId": "0hDXw48jLfd"   // publishes deploy_finished on completion
}}

// 3. Check the system is actually running.
workflows {"action": "listTasks", "payload": {"workflowId": "0hWfK92pXqL"}}

Calling the Tools: Action and Payload

The supervisor has nine tools: workspace, task, memory, skills, events, workflows, machines, pano and help. Every tool takes exactly two inputs: action, the thing to do, and payload, that action's fields. payload is left out when an action takes nothing.

task {"action": "create", "payload": {"workspaceId": "0ZzhYQG2qtl", "title": "Release v0.9.20"}}
machines {"action": "createEnrolmentCode"}

Each action checks its payload strictly. An unknown field or a missing required one is refused with an error that names the action, so a typo fails loudly instead of being ignored. In prose these docs write an action as task → create.

Ask help for the exact payload

This page lists every action and shows an example, but it does not copy every field. The server documents itself: the help tool prints the tools, a tool's actions, or one action's payload fields and an example call. Every other tool also has a help action, which does the same for that tool: task {"action": "help", "payload": {"topic": "create"}}.

help {}                            // every tool and its actions
help {"action": "events"}         // one tool's actions
help {"action": "task.create"}    // one action's payload and an example

Every tool takes {"action": "<action>", "payload": {...}}.

Tools:
  workspace    The account's workspaces, and their forks.
               actions: list, create, get, update, stats, fork, mergeFork
  task         The tasks of every workspace.
               actions: list, listAll, create, get, reply, respond, updateStatus, updateSortingOrder, updateAssignee, updateAllowAll, updateSchedule, delete, getAttachment
  memory       A workspace's memory, read-only.
               actions: list, get
  skills       The account's skills as a workspace sees them, read-only.
               actions: search, get
  events       Named signals, and the triggers that turn them into tasks.
               actions: list, create, get, update, delete, listTasks, listTriggers, createTrigger, getTrigger, updateTrigger, deleteTrigger
  workflows    Graphs of events and the workspaces they hand off to.
               actions: list, create, get, getText, update, delete, replaceFromText, listSteps, createStep, deleteStep, listTasks
  machines     Machines running agentrqd, and the agents on them.
               actions: list, createEnrolmentCode, launchAgent, stopAgent
  pano         Markdown docs every workspace of the account shares.
               actions: save, read, comment, attach, delete

Run help {"action": "<tool>"} for a tool's actions, or {"action": "<tool>.<action>"} for one action's payload and an example.

Usage: events {"action": "<action>", "payload": {...}}

Actions:
  list                 List the account's events.
  create               Define a named signal that workspaces publish and triggers react to.
  get                  Get an event.
  update               Revise an event's payload guidelines. Its name is fixed once created.
  delete               Delete an event. Its triggers stop firing.
  listTasks            List the tasks an event has spawned, to see whether what was wired up is running.
  listTriggers         List an event's triggers: everything that happens when it fires.
  createTrigger        React to an event: when it fires, create a task in a workspace.
  getTrigger           Get an event trigger.
  updateTrigger        Rewrite an event trigger.
  deleteTrigger        Delete an event trigger, leaving its event in place.
  help                 This list, or with payload {"topic": "<action>"} that action's payload.

Usage: task {"action": "create", "payload": {"workspaceId": <string>, "title": <string>, ...}}

Create a task in a workspace, assigned to the human unless assignee says otherwise.

Write the full context into body: the receiving agent has nothing else. cronSchedule makes it a scheduled task: a recurring one runs at most hourly, a one-time one fixes dom and month.

Required:
  workspaceId          string   The workspace's ID (base62).
  title                string   The task's title.

Optional:
  body                 string   The task's body: what is to be done.
  assignee             string   One of: human, agent.
  cronSchedule         string   A 5-field cron schedule (minute hour dom month dow) to run the task on. A recurring task is at most hourly: a single minute 0-59, e.g. '30 * * * *'. A one-time task fixes dom and month, e.g. '30 14 25 4 *'.
  parentId             string   The task this one belongs under (base62).
  clearContext         boolean  Ask for a clean slate: /clear is sent to the agent's terminal before this task is handed over, so it starts without the previous task's context. Ignored when the target workspace has no running Claude Code session. Defaults to the target workspace's own setting.

Example:
  task {"action": "create", "payload": {"workspaceId": "0ZzhYQG2qtl", "title": "Release v0.9.20", "body": "Tag main and publish the release notes.", "assignee": "agent", "clearContext": true}}

workspace {"action": "create", "payload": {"name": "release-notes", "description": "Writes the release notes for every tag."}}
workspace {"action": "stats", "payload": {"id": "0ZzhYQG2qtl", "range": "7d"}}

task {"action": "create", "payload": {
  "workspaceId": "0ZzhYQG2qtl",
  "title": "Release v0.9.20",
  "body": "Tag main and publish the release notes.",
  "assignee": "agent",
  "clearContext": true
}}

// Answer a waiting permission request
task {"action": "respond", "payload": {"workspaceId": "0ZzhYQG2qtl", "taskId": "0kGogHmaqvZ", "action": "allow"}}

memory {"action": "get", "payload": {"workspaceId": "0ZzhYQG2qtl", "name": "memory.md"}}

skills {"action": "search", "payload": {"workspaceId": "0ZzhYQG2qtl", "q": "release"}}
skills {"action": "get", "payload": {"workspaceId": "0ZzhYQG2qtl", "uri": "skill://release-notes"}}

events {"action": "createTrigger", "payload": {
  "eventId": "0kEvt7hQx2M",
  "workspaceId": "0ZzhYQG2qtl",
  "title": "Write the release notes",
  "body": "{{EVENT_PAYLOAD}}",
  "emitEventId": "0kEvt9notes"
}}

workflows {"action": "replaceFromText", "payload": {
  "workflowId": "0kWfl5mN2pQ",
  "text": "- event:release_tagged\n  - agent:release-notes\n    - event:notes_ready"
}}

machines {"action": "createEnrolmentCode"}
machines {"action": "launchAgent", "payload": {"workspaceId": "0ZzhYQG2qtl", "machineId": "0kMch4rT8uV", "kind": "claude-code", "model": "opus"}}

pano {"action": "save", "payload": {"title": "Release plan", "markdown": "# Release plan\n\n- [ ] Tag v0.9.20", "color": "green"}}