Asana MCP Server – Tasks and Project Workflows
Asana's official V2 MCP server gives AI assistants permission-aware access to the Asana Work Graph. Use it to search workspace data, create and update tasks and projects, review portfolios, generate summaries, and coordinate work from an MCP-compatible client.
Overview
Asana's official V2 MCP server connects compatible AI assistants to the Asana
Work Graph. It gives an agent live, structured access to permitted workspace
information and supported actions, rather than limiting the workflow to text
copied manually from tasks, projects, or portfolios.
What the MCP server enables
Asana documents MCP capabilities for searching, retrieving, creating, updating,
and analyzing workspace objects. Depending on the current tool set, the user's
permissions, and workspace app-management policies, an AI agent can:
- Search for tasks, projects, portfolios, and other supported work objects.
- Retrieve task, project, portfolio, section, and status information.
- Create and update tasks and projects through natural-language instructions.
- Find incomplete or overdue work and filter tasks by date or ownership.
- Generate reports, summaries, and project-status overviews.
- Analyze workload and project data for planning and coordination.
- Use the MCP
tools/listcommand to discover the server's current tools.
When to use it
Use Asana MCP when an AI workflow needs current workspace context or must
perform an authorized work-management action. Typical examples include finding
tasks due this week, creating an assigned task in a project, reviewing project
sections, summarizing a portfolio, checking project status, preparing planning
reports, and coordinating follow-up work directly from an AI assistant.
Connection and authentication
The generally available V2 endpoint is
https://mcp.asana.com/v2/mcp over Streamable HTTP. Authentication uses OAuth
2.0 with an MCP app created in the Asana developer console. The app provides a
client ID and client secret, requires one or more exact redirect URLs, and can
be distributed to selected workspaces or any workspace.
Dynamic client registration is not supported. Clients must use pre-registered
credentials and complete the browser-based authorization flow. MCP access
tokens are specific to the MCP server, expire after one hour, and should be
renewed with the OAuth refresh-token flow.
Key considerations
Access remains limited by the signed-in user's Asana permissions and by
workspace app-management controls. Administrators can block or approve MCP apps,
and integrations distributed to specific workspaces must include at least one
permitted workspace. Keep client secrets and tokens in a secure credential
store, use HTTPS, implement token refresh, and revoke credentials when no longer
required. The former V1 SSE endpoint was deprecated and shut down on May 11,
2026, so new integrations should use only the V2 Streamable HTTP endpoint.
Supported Transports
streamable_http
URL: https://mcp.asana.com/v2/mcp
Frequently Asked Questions
- When should an AI agent use the Asana MCP server?
- Use it when a workflow needs current Asana workspace context or authorized actions, such as finding tasks, creating or updating work, reviewing projects and portfolios, checking status, analyzing workload, or generating planning and progress summaries.
- What does the Asana MCP server add to an AI agent's capabilities?
- It gives the agent structured, permission-aware access to the live Asana Work Graph, allowing it to search, retrieve, create, update, and analyze workspace information instead of relying only on static model knowledge or manually pasted task data.
- What can an AI agent access or manage through Asana MCP?
- Depending on the current tools and user permissions, the agent can work with tasks, projects, portfolios, sections, assignments, due dates, status information, search results, reports, summaries, and supported creation or update operations.
- How is authentication configured for the Asana MCP server?
- Create an MCP app in the Asana developer console, configure exact redirect URLs and workspace distribution, and provide its client ID and client secret to the MCP client. The client completes OAuth 2.0 authorization and sends the resulting access token as a Bearer token. Dynamic client registration is not supported.
- Which transport should be used for the Asana MCP server?
- Use Streamable HTTP with https://mcp.asana.com/v2/mcp. Asana's former V1 SSE endpoint was deprecated and shut down on May 11, 2026, so it is not included in this YAML.