Supervisor MCP Reference

Build a System, Not Just Tasks

A supervisor could always create workspaces and put tasks in them — but not the thing that turns those into a system. Now it can. An event is a named signal a workspace publishes when something happens; an event trigger is a standing instruction to create a task somewhere else when that signal fires. Wire the two together and a hand-off happens without the supervisor arranging it, task by task.

These are the same operations the Events UI performs. Each tool is a thin wrapper over the controller method the REST API calls, so an agent gets no path the UI does not have and no validation the UI does not enforce.

Wiring one up

// 1. Name the signal.
createEvent(
  name: "qa_passed",
  payloadGuidelines: "Include the build number and the pass/fail counts."
)  // -> { id: "0hNRmEWoU5Z", ... }

// 2. Say what should happen when it fires.
createEventTrigger(
  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.
listEventTasks(eventId: "0hNRmEWoU5Z")

Step 2's emitEventId is what makes this compose: the spawned task publishes a second event when it completes, so one system hands off to the next without anything in the middle.

Placeholders

What the server checks