---
title: "Asana MCP V2: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/asana/
description: "Asana’s current workspace-scoped MCP connection for task, project and portfolio workflows."
---

# Asana MCP V2: review, setup & limitations · Undominated.ai

> Asana’s current workspace-scoped MCP connection for task, project and portfolio workflows.

[← Explore all mcp servers](/mcp-servers/)

PLANNING AND COLLABORATION / Asana

# Asana MCP V2

Asana’s current workspace-scoped MCP connection for task, project and portfolio workflows.

 [See setup guidance ↓](#setup)[Original source ↗](https://developers.asana.com/docs/integrating-with-asanas-mcp-server)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 3 linked sources
 Publisher Asana
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“The Asana V2 MCP server is generally available and uses OAuth for authorization.”

 [Asana · upstream description ↗](https://developers.asana.com/docs/integrating-with-asanas-mcp-server) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Uses the current V2 endpoint and registered OAuth app flow, with a session tied to the selected workspace.
- The tool reference distinguishes standard direct writes from supported interactive preview tools.
- Asana’s V2 guide says an MCP token cannot exceed the authorizing user’s existing access to workspaces, projects, and tasks.
- Dynamic client registration is not supported, MCP tokens are not valid for the ordinary Asana API, and the client list does not imply an Asana endorsement.

### A good fit for

 - Inspecting tasks, projects and portfolio context within an authorized workspace
- Creating or updating work items after reviewing the intended changes
- Reading or creating Asana work the signed-in user can already access, from a pre-registered OAuth client
- Not for calling the standard Asana REST API with the MCP token

### Weigh up before choosing

 - Standard write tools execute immediately; a confirmation interface exists only for supported interactive tools and hosts.
- The current grant exposes current and future MCP tools within the user’s existing permissions; the reviewed flow has no per-tool OAuth scope selection.
- MCP tokens do not work as general Asana REST tokens. App distribution, workspace access and some search features depend on account configuration or plan.
- Dynamic client registration is not supported. Clients must pre-register for a client id and secret.
- An MCP token does not grant permissions beyond the user, and it does not work as a standard API token.
- No licence was stated on these pages, and none was inferred.
- This review did not execute the resource.
- The server was not called.
- The Command MCP endpoint is separate, and short-lived access tokens require refresh; a V1 SSE setup is not the V2 setup.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - Official V2 setup and OAuth guide
- Current MCP tools reference
- Official client guidance
- https://developers.asana.com/docs/integrating-with-asanas-mcp-server
- https://developers.asana.com/docs/mcp-tools-reference
- https://developers.asana.com/docs/mcp-clients
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### Our findings

 - The reviewed documentation separates MCP-only tokens from REST API tokens and scopes the session to a workspace.
- Tool documentation explicitly distinguishes immediate standard writes from interactive preview behavior; no private server implementation was inspected.
- Asana says the MCP token does not grant permissions beyond the user and can only reach workspaces, projects, and tasks that user already has.
- The tools page repeats that a tool cannot access projects, tasks, or data the user cannot already view. MCP apps do not use permission scopes; authorization requests all available tools.
- Dynamic client registration is not supported on the V2 server, tokens issued for MCP apps only work with the MCP server, and inclusion on the client list does not imply endorsement by Asana.
- Tokens issued for MCP apps are limited to the MCP server and cannot be reused as standard Asana API tokens.

### Not established by this review

 - No MCP server or upstream package was installed or run.
- No authenticated account, API request, client handshake or write operation was tested.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://developers.asana.com/docs/integrating-with-asanas-mcp-server)
 - Create an MCP app in the Asana developer console and register the client redirect URL and intended distribution/workspaces.
- Configure the client for https://mcp.asana.com/v2/mcp with the registered OAuth credentials, then complete user authorization. Omit an explicit scope parameter, following the guide’s troubleshooting advice.
- Select the intended workspace and review direct write calls. Do not use the deprecated V1/SSE endpoint.

### Before you start

 - Asana account with access to the intended workspace
- A pre-registered Asana MCP OAuth app; dynamic client registration is not the documented path
- A compatible client with secure client-secret handling

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "asana": {
 "url": "https://mcp.asana.com/v2/mcp",
 "auth": {
 "CLIENT_ID": "${env:ASANA_CLIENT_ID}",
 "CLIENT_SECRET": "${env:ASANA_CLIENT_SECRET}"
 }
 }
 }
} Copy configuration ↗

### Compatibility

ChatGPT · Claude · Remote MCP clients · Configuration example is the coding-clients guide’s Cursor mcpServers block.

### Transports

Streamable HTTP

### Hosted account connection

 - Read workspace tasks, projects and portfolio information permitted to the user
- Authorized tools can create, edit, delete or comment on resources
- Standard write tools do not require a service-side confirmation preview

### Cost model

Hosted service under Asana account and feature entitlements; some advanced search capabilities depend on the plan. Client/model usage is separate.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Official service setup ↗](https://developers.asana.com/docs/integrating-with-asanas-mcp-server) Checked 2026-10-14 https://developers.asana.com/docs/integrating-with-asanas-mcp-server Supports: summary, upstreamDescription, whySelected, bestFor, install, compatibility, transports, limitations, access
- [Current Asana MCP tools ↗](https://developers.asana.com/docs/mcp-tools-reference) Checked 2026-10-14 https://developers.asana.com/docs/mcp-tools-reference Supports: install, compatibility, review, limitations, access
- [Asana MCP clients ↗](https://developers.asana.com/docs/mcp-clients) Checked 2026-10-14 https://developers.asana.com/docs/mcp-clients Supports: install, compatibility, review, limitations, access

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Trello MCP Server ↗ Atlassian-hosted endpoint that lets an AI client read, search and update Trello boards, lists, cards and checklists in one authorised workspace, over OAuth 2.0.](/mcp-servers/trello/)[### Azure DevOps MCP Server ↗ Works against one named Azure DevOps organisation, and the README says to prefer the remote server when you can.](/mcp-servers/microsoft-azure-devops-mcp/)[### Todoist MCP ↗ Reads and changes Todoist tasks, projects and schedules through Doist’s hosted service or local server.](/mcp-servers/todoist/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
