MCP tool reference · #225 of 563 by publishers
update_task
Exposed by 13 servers from 13 publishers, read from the live servers by the Serverdex check; most of them sit in Productivity; 61.5% of them take a status parameter; the most-starred is FlowCastle (3 stars).
update_task(status?: string, description?: string, title?: string, priority?: string, id: string, …)Parameters
share = % of the 13 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| status | string | 61.5% | 12.5% | "" clears |
| description | string | 53.8% | 0% | Description |
| title | string | 53.8% | 0% | New title |
| priority | string | 46.2% | 0% | New priority level, urgent highest (optional). |
| id | string | 38.5% | 100% | Task id |
| name | string | 30.8% | 0% | Your name for the task. Unique among your live tasks; creating with an existing name updates it. |
| taskId | string | 30.8% | 100% | Required. Task id, as returned by list_tasks or create_task. |
| task_id | string | 23.1% | 100% | From get_milestone |
| assignee | string | 15.4% | 0% | "me" claims; "" releases |
| assigneeId | string | 15.4% | 0% | Assignee company_members.id (team member ID, not user ID) |
| deadline | object | 15.4% | 0% | New deadline, ISO-8601 UTC, or omit to leave it unchanged. |
| done | boolean | 15.4% | 0% | true releases the claim |
Source: the input schema each server returns for update_task, aggregated over the 13 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with update_task
13 of 13 · 13 publishers · 13 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes update_task |
|---|---|---|---|---|---|---|
| 1 | FlowCastleflowcastle · Communication | flowcastle | Communication | 3 | yes | Change one CRM task: its fields, its status, or which contacts it is linked to, in one call. Tasks live in CRM → Tasks. A task may stand alone or be linked to contacts. While leads are on for the workspace, linking parks the contact's open lead until the task is done (parkLeads, default true), and marking the task done brings the linked leads back to Waiting on us so someone tells them the result |
| 2 | cnvs.applksrz · Other | lksrz | Other | 1 | yes | Update an existing task by `id` (from `list_tasks`). Pass only the fields you want to change: `name`, `description`, `due_date`, `priority` ('H'|'M'|'L'), `assignee`, `done` (true once completed), `column_id` (to reassign), `sort`. To move a card between columns while setting its order, `move_task` is the dedicated tool. |
| 3 | 402cron402cron · Productivity | 402cron | Productivity | — | yes | Change the schedule, destination, method, timeout, headers or body of an existing task. Omit a field to leave it unchanged — sending null is refused, because "unchanged" and "cleared" must not look the same. State is NOT editable here: use pause_task and resume_task. |
| 4 | workload.zerogetitdone-gmbh · Business & CRM | getitdone-gmbh | Business & CRM | — | yes | Update a task. Give only the fields to change; assignedTo, tags and links replace the existing lists. Archive with status "archived". |
| 5 | TeamMeettheguysaccount · Productivity | theguysaccount | Productivity | — | yes | Sets a task's status (working, done or blocked) with a short note and links. The call the task came from sees the update in its chat. |
| 6 | Mundanesttruji · Media & Creative | sttruji | Media & Creative | — | yes | Amend an unassigned task instead of cancel-and-repost. Supply only the fields to change; at least one is required. Material changes (title, instructions, location, capabilities, proof requirements) re-run the FULL screening cascade — the response's `status` may come back `rejected` — and withdraw any pending offer with an automatic escrow refund. Budget or deadline-only changes skip re-screening b |
| 7 | AIOProductOS MCPaioproductos · Data & Analytics | aioproductos | Data & Analytics | — | yes | Update one or more of a task's fields and return the updated task; fields you omit are left unchanged (idempotent — re-sending the same values is a no-op). Pass sprint_id: null to remove the task from its sprint. Resolve ids first — the task via get_task/list_tasks, and status/feature/insight/sprint/member ids via pm_meta and the list_* reads — never guess them. Only id is required. |
| 8 | Forge Enginealongkornonline2019 · Developer Tools | alongkornonline2019 | Developer Tools | — | yes | Edit a task or CLAIM it — DIRECT. assignee:"me"+status:"in-progress" claims (errors if held; force:true for stale); done:true or assignee:"" releases. |
| 9 | Mailcannonainaluc · Communication | ainaluc | Communication | — | yes | Update a task's status, priority, or fields |
| 10 | FavCRMfavcrm · Business & CRM | favcrm | Business & CRM | — | yes | Update a task (status, priority, assignee, due date, completion). |
| 11 | Ganty MCPhomareyoshizaki · Data & Analytics | homareyoshizaki | Data & Analytics | — | yes | Update fields of an existing task. Only provided fields will be modified. |
| 12 | Todoursverrirvalgeirsson · Productivity | sverrirvalgeirsson | Productivity | — | yes | Update a task's content (todo.txt). Only the task owner may update. |
| 13 | ContextLayerdotnova · Documents & Knowledge | dotnova | Documents & Knowledge | — | yes | Update a task's status, title, description, priority, or team assignment. Use this to move tasks through the workflow (todo -> in_progress -> done) or reassign to a team. |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.