MCP tool reference
Every tool the Masaro MCP server exposes. Your agent discovers these automatically on connect; this page is for humans who want to know exactly what a connected agent can and can't do.
All tools operate inside the single workspace the connection was authorized for. There is no cross-workspace access on one connection.
Context: reading the board
| get_workspace_context | The workspace at a glance: board shape, projects, conventions, memory. The standard first call of a session. |
|---|---|
| get_project_context | Deeper context for one project: its memory and decisions. |
| find_tasks | Filter tasks by status, epic, or tags, or list what’s assigned to you. No free-text search. |
| get_task_detail | One task in full: description, acceptance criteria, dependencies, comments, activity. |
| get_next_task | The next workable task: Ready, unblocked, agent-appropriate. The “give me work” call. |
Work: the execution loop
| claim_task | Take a task. Moves it to In Progress under the agent's identity; prevents duplicate pickup. |
|---|---|
| update_progress | Report a meaningful chunk of progress (setup, core implementation, tests, PR opened). Lands on the activity feed; doubles as the liveness heartbeat. |
| complete_task | Deliver: a summary plus an optional met/not-met mapping per acceptance criterion. Moves the task to In Review; returns any tasks that became unblocked. |
| report_blocker | Stuck on something needing human input. Notifies you immediately with specific unblocking questions. |
| release_task | Put a claimed task back to Ready without completing it: clean hand-back, no zombie claim. |
Authoring: proposing work
| create_task | Create a task (title, description, criteria, complexity, labels). Top-level tasks land in Triage for your accept/decline; subtasks land in the backlog. |
|---|---|
| update_task | Edit an existing task's fields. |
| create_epic | Create an epic to group related tasks. |
| link_tasks | Declare relationships: blocks, relates_to, duplicate_of. |
| add_comment | Comment on a task: questions, findings, context for the reviewer. |
Guardrails, summarized: one workspace per connection · authoring lands in Triage under the default supervised policy · every action is attributed to the agent’s identity on the activity feed · access is revocable from Masaro at any time.