Tasks

To-dos and follow-ups, including batched and idempotent writes.

16 tools — 4 read, 12 write.

Tool		What it does
add_task_dependency	write	Add a dependency between two tasks: taskId blocks blockedById (so blockedById is blocked by taskId).
cancel_task	write	Cancel a task.
complete_task	write	Mark a task as done.
create_subtask	write	Create a subtask under a parent task.
create_task	write	Create a new task (action item).
delete_task	write	Delete a task permanently, including its dependency edges and search index entry.
get_task	read	Read one task in full by id — its state, owner, due date, tags, links, blockers and subtasks.
list_task_tags	read	List the distinct tags used on tasks you can reach.
list_tasks	read	List the tasks you can reach — your own, those assigned to you, those in your spaces and those shared with you — optionally filtered by state, owner, priority, due range, or tags.
remove_task_dependency	write	Remove a dependency between two tasks (the taskId → blockedById blocking edge).
reopen_task	write	Reopen a done or cancelled task, returning it to the open state.
search_tasks	read	Search existing tasks by keyword (matches title, description, and tags, case-insensitive).
set_task_parent	write	Set (or clear) a task's parent.
start_task	write	Mark a task as in progress.
update_task	write	Patch a task.
upsert_tasks	write	Create many tasks in ONE call (max 500), idempotently.

Calling these

Over MCP, find one with search_tools, then run it with execute_tool. Over REST, POST /api/capabilities/<tool> with the arguments as the JSON body. Either way, fetch the input schema for the tool you're about to call rather than guessing — get_tool_schema over MCP, or GET /api/capabilities?name=<tool> over REST.

See How the API works for auth, errors and the shared envelope.