Asana

Twenty-seven, not the fifteen Anthropic's directory lists. Asana's own MCP Tools Reference, updated 2026-06-04, enumerates eighteen read tools, six write tools and three interactive tools. Anthropic's directory description separately claims 30+ tools, so even Asana's twenty-seven should be read as a floor rather than a complete surface.

Yes, and it cannot be undone. Asana's MCP Tools Reference documents delete_task as permanently deleting a task and any of its subtasks that are not also members of another project, stating explicitly that the action cannot be undone. This tool does not appear in Anthropic's directory listing at all, so the listing understates the connector's reach.

Yes, several tools can. Asana documents followers as users who have opted in to receive notifications, and create_tasks and update_tasks both accept a followers field. The add_comment tool supports @-mentions via GID references. Asana's spec also records a custom-field flag governing whether followers receive inbox notifications from changes to that field.

Yes. Asana's app components documentation names task created and user assigned among the triggers that automate rule actions, and it documents a two-minute delay on rule actions for newly created tasks. So create_tasks and update_tasks can fire automations a colleague configured, whose downstream effects the tool call itself never describes.

One coarse grant that narrows nothing. Reading the server's own RFC 9728 descriptor on 2026-08-21 returned scopes_supported containing the single value default. Asana states plainly that MCP apps do not use permission scopes and that authorising a client requests full access to all available tools, so reading cannot be granted without writing.

No. Asana documents that once authorised, a tool cannot access projects, tasks or data the authenticated user cannot already view in Asana. Tokens are also workspace-scoped: you select one workspace when authorising, every call in that session is confined to it, and working across workspaces requires separate sessions.

Because Claude and ChatGPT get three interactive tools the other clients do not. Asana documents create_task_preview, create_project_preview and search_tasks_preview as rendering a confirmation UI before committing a change, and states they are currently available in Claude and ChatGPT. Other MCP clients use the standard write tools directly, with no review step.

No. Asana states that tokens issued for MCP apps are valid only for the MCP server, and that standard API access requires a separate app authenticated through the normal OAuth flow. Asana also warns that the beta v1 server at mcp.asana.com/sse is deprecated and scheduled for shutdown on 05/11/2026.