Set up Asana MCP Server

What the Asana MCP Server is

The Asana MCP Server is the official implementation of the Model Context Protocol standard by project management provider Asana. Per the provider, the server gives AI assistants and other applications access to the Asana Work Graph, the connected structure of tasks, projects, portfolios, goals, and teams. This allows tasks and projects to be created and managed through natural language, reports and summaries generated from Asana data, and project data analyzed with AI-powered insights. The current V2 server is reachable at mcp.asana.com/v2/mcp; per the documentation, an older beta version at mcp.asana.com/sse is scheduled to be shut down on a fixed date, so clients should migrate to the V2 address.

Prerequisites and connecting

Per the provider, using the server requires an MCP client that supports the Streamable HTTP transport protocol; a list of compatible clients is maintained in Asana's documentation. In addition, the client application in use must not be blocked via the organization's own Asana app management, or a prompt will appear during authorization asking the user to request that an administrator unblock it. The connection itself is established via OAuth: the client is configured to point at the V2 server address, after which the user is prompted to authenticate with their own Asana account and authorize access. Per the provider, clients that don't handle this flow automatically may need a client ID and client secret pair generated through Asana's integration guide.

Available tools

Per the reference documentation, the server exposes three categories of tools. Read tools return data from the workspace without making changes, such as search_objects for a universal search across tasks, projects, portfolios, goals, teams, users, tags, and custom fields, or get_task for the full details of a single task including subtasks and comments. Write tools create, modify, or delete data in the workspace. Interactive tools additionally render a confirmation UI before a change is committed; per the provider, this variant is currently available in Claude and ChatGPT. Since the exact tool list, per the provider, keeps evolving, it is recommended to use the tools/list command within the client to always see the current set.

Access rights and security

A notable detail per the documentation is that MCP apps in Asana do not use granular permission scopes: once a user authorizes an MCP client, the issued token automatically requests access to all available tools. The actual restriction comes from the authenticated person's existing Asana permissions, so a tool can only access projects and tasks the user could already view in Asana anyway. Customers on the Enterprise+ or Legacy Enterprise tiers can selectively block or allow individual MCP clients via Asana's app management; on other tiers, doing so requires a request to Asana Support submitted by a super admin.

Practical value and limits

Day to day, the server suits requests such as listing all incomplete tasks due this week, creating a new task in the right project, or checking the status of an ongoing project, all directly from a conversation with the assistant without manually opening the Asana interface. Per the provider, there is a separate, more detailed guide for connecting coding-focused clients such as Claude Code, Codex, Cursor, or VS Code. The limit is that, absent granular permission scopes, every authorization grants full tool access within the bounds of the user's own permissions; anyone needing finer control must manage it through Asana's own role administration rather than through the MCP server itself. For connection problems, the provider recommends signing out and back in, and verifying that the necessary workspace permissions actually exist.