Asana MCP Server Setup for Cursor IDE (2026)

How do you set up the Asana MCP server in Cursor? Add an entry to ~/.cursor/mcp.json pointing at Asana's hosted MCP endpoint (typically bridged through the mcp-remote package, the same pattern other SaaS-hosted MCP servers on this site use), restart Cursor, and approve the connection through a browser-based OAuth flow. There's no API token to generate or paste — Asana's MCP server runs remotely and authenticates the same way logging into Asana in a browser does.

If you've set up a token-based integration before (a Linear or ClickUp API key, for instance), this will feel different. There's no field in the config to paste a secret into. The first connection opens a browser window, you log into Asana and approve the grant, and the resulting session is cached locally rather than stored as a static key in your config file.

What You Can Do With Asana MCP in Cursor

Once connected, Cursor can typically:

Whether create/update operations are available — and how broadly scoped they are — depends on the OAuth grant you approve and the specific package bridging the connection. Some setups scope access to specific workspaces or projects during the OAuth flow; others grant broader workspace access by default. Check what you're approving in the browser window, not just what the tool list shows afterward.

Prerequisites

Step 1: Add the Remote Server to Cursor's Config

Open ~/.cursor/mcp.json and add an asana entry using the remote-bridge pattern:

{
  "mcpServers": {
    "asana": {
      "command": "npx",
      "args": ["-y", "mcp-remote", ""]
    }
  }
}

Swap for the current endpoint listed in Asana's own MCP/developer documentation. This site won't print a specific URL here with confidence — hosted MCP endpoints in this SaaS-remote category have shifted domains and paths as vendors move features out of beta, and a stale URL copied from an outdated guide is a more common failure than anything covered in Troubleshooting below. Check Asana's developer docs or Cursor's MCP directory listing for Asana immediately before finalizing this block.

Step 2: Authenticate via Browser

1. Restart Cursor completely after saving the config
2. Open the AI chat and ask something that requires Asana access, e.g. "List my Asana tasks due this week"
3. A browser window opens asking you to log into Asana (if you aren't already) and authorize the connection
4. Review what the grant covers — workspace-wide or project-scoped — before approving
5. Approve it — the session is cached locally, so you won't see this again unless it expires or you revoke access from Asana's app settings

If the browser window doesn't open automatically, check Cursor's MCP output panel for a URL to open manually — the same failure mode covered in the Cloudflare MCP guide, which uses an identical bridge pattern.

Step 3: Verify the Connection

List my Asana tasks that are due this week

A response naming real task titles and projects confirms it's working. An auth error usually means the OAuth session didn't save — remove and re-add the server config to force a fresh login.

Practical Workflows

Morning task triage

List everything assigned to me in Asana that's overdue or due today, grouped by project

Filing a task without breaking flow

Create an Asana task in the "Website Redesign" project titled "Fix broken checkout link on mobile" with a due date of Friday, and assign it to me

Getting context before starting work

Find the Asana task about the Q3 pricing page update, and summarize the comment thread so I know what's already been decided

Status check before a stand-up

List all tasks in the "Sprint 14" project by status, and flag anything that's been sitting In Progress for more than a week

Asana vs. the Other Project-Management MCP Servers on This Site

This site also covers Linear and ClickUp, and it's a fair question which one to actually wire up if your team could plausibly use any of them. They're not interchangeable in practice, even though all three can "list my tasks."

Linear is built for engineering teams specifically — cycles, issue states, and its API are opinionated toward software work, and its MCP setup uses a straightforward API key rather than OAuth. ClickUp leans toward heavy customization across many team types, which shows up as more configuration surface (spaces, folders, custom fields) that an AI has to navigate correctly. Asana sits closer to cross-functional, non-engineering work — marketing calendars, ops checklists, launch plans — and its MCP server being OAuth-based rather than token-based reflects that it's more commonly deployed org-wide, where individual API tokens per person become harder to manage than a per-user OAuth grant.

If your team's actual project tracking lives in Asana because non-engineers use it too, don't try to force a Linear-shaped workflow onto it — the value here is in tasks, projects, and comments the way Asana already models them, not in bolting sprint terminology onto a tool that doesn't use it.

Troubleshooting

Browser auth window never appears
Check Cursor's MCP output panel (View → Output → MCP) for a URL and open it manually. Corporate SSO configurations on the Asana workspace side sometimes interrupt the automatic redirect.

"Unauthorized" after previously working fine
OAuth sessions expire or get revoked. Remove the server entry, save, re-add it, and restart Cursor to trigger a fresh login.

Connected but task lists come back empty
You're likely authenticated against the wrong Asana workspace — if you belong to more than one (a personal workspace plus a company one, for example), the OAuth flow authorizes whichever was active in your browser at the time. Check which workspace you're in inside Asana's own UI and reconnect if needed.

Created tasks land in the wrong project
Be explicit about the project name in your prompt rather than relying on a "default" — unlike a single-workspace tool, Asana's project hierarchy means an ambiguous prompt can resolve to a same-named project in a different team.

mcp-remote hangs on startup
Usually a stale cached token causing a redirect loop. Clear the bridge's local token cache (check its README for the current path, since it has changed between versions) and reconnect.

Frequently Asked Questions

Q: Do I need an Asana API token, or is this purely OAuth-based?
A: Purely OAuth-based for the hosted MCP server covered here. There's no static API token to generate or paste into mcp.json — the browser-based grant handles authentication.

Q: Does this work with a free Asana plan?
A: Basic task and project access generally works on free plans, but some advanced fields (custom fields, portfolios) are gated behind paid tiers regardless of how you're accessing them — MCP doesn't unlock anything the Asana web UI wouldn't already show your account.

Q: Can it complete or update tasks, or only read them?
A: Depends on the OAuth grant you approve and the specific tools the server exposes. Read access (listing, searching, pulling task detail) is the reliable baseline; write access (creating, completing, reassigning tasks) is common but worth confirming in the tool list after connecting rather than assuming.

Q: I'm in multiple Asana workspaces — can I connect to more than one?
A: You can add multiple entries in mcp.json under different keys (e.g., asana-personal, asana-work), each going through its own OAuth flow. Which workspace a given session authorizes depends on which one was active in your browser during that specific approval.

Q: How does this compare to just using Asana's web app or mobile notifications?
A: It's not a replacement for notifications — it's for pulling task context into a coding or planning session without switching tabs, and for filing tasks the moment you notice something instead of remembering to do it later in a separate app.

Related Guides

---