Asana Profile — BYO-UI

Asana

Asana belongs in Atlas because its GA V2 MCP exposes workspace-scoped work-graph search plus immediate and previewable task or project mutations under user permissions.

Work & collaborationSystem of coordinationBYO-UI-ready platform

Representative source ↗Product site ↗Suggest a correction

System roleSystem of coordination

Access maturityBYO-UI-ready platform

MCP supportOfficial MCP server

Reference updatedNot stated by publisher

BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Tasks, projects, portfolios, goals, teams, users, tags, custom fields, comments, attachments, sections, followers, project status updates, dependencies, and AI Teammates.

02 · Data you can retrieve

Search workspace objects and task text; inspect task, project, portfolio, attachment, user, team, AI Teammate, and aggregated project-status context across the workspace.

03 · Actions and write paths

Create projects or up to 50 tasks, update or permanently delete tasks, add comments, and post project or portfolio status updates; selected creation flows offer previews.

04 · Authentication and permissions

V2 uses a pre-registered MCP OAuth app and one-hour workspace-scoped tokens. MCP has no granular scopes; every tool remains limited by the authorizing user's Asana permissions.

05 · Monitoring, approval, and recovery

Claude and ChatGPT can render confirmation previews for task and project creation; other clients call immediate write tools, so the client must supply equivalent review before commitment.

06 · Limits and caveats

Dynamic client registration is unsupported, tools evolve through `tools/list`, sessions are workspace-scoped, and the deprecated V1 SSE server is scheduled to shut down July 29, 2026.

First-party MCP tool catalog

27 named MCP tools · Asana-hosted V2 server

The exact V2 tool names published for Asana's hosted workspace-scoped MCP server at mcp.asana.com/v2/mcp. Reviewed Jul 10, 2026. The publisher says the page lists every available V2 tool but directs clients to tools/list for current schemas. OAuth grants the full MCP tool set within the selected workspace and the authenticated user's existing permissions. Interactive confirmation tools currently render only in Claude and ChatGPT; ordinary write tools act immediately.

First-party exact listPublisher-described complete catalogAsana V2 MCP server

Search this catalog

27 shown

Workspace search, tasks, and status7

search_objectsreadget_taskreadget_tasksreadget_my_tasksreadsearch_tasksreadget_status_overviewreadget_attachmentsread

Projects and portfolios5

get_projectreadget_projectsreadget_portfolioreadget_portfoliosreadget_items_for_portfolioread

People, teams, and AI Teammates6

get_userreadget_mereadget_usersreadget_teamsreadget_agentreadget_workspace_agentsread

Immediate writes6

create_taskswritecreate_projectwriteupdate_taskswritedelete_taskconsequential writeadd_commentwritecreate_project_status_updatewrite

Interactive confirmation3

create_task_previewdraftcreate_project_previewdraftsearch_tasks_previewread

Catalog evidence: Asana V2 MCP Tools Reference · Using Asana's MCP Server

First-party access

Documented surfaces

MCP / agent surface ↗Verified first-party provider MCP API ↗Developer access Developer docs ↗SDKs and platform guidance Events / extensions ↗Webhooks, apps, or extensions Product ↗Native platform experience

Agent access

MCP support

Official MCP serverAsana-hosted V2 remote MCPGeneral availability

Support: Official MCP server

Read scope: Search tasks and work-graph objects, inspect detailed project or portfolio context, retrieve attachments and people, and assemble status overviews within the authorized workspace.

Write scope: 8 of 27 reviewed named tools have a write, draft, or mixed action label, including create_tasks, create_project, update_tasks, delete_task, add_comment, and others. Read each catalog boundary before enabling them.

Authentication: A pre-registered confidential MCP app uses Asana OAuth; access tokens last one hour, refresh tokens renew access, and MCP tokens cannot call the REST API.

Approval boundary: Use Asana's preview tools before creating tasks or projects where supported; require explicit client confirmation for bulk updates, comments, status posts, and irreversible task deletion.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4

Action access4

Event access4

Identity4

Governance4

Agent access4

UI extensibility4

Portability4

Observability3

Documentation5

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Asana ships them.

Single-platform patterns

Campaign launch, owner, and dependency room
Marketing launch room
Agent supervision inbox
Cross-functional approval workspace

Use in the brief builder →

Multi-platform compositions

Asana + campaign or CRM system: marketing launch room
Asana + content-production platform + analytics or automation system: cross-system decision workspace

Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

8 recorded sources

MCP / agent-role validationRepresentative source

https://developers.asana.com/docs/integrating-with-asanas-mcp-server ↗

V2 availability, OAuth registration, workspace scoping, token lifetime and separation, permissions, dynamic tools, and V1 retirement

Publisher updated: Not stated by publisher
BYO-UI reviewed: Jul 22, 2026

Asana V2 integration, tokens, permissions, and migration reviewed 2026-07-22

APISource inventory

https://developers.asana.com/reference/rest-api-reference ↗

First-party API reference or API overview recorded for this platform.

Publisher updated: Not stated by publisher
BYO-UI reviewed: Jul 10, 2026