Skip to content
Call wiki

What can Claude's stock Asana connector do, and when do you need more?

Last updated 2026-08-17 · Confidence: documented — Asana’s developer docs and Claude’s help center; whether Cowork’s directory lists the Asana app is inferred.

Claude’s Asana connector is Asana’s own MCP server, and since its V2 release (tools reference dated June 4, 2026) it covers most daily reads and writes — tasks, custom fields, portfolios, comments, status updates. Tags, sections, attachment uploads, and bulk automation still need a fuller MCP server or the REST API.

The stock connector is Asana’s own server

Section titled “The stock connector is Asana’s own server”

The Asana app in Claude’s directory connects to Asana’s hosted MCP server (mcp.asana.com/v2/mcp), authenticated with your Asana login — so it sees exactly what you can. In Claude it adds interactive previews: draft tasks and project plans render for review before anything is created.

What V2 exposes — more than it used to

Section titled “What V2 exposes — more than it used to”

The tools reference lists reads across tasks (with subtasks, comments, and custom fields), projects, portfolios, users, teams, and attachments, plus writes: create or update up to 50 tasks at once — custom fields and dependencies included — create projects with sections, add comments, post status updates. Full-text task search is gated to Premium Asana plans.

“The stock connector can’t do what clicking around can” was truer of the narrower V1 server, which Asana is retiring in favor of V2.

When you still need more

Section titled “When you still need more”
  • Gaps in the V2 tool list: no tags, no creating or reordering sections in an existing project, no uploading attachments, one workspace per session — and its tokens don’t work against the REST API.
  • Fuller MCP servers: community servers wrap more of the API — one exposes 41 tools, adding sections, tags, subtask restructuring, and a read-only mode, authenticated by a personal access token. Any remote MCP server installs into Claude, Cowork, or the desktop app as a custom connector — see Connector scope for what that grants. A community server can also ship as a desktop extension — a one-file .mcpb bundle that runs the server locally inside Claude Desktop (Settings → Extensions → Advanced settings → Install Extension), asking for the access token at install.
  • The API route: a personal access token gives an agent that can run code — Claude Code, or scripts it writes — the entire REST API, the real “anything you could do clicking around” tier. Write actions still pass through the client’s approval flow — see Permission modes.

Sources

Section titled “Sources”