Ranked roundup · Asana
Best MCP Server for Asana
If you want an MCP server for Asana, the good news is that Asana ships one itself, and it is the right default for most people. The official server is remote, hosted at mcp.asana.com/v2/mcp, authenticates with OAuth, and is generally available — no beta caveat anymore, though the original v1 beta endpoint has been retired. Around it sits a small but real ecosystem: the community fills the self-hosted niche with open-source servers you run locally against a personal access token (roychri/mcp-server-asana is the clear leader at 147 GitHub stars), and managed platforms like Composio and Zapier wrap the Asana API for teams that want someone else to handle hosting and credentials. This is a thinner field than some apps get — one official server, one dominant community project, and a tail of tiny forks. We ranked what's here on verifiable criteria: official vendor support, maintenance recency, auth model, and documented capability coverage. Nobody paid to be on this page.
Facts checked September 1, 2026 · ranked on verifiable criteria · placement is never for sale
Founder, Automation Squad ·
The ranking
- Official · Asana
Almost everyone — it is the lowest-friction, best-supported way to connect an AI client to Asana, with no server to run and no token to babysit.
Task creation and updates, project and workspace search, and Work Graph access via natural language. Asana points clients at tools/list for the current tool set rather than publishing a fixed count, and ships pre-built app integrations for Claude and ChatGPT.
Remote (vendor-hosted) at https://mcp.asana.com/v2/mcp — nothing to install; requires a client that supports OAuth and Streamable HTTP transport · OAuth 2.0; you authorize with your own Asana account, and access is limited to workspaces, projects, and tasks that account can already see. Access tokens expire after one hour (clients refresh automatically).
- The v1 beta endpoint (mcp.asana.com/sse) is deprecated; Asana scheduled its shutdown for August 5, 2026, so anything still pointing at /sse is dead — use the v2 URL.
- All actions run as the authorizing user and appear under their name — there is no service-account mode.
- MCP tokens work only against the MCP server, not the standard Asana REST API.
- Admin allow/block controls for MCP clients are limited to Enterprise+ and Legacy Enterprise plans; other tiers must contact support to restrict access.
- Community
Self-hosters, clients that can't do remote OAuth, and anyone who wants a read-only guarantee — the READ_ONLY_MODE switch is something the official server doesn't offer.
Broad read/write coverage: workspace listing, regex project search, advanced task search (assignee, tags, blocked/blocking, custom fields), task create/update, subtasks, comments and stories, milestones.
Self-hosted stdio server (npm package @roychri/mcp-server-asana); runs locally alongside your MCP client · Asana personal access token via the ASANA_ACCESS_TOKEN environment variable. An optional READ_ONLY_MODE flag disables every write tool. · MIT · 147★
- Community project, not affiliated with or supported by Asana.
- A personal access token carries the full permissions of your Asana account with no scope narrowing — treat it like a password.
- You run and update the server yourself; last push was May 2026, so check activity before depending on it.
- Community
Developers building agents that need Asana plus other apps behind one managed endpoint, especially with frameworks Composio already supports.
Composio documents 153 Asana tools and 6 triggers, covering subtasks, custom fields, portfolios, and goal linking — the broadest published tool count of any option here. Integrates with Claude Code, Cursor, CrewAI, OpenAI Agents SDK, and other frameworks.
Managed — Composio hosts the server and the Asana connection; you point your client or agent framework at it · OAuth handled by Composio's managed auth layer; credentials live on Composio's platform, not in your config files.
- Not an Asana product — a third party sits between your agent and your Asana data.
- Platform pricing applies beyond the free tier; the 153-tool figure is Composio's own published count, not independently tested by us.
- Community
Non-developers and teams already on Zapier who want a no-code path with deliberately narrow permissions rather than the full API surface.
Asana actions (create tasks, update progress, search) drawn from Zapier's integration catalog, alongside 9,000+ other apps on the same endpoint. Action-level scoping is the standout: you expose only what you choose.
Managed — Zapier generates a personal MCP endpoint; no code or hosting on your side · Your existing Zapier account connects to Asana; you pick and scope the specific actions the AI is allowed to call.
- Every tool call routes through Zapier's infrastructure.
- Usage is metered against Zapier's plan limits, so heavy agent traffic can get expensive.
- Capability depth depends on Zapier's Asana integration, which is shallower than the raw API.
- Community
Power users who hit the limits of the base community server and specifically need batch task operations.
Extends roychri/mcp-server-asana with batch operations, direct section assignment, and selective tool activation — useful for trimming the tool list an LLM has to reason over.
Self-hosted stdio server (npm package @n0zer0d4y/asana-project-ops) · Asana personal access token, same model as the roychri server it builds on. · MIT · 3★
- Very small adoption — 3 GitHub stars — so you are close to being the maintainer.
- A derivative of the roychri server; if that project stalls, this likely does too.
- Same unscoped personal-access-token risk as any PAT-based server.
Asana MCP servers compared
| Server | Maintained by | Runs | Auth | License |
|---|---|---|---|---|
| Asana MCP Server (official) | Asana | Remote (vendor-hosted) at https://mcp.asana.com/v2/mcp — nothing to install; requires a client that supports OAuth and Streamable HTTP transport | OAuth 2.0; you authorize with your own Asana account, and access is limited to workspaces, projects, and tasks that account can already see. Access tokens expire after one hour (clients refresh automatically). | — |
| roychri/mcp-server-asana | Community | Self-hosted stdio server (npm package @roychri/mcp-server-asana); runs locally alongside your MCP client | Asana personal access token via the ASANA_ACCESS_TOKEN environment variable. An optional READ_ONLY_MODE flag disables every write tool. | MIT |
| Composio Asana MCP | Community | Managed — Composio hosts the server and the Asana connection; you point your client or agent framework at it | OAuth handled by Composio's managed auth layer; credentials live on Composio's platform, not in your config files. | — |
| Zapier MCP (Asana) | Community | Managed — Zapier generates a personal MCP endpoint; no code or hosting on your side | Your existing Zapier account connects to Asana; you pick and scope the specific actions the AI is allowed to call. | — |
| n0zer0d4y/asana-project-ops | Community | Self-hosted stdio server (npm package @n0zer0d4y/asana-project-ops) | Asana personal access token, same model as the roychri server it builds on. | MIT |
How to choose
Pick the official Asana server if you can: OAuth, no hosting, vendor-maintained, and actions are scoped to what your Asana account can already see. Pick roychri/mcp-server-asana if you need to self-host, want a read-only mode, or your client can't do OAuth over Streamable HTTP — you trade that for managing a personal access token yourself. Pick Composio if you're wiring Asana into an agent framework alongside other tools and want managed auth. Pick Zapier MCP if you already pay for Zapier and want scoped, hand-picked actions rather than the full API surface.
How this ranking works
Every server here is real and was checked against its repository or vendor documentation on the date above — stars and licenses come from the GitHub API, not from memory. Order reflects verifiable criteria only: official support, maintenance recency, adoption, auth model, and documented capability coverage. We do not run paid placements, and we list every caveat we find, including the unflattering ones.
Common questions
- Does Asana have an official MCP server?
- Yes. Asana hosts a remote MCP server at https://mcp.asana.com/v2/mcp, and it is generally available, not beta. The original v1 beta endpoint (mcp.asana.com/sse) is deprecated, with shutdown scheduled by Asana for August 5, 2026.
- How does setup and authentication actually work?
- The official server uses OAuth: add the endpoint to a client that supports OAuth and Streamable HTTP, sign in with your Asana account in the browser, and access mirrors whatever that account can already see. Community servers skip OAuth entirely — you generate an Asana personal access token and pass it as an environment variable, which is simpler but grants your full account permissions with no scoping.
- Does the official Asana MCP server cost extra?
- Asana doesn't charge separately for the MCP server; access follows your existing Asana seat and permissions. The one plan-gated piece is admin control — allowing or blocking specific MCP clients requires Enterprise+ or Legacy Enterprise.
- Why would anyone use a community server when an official one exists?
- Three real reasons: your MCP client can't handle remote OAuth servers, you want to self-host so no third party is in the path, or you want roychri's READ_ONLY_MODE, which hard-disables all write tools — a guarantee the official server doesn't offer.
MCP servers we build
Automation Squad publishes its own open-source MCP servers and agent skills, documented with the same rules this ranking uses.