Asana

Create and update Asana tasks, projects and portfolios from an AI agent.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Asana connector does

The Asana MCP server connects an Asana workspace to Claude, ChatGPT and any MCP-compatible agent. It reads tasks, projects, portfolios, attachments, teams and users, and it creates projects, creates and updates tasks in batches of fifty, posts comments and status updates, and permanently deletes tasks. Anthropic's directory lists 15 tools; Asana's own reference documents 27.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Asana tools (15)

  • create_project_preview
  • create_task_preview
  • search_tasks_preview
  • get_status_overview
  • get_items_for_portfolio
  • get_portfolio
  • get_portfolios
  • get_project
  • get_projects
  • get_task
  • get_tasks
  • get_user
  • get_workspace_users
  • search_objects
  • update_task

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Deletion is permanent. delete_task removes a task and its non-shared subtasks with no recovery path documented. Asana's reference states the action cannot be undone.
  • The consent screen offers no choices. The server's RFC 9728 descriptor advertises a single scope, default. Asana states that MCP apps do not use permission scopes and that authorisation requests full access to all available tools. There is no read-only mode, and no delete axis.
  • One workspace per session. Tokens are workspace-scoped and selected at authorisation. Working across workspaces requires separate sessions.
  • search_tasks is Premium-gated. Asana documents it as available on Premium accounts only, directing non-Premium workspaces to get_tasks.
  • Batch calls cap at 50. Both create_tasks and update_tasks are documented at up to 50 tasks per call.
  • The confirmation UI is client-dependent. The three interactive preview tools are documented as currently available in Claude and ChatGPT only. Every other MCP client calls the immediate write tools with no review step.
  • The v1 beta server is being shut down. Asana dates the shutdown of https://mcp.asana.com/sse to 05/11/2026 and warns that clients not updated to the v2 URL will lose access.
  • Task content is user-authored text. Descriptions, comments and status updates written by colleagues enter the agent's context when read, and Asana's search_tasks searches comment bodies as well as task names.
  • No tool schemas were read. The endpoint requires OAuth, so no parameter types, constraints or safety annotations could be observed. Tool names and behaviour come from Anthropic's directory and Asana's own reference. Asana directs clients to tools/list for authoritative current schemas.

Frequently asked questions

How many tools does the Asana MCP server actually have?

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.

Can the Asana connector permanently delete a task?

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.

Will using the Asana connector email or notify my colleagues?

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.

Can the Asana MCP server trigger an Asana Rule or automation?

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.

What OAuth permissions does the Asana MCP server request?

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.

Can the connector see Asana projects I do not have access to?

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.

Why does the Asana connector ask me to review before creating a task?

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.

Does the Asana MCP token work with the regular Asana API?

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.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Asana to work.

Connect Asana once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.