Asana MCP Server: What It Does and How to Connect Asana to AI in 2026
Yes — Asana has an official MCP server. It’s a remote server at mcp.asana.com that lets any MCP-compatible AI tool read and write your tasks, projects, and the rest of the Asana Work Graph. So if you’re searching “Asana MCP,” the connection you want already exists and comes straight from Asana.
The thing worth knowing before you set it up: an MCP server hands your Asana data to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches Asana for you, nothing fires when a task moves to Done, and nothing runs while the chat is closed. Here’s exactly what the Asana MCP does, how to turn it on, where it stops — and what to use when you want Asana work that runs on its own.
What the Asana MCP server does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, Cursor, VS Code, and others — talk to an outside app through a shared interface. Asana maintains one official server, now in its second version:
- V2 server (
mcp.asana.com/v2/mcp, Streamable HTTP transport) — the current, generally available endpoint. It gives an MCP-compatible AI read and write access to tasks, projects, portfolios, and the connections between them across the Asana Work Graph. - V1 beta server (
mcp.asana.com/sse) — the older SSE-based endpoint. It’s deprecated and scheduled to shut down on 05/11/2026, so new setups should point at V2.
With it connected, an AI client can:
- Look up work — “what’s the status of the Q3 launch project and who owns each open task?” answered from live Asana data.
- Query and filter — “which tasks are overdue in the marketing portfolio?” run against your actual workspace, not a guess.
- Create and update — add a task, move it to a new section, assign it, or leave a comment without opening Asana.
- Reason across the Work Graph — summarize a project’s progress, spot stalled tasks, draft a status update from real task history.
It’s genuinely useful for ad-hoc work: ask a question, get an answer grounded in your actual projects, make a change on the spot.
How to set up the Asana MCP server
The V2 server is the quick path — no code, no hosting:
- In your AI client’s connector settings, add a remote MCP server pointing at
mcp.asana.com/v2/mcp. - Make sure your client supports Streamable HTTP transport and OAuth, then authorize it against your Asana account — you’re granting the AI the same scopes your user already has.
- Confirm the tools appear in the client, then start a chat and ask it to read or update a task.
Note that V2 currently exposes a smaller set of tools than V1 offered — Asana has been restoring capability in stages, so check the current tools reference in Asana’s developer docs if something you relied on in V1 seems missing.
Where the Asana MCP stops
None of this is a knock on MCP — it’s just the shape of the protocol. Four limits show up the moment you want more than a conversation:
- It only works inside a chat you start. Close the window and nothing happens. The AI doesn’t watch Asana; it waits for you to ask.
- No triggers. A task moving to Done, a new task landing in a project, an assignee changing — none of these can start anything through MCP. There’s no “when this happens in Asana, do that.”
- It’s one app at a time. The Asana MCP knows Asana. Getting a completed task into Slack, a time-tracking sheet, and an invoice tool means wiring up (and authing) a separate MCP server for each, then hoping your client can juggle them in one turn.
- You own the plumbing and the scopes. OAuth tokens, refresh, and the blast radius of read/write access to your projects are all on you.
So the Asana MCP is a great way to ask Asana things and make one-off edits. It is not a way to make Asana run — to have work happen on a schedule or in reaction to an event, across the other tools a task touches.
Running Asana work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to Asana natively — no MCP server to host, no OAuth plumbing to maintain — and to the ~260 other apps it supports, plus anything with a public API through your own key. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Asana work happens whether or not anyone has a chat window open.
A few things that MCP can’t do but a Carly workflow can:
- When a task moves to Done → post an update to the client’s Slack channel, log the hours in your time-tracking sheet, and check off the matching line in a project tracker — automatically, the moment it happens.
- Every Monday morning → summarize every overdue task across your projects and send the list to each owner.
- When a new task lands in an intake project → enrich it with the right tags, assign it based on workload, and draft a kickoff comment for approval.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (drafting, summarizing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Asana connection and everything downstream.
If you just want to interrogate your projects from a chat, Asana’s official MCP server is the right tool and it’s free to connect. If you want Asana to actually do things — on a trigger, on a schedule, across every app a task flows through — that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does Asana have an official MCP server?
Yes. The V2 server at mcp.asana.com/v2/mcp is Asana’s own, generally available MCP server, using Streamable HTTP transport and OAuth. An older V1 beta server (mcp.asana.com/sse) is deprecated and shutting down on 05/11/2026.
Is the Asana MCP server free? Connecting the MCP server is free; you’re authorizing an AI client against your existing Asana account and scopes. You still need whatever Asana plan your workspace runs on.
Can the Asana MCP trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Asana work across apps, you need a workflow tool like Carly rather than an MCP server.
What AI tools can connect to Asana over MCP? Any MCP-compatible client that supports Streamable HTTP and OAuth — Claude, ChatGPT, Cursor, VS Code, and others — can connect to the Asana MCP server.
Can I connect Asana to AI without coding or hosting a server? Yes. You don’t have to touch MCP at all. Carly connects to Asana for you and lets you build the automation in plain language — describe what you want to happen and it wires up Asana and the other apps involved, with no server to host and no code to write.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
