Does the Asana MCP server work with Claude?

Yes. Asana ships an official, OAuth-authenticated MCP server at https://mcp.asana.com/v2/mcp that works with any MCP client, including Claude Cowork, Claude Code, and Claude Desktop. Asana lists Claude and Claude Code as compatible clients.

Is there an official Asana MCP server?

Yes. Asana maintains an official V2 server. There's also a popular community server (roychri/mcp-server-asana) that runs locally with a personal access token. For most teams the official server is the right default.

Is the Asana MCP server free?

The server itself is free to use. You authenticate with your existing Asana account, so you only pay for whatever Asana plan you already have. A few tools, like advanced task search, require a Premium-or-higher Asana workspace.

Can the Asana MCP server create and update tasks, not just read them?

Yes. The official server exposes write tools like create_tasks, update_tasks, add_comment, and create_project_status_update, alongside read tools. In Claude and ChatGPT, task and project creation runs through a confirmation preview before anything is written.

Asana MCP Server: What It Does & How to Use It with Claude

The Asana MCP server lets an AI assistant read and act on your Asana Work Graph. It searches tasks, creates and updates work, posts comments, and pulls project status, all directly from a chat. Asana ships an official OAuth-authenticated server at https://mcp.asana.com/v2/mcp, so you connect it once and Claude can answer “what’s overdue in the launch project?” or draft a status update without you opening Asana.

What can the Asana MCP server do?

Capability	What it enables
Universal search	`search_objects` searches across tasks, projects, portfolios, goals, teams, users, tags, and custom fields from one query.
Read tasks	`get_task`, `get_tasks`, and `get_my_tasks` pull individual tasks, filtered lists, or your own assignments.
Advanced task search	`search_tasks` does full-text search with complex filters (due dates, assignees, custom fields). Requires a Premium+ workspace.
Read projects	`get_project` / `get_projects` return project details and metadata.
Portfolios	`get_portfolio`, `get_portfolios`, and `get_items_for_portfolio` expose portfolio-level rollups.
Status overview	`get_status_overview` returns aggregated status for a project or portfolio.
Create work	`create_tasks` and `create_project` add new tasks and projects.
Update & delete	`update_tasks` edits name, assignee, dates, status, and custom fields; `delete_task` removes a task.
Comments & updates	`add_comment` adds context to a task; `create_project_status_update` posts a colored status update.
People & files	`get_user`, `get_me`, `get_users`, `get_teams`, and `get_attachments` cover identity and file access.

In Claude and ChatGPT, creation runs through interactive preview tools (create_task_preview, create_project_preview) so you confirm before anything is written.

Official vs community server

Official Asana V2 server (https://mcp.asana.com/v2/mcp) is the right default. It’s OAuth-authenticated, hosted by Asana, supports Streamable HTTP, and is governed by your workspace’s app-management controls. Note the V1 beta (mcp.asana.com/sse) is deprecated and shuts down 2026-05-11, so target V2.
Community server (roychri/mcp-server-asana) runs locally and authenticates with a personal access token (ASANA_ACCESS_TOKEN). It exposes ~41 tools with extra granularity like subtasks, sections, dependencies, and an optional READ_ONLY_MODE flag. Good for self-hosting or tinkering; you own the token’s security.

How do you connect it to Claude (Cowork / Code / Desktop)?

Claude Cowork / Desktop: open Settings → Connectors → Add custom connector, name it “Asana,” and paste the server URL https://mcp.asana.com/v2/mcp. Save.
Authorize: Claude opens an OAuth prompt. Sign in to Asana and approve access. Tokens issued for MCP only work with the MCP server, which contains the blast radius if one leaks.
Claude Code: the V2 server uses OAuth 2.0 with a registered client ID and secret, so first create an Asana MCP app to get those credentials, then run claude mcp add --transport http --client-id YOUR_CLIENT_ID --client-secret asana https://mcp.asana.com/v2/mcp and authorize when prompted.
Start read-only: ask “list my incomplete tasks due this week” before letting it create or update anything. Confirm the right workspace is connected first.

How we use it: Good for triage and reporting. “Summarize blocked tasks in the Q3 portfolio” or “draft a status update for the launch project” lands well, and the preview-before-write flow keeps the agent honest. Bad for bulk restructuring; once you’re past a couple dozen edits, a script against Asana’s REST API is faster and safer than a chat. One gotcha: search_tasks (advanced filtering) needs a Premium-or-higher Asana plan. On a free workspace it just won’t be available, and the agent may quietly fall back to a weaker search.

Security & permissions

Authenticate with OAuth, not a shared token, and start read-only. The server respects your workspace’s app-management controls, so admins can gate it centrally. MCP tokens are scoped to the MCP server only, so keep it that way rather than reusing a general-purpose API token, and review which members can connect custom connectors.

Wiring Asana into your stack

The Asana MCP server is most useful when it’s one node in a connected workflow: task status feeding a Slack standup, or a Linear-to-Asana handoff your agent stitches together. That’s the part worth designing deliberately: which tools an agent can call, when writes need a human, and how it composes with your other connectors.

If you want help scoping a project-management agent that’s safe to turn loose, Book a discovery call.

Sources: Using Asana’s MCP Server · Compatible MCP Clients · Connecting clients to V2 · roychri/mcp-server-asana