Skip to main content
25 tools, a set of docket:// resources, and 3 prompts. Each is named for what the caller is trying to do.

Tools

Reading: 5 tools

find reads the same permission-filtered index the web app reads. That index updates a moment after a write.list_work filters on team, project, assignee, delegate, state, priority, label, cycle, due window, blocked-ness, and the triage queue. Pass a filter the chosen entity has no column for and the call fails, naming the filters that entity does support.get returns a task with its dependencies and subtasks, and lists the references you cannot see in missing.
Every write records an undoable change set. Call undo once and Docket reverses forty edits.

Scopes per tool

See Authentication for requesting and stepping up scopes.

Resources

The same data, read as resources. An item you cannot see looks like one that does not exist. Everything else is templated:
Where type is one of task, project, program, initiative, cycle, team, update, comment, session, agent, view, or org.

Subscriptions

Call resources/subscribe, then open the GET /mcp stream and Docket sends notifications/resources/updated. Delivery is best-effort and never replayed. Read the resource again when one arrives.

Prompts

Widgets

Hosts that render MCP Apps get UI resources under ui://docket/* for every entity type, plus work lists, plans, and change reports. Other hosts get the structured results.

Server capabilities

tools.listChanged, resources.subscribe, resources.listChanged, prompts.listChanged, completions, and logging. A deployment flag turns on experimental MCP task support.
tools/list returns only the tools your grants allow. Change one and Docket sends notifications/tools/list_changed immediately.