MCP field guide / Asana
// mcp field guide · project management
Like Linear, a project-management MCP is a low-to-moderate guard case: read-and-triage dominates, and most writes undo with a follow-up edit. The value concentrates in three spots — delete_task (which Asana itself labels "cannot be undone"), bulk writes (up to 50 objects per call), and comments that notify real people.
GUARD FIT · READ + SINGLE WRITES
LOWSearch/get, and one-off create/update tasks or projects — reversible by a follow-up edit. Little to gate.
GUARD FIT · DELETE + BULK + NOTIFY
SELECTIVEdelete_task (vendor-labeled irreversible), bulk create/update up to 50, and @-mention comments/status updates.
Overall fit: WEAK → MODERATE — strong only on delete_task; moderate on bulk writes and notification-emitting tools.
Asana's official server is hosted (mcp.asana.com/v2/mcp, OAuth 2.0, GA — the V1 beta shut down Aug 5, 2026). It gives an agent read/write access to the Asana Work Graph (tasks, projects, portfolios, goals, teams), including interactive "preview" tools that render an in-client approval UI before a change commits. Asana states the tool set evolves — call tools/list for the live roster.12
| Tier | Tools |
|---|---|
| read-only | search_objects, get_task/get_tasks/get_my_tasks, get_project/get_projects, get_portfolio, get_status_overview, get_user/get_me; preview variants create_task_preview/create_project_preview |
| mutating | create_tasks (up to 50), update_tasks (up to 50), create_project, add_comment (@-mentions notify), create_project_status_update (notifies followers) |
| destructive | delete_task — Asana's own text: "Permanently deletes a task… This action cannot be undone." No delete_project tool is exposed. |
One nuance we flag rather than assert: Asana's delete_task says "cannot be undone," yet in the Asana product/REST API deleted tasks normally go to trash for a window (~30 days). Whether the MCP tool bypasses trash or the wording is conservative framing is unverified — so we treat it as irreversible until confirmed. And add_comment/create_project_status_update aren't destructive to data, but they emit user-facing notifications that can't be "unsent."
Status synthesis. Read get_my_tasks/get_status_overview and draft a project status, optionally posting it.
Bulk task intake. Turn a transcript into up to 50 tasks in one create_tasks call (with a preview approval step in the client).
Triage & grooming. Search, then update_tasks in bulk to reassign/re-date/close stale tasks; add_comment to loop in owners.
Reads and single writes → low. Search/get change nothing; a wrong due date or assignee is cheap to fix.
The three real spots:
create_tasks/update_tasks touch up to 50 objects per call; a bad batch is tedious to reverse by hand even if each item is technically reversible. An impact diff ("50 tasks will be reassigned") before commit is genuinely useful.delete_task — the one tool Asana labels permanent. Destructive, vendor-unrecoverable, worth a human confirm every time.Honest bottom line: for a guard, Asana is weak-to-moderate — strong only on delete_task (irreversible, no compensation possible), moderate on bulk writes and notification-firing tools. Creates compensate by deletes and updates by inverse-updates; deletes and sent notifications are the "compensation ≠ reversal" cases. Right-size the control — gate the dangerous subset.
ChronoMCP passes reads and one-off edits through, and holds delete_task, bulk writes and notification-emitting actions for a human.
Profiles describe third-party software from its public sources; ChronoMCP is not affiliated with Asana. Tool names are from Asana's official reference; the exact total count and whether delete_task bypasses trash are noted as unverified. The tool set evolves — call tools/list for the live roster. Risk groupings are our classification. Sources current as of Aug 2026.