Skip to content

Asana MCP

Asana's hosted MCP server (v2) for reading and creating tasks and projects from Claude, ChatGPT and coding tools.

Reviewed by Sheela · Updated

Setup docs Free

Our rating

4.0/5

Asana's v2 server handles the everyday jobs, but app registration, an unsupported bridge for most clients and an unpublished tool list make it harder work than its rivals.

What it is

Asana's MCP server is hosted at https://mcp.asana.com/v2/mcp and needs a client that supports Streamable HTTP and OAuth. The older beta server at https://mcp.asana.com/sse was first due to close on 11 May 2026; Asana extended that to 5 August 2026, and clients still pointed at it have lost access.

Dynamic client registration is not supported. Outside Asana's official apps in Claude and ChatGPT, someone must create an 'MCP app' in Asana's developer console to get a client ID and secret. On Enterprise+ and Legacy Enterprise, admins can allow or block each MCP client separately. A second server at /v2/command/mcp covers tickets and releases for Command by Asana licence holders.

Asana does not publish a fixed tool list; it tells you to run tools/list from your client and follow its forum changelog. Its examples include finding incomplete tasks, creating tasks, listing project sections and checking project status.

Install

https://mcp.asana.com/v2/mcp

Our review

Asana's v2 server is the supported way in and it works, but it asks more of whoever connects it than most hosted servers do. Dynamic client registration is not supported, so outside the official Claude and ChatGPT apps someone has to create an MCP app in Asana's developer console, copy a client ID and secret, and match a client-specific redirect URL exactly. For most clients other than Claude Code, Asana's own instructions route through mcp-remote, a community bridge it calls experimental and declines to support.

The security model is coarse but legible. Access is user-based with no scopes: any authorisation can call every tool, including tools added later, bounded only by what that user can already see, and actions appear under the user's name. Tokens issued to MCP apps work only against the MCP server, not the REST API, and expire after an hour, which limits what a leaked token can do.

The documentation trails the product. The beta SSE server's shutdown moved from 11 May to 5 August 2026, yet the main user page still shows the old date. The tool list is not published at all; Asana tells you to call tools/list and watch a forum changelog, which makes it hard to audit what an agent can do before you connect it.

Admin control is the strong suit on the top tiers, where Enterprise+ and Legacy Enterprise admins allow or block each client. Asana does not say whether MCP traffic shares its REST limits of 150 requests a minute on free domains and 1,500 on paid ones. If it does, the search API's separate cap of 60 a minute is the ceiling a lookup-heavy agent would meet first.

Where it earns its place

  • A marketing operations lead on Asana Advanced using Claude

    Turn a launch brief into a project with tasks and owners

    The Asana app in Claude connects with no configuration, and the model creates tasks as the signed-in user, so the audit trail is clear. There is no way to grant read-only access, so a mistaken instruction can edit real projects.

  • A developer using Claude Code who tracks sprint work in Asana

    Pull the next task and update it from the terminal

    Register an MCP app in the developer console, set its redirect to http://localhost:8080/callback, export ASANA_CLIENT_ID and ASANA_CLIENT_SECRET, and add the v2 URL. That is more OAuth plumbing than Todoist's server, whose API supports dynamic client registration.

  • An IT administrator at an Enterprise+ company

    Decide which AI tools may touch Asana data

    App management allows or blocks each v2 MCP client separately, and MCP tokens cannot be replayed against the REST API. Below Enterprise+ there is no per-client control, so any user can authorise any client.

Before you commit

Setup
Official apps in Claude and ChatGPT need no config. Other clients take https://mcp.asana.com/v2/mcp plus a pre-registered client ID and secret; Asana documents Claude Code, Codex, Cursor, VS Code, Windsurf and Kiro, most of them through mcp-remote and Node.js.
Integrations
Tools cover finding and creating tasks, project sections, project status and portfolios, but Asana publishes no list or count; tools/list is the only source. A separate Command MCP server handles Command Teamspaces, tickets and releases.
Data and privacy
Hosted by Asana; the model sees whatever the authorising user can see, with no scopes to narrow it. Access tokens last one hour and work only on the MCP server. Task descriptions and comments written by others reach the model unfiltered, a prompt-injection path in shared workspaces.
Cost at scale
No MCP fee; seats are Starter $10.99 or Advanced $24.99 per user a month billed annually ($13.49 and $30.49 monthly). Asana does not publish MCP-specific rate limits; its REST limits are 150 requests a minute per token on free domains and 1,500 on paid, with search capped at 60.
Limits
No dynamic client registration, no published tool list, and no read-only mode. The v1 beta server is gone, and Asana's official server is not in the MCP registry.

What's good

  • Hosted by Asana, with official apps in Claude and ChatGPT
  • MCP-only tokens that expire after an hour
  • Per-client allow and block on Enterprise+
  • Separate Command server for tickets and releases

What's not

  • No dynamic client registration; most clients need a registered app
  • Clients other than Claude Code lean on the unsupported mcp-remote
  • No scopes: every authorisation gets every tool
  • Tool list unpublished and docs partly out of date

Best for

Asana teams that want an assistant to look up, create and update tasks.

Alternatives

Asana MCP: common questions

Is Asana MCP worth it?
Asana's v2 server handles the everyday jobs, but app registration, an unsupported bridge for most clients and an unpublished tool list make it harder work than its rivals. We rate it 4.0 out of 5.
How much does Asana MCP cost?
Free to connect; uses your Asana plan (Starter $10.99, Advanced $24.99 per user/month billed annually). Per-client admin controls need Enterprise+ or Legacy Enterprise.
What are the downsides of Asana MCP?
No dynamic client registration; most clients need a registered app; clients other than Claude Code lean on the unsupported mcp-remote; no scopes: every authorisation gets every tool; tool list unpublished and docs partly out of date.
Who is Asana MCP best for?
Asana teams that want an assistant to look up, create and update tasks.
How much does Asana MCP cost for a team or in production?
No MCP fee; seats are Starter $10.99 or Advanced $24.99 per user a month billed annually ($13.49 and $30.49 monthly). Asana does not publish MCP-specific rate limits; its REST limits are 150 requests a minute per token on free domains and 1,500 on paid, with search capped at 60.
Is Asana MCP safe for company data?
Hosted by Asana; the model sees whatever the authorising user can see, with no scopes to narrow it. Access tokens last one hour and work only on the MCP server. Task descriptions and comments written by others reach the model unfiltered, a prompt-injection path in shared workspaces.
What are the best Asana MCP alternatives?
The closest alternatives we have reviewed are Linear MCP, monday.com MCP and Atlassian Rovo MCP Server.

Answers checked Oct 23, 2026.

Make Asana MCP? Show this rating on your siteAsana MCP rated 4.0 out of 5 on ReviewRamble