Asana Official MCP Server

Asana's official V2 MCP server connects a supported assistant to the Asana Work Graph through OAuth.

Use the V2 service

The documented resource is https://mcp.asana.com/v2. Asana's old V1 beta SSE endpoint was scheduled to shut down on the publisher’s announced release. A configuration copied from an older guide can therefore point to a retired service even when its JSON is valid.

For a custom integration, pre-register an MCP app in the Asana developer console and follow the OAuth instructions. Tokens issued for an MCP app are for the MCP service; they are not general-purpose Asana API credentials. Check the documented workspace and user restrictions for the app.

Planning with evidence

Start by reading a named project's tasks and identifying overdue work or missing ownership. Include the project identifier, date boundary and status definition. If you turn a planning document into tasks, show the proposed titles, owners and deadlines before creating them. Do not invent dependencies merely to make the plan look complete.

Tool behavior differs

The current reference groups tools into read, write and interactive operations. Interactive confirmation UI is documented for Claude and ChatGPT. Other clients can expose a different interaction, so do not promise a confirmation screen everywhere.

Check the resulting project

After a change, inspect the task in Asana and confirm its project, assignee and due date. A successful tool response does not prove that an ambiguous project name resolved to the intended workspace. Compare Linear for issue-oriented planning and Notion for workspace documents.

Publisher documentation

Source 1 · Source 2