Asana MCP Server

About

Asana ships an official MCP server, and it is a hosted remote one: the V2 endpoint at https://mcp.asana.com/v2/mcp, documented in Asana's own developer docs. There is nothing to install, but there is something to create — V2 requires OAuth 2.0 against a client ID and secret you register yourself at app.asana.com/0/my-apps, with a redirect URL that matches your client exactly (http://localhost:8080/callback for Claude Code, cursor://anysphere.cursor-mcp/oauth/callback for Cursor, http://localhost:3334/oauth/callback for most others). MCP apps in Asana do not use permission scopes: authorising grants the full tool set, and what it can actually reach is bounded only by what your Asana account can already see. Read tools include search_objects, get_task, get_tasks, get_my_tasks, get_project, get_portfolio, get_status_overview and get_workspace_agents; write tools include create_tasks and update_tasks (up to 50 per call), create_project, delete_task, add_comment and create_project_status_update; Claude and ChatGPT additionally get interactive preview tools that show a confirmation UI before committing. One documented plan limit matters: search_tasks is Premium-only, and non-Premium workspaces must use get_tasks instead. The community alternative, roychri/mcp-server-asana (npm @roychri/mcp-server-asana), runs locally on a personal access token and is the option to pick when you want READ_ONLY_MODE=true, which the official server has no equivalent of.

Installation

npx -y @roychri/mcp-server-asana

Connecting to the Asana V2 MCP server

1. 1.Create an Asana MCP app

   Go to app.asana.com/0/my-apps and create an app. You get a client ID and a client secret. Asana recommends unique credentials per developer rather than a shared pair, and warns against committing them — the secret is a long-lived credential for your whole work graph.

2. 2.Set the redirect URL to match your client exactly

   This is the step that fails. Each client has its own callback and Asana requires an exact match: Claude Code is http://localhost:8080/callback, Cursor is cursor://anysphere.cursor-mcp/oauth/callback, VS Code needs both http://127.0.0.1:33418/ and https://vscode.dev/redirect, and most others — Windsurf, Kiro, Codex — use http://localhost:3334/oauth/callback.

3. 3.Add the server (Claude Code)

   Claude Code supports pre-registered OAuth credentials natively, which is why Asana recommends it over the mcp-remote bridge. Run the command, then paste the client secret at the prompt — it is hidden as you type and stored in your system keychain, not in ~/.claude.json.

   shell

   claude mcp add --transport http \
     --client-id YOUR_CLIENT_ID \
     --client-secret \
     --callback-port 8080 \
     asana https://mcp.asana.com/v2/mcp

4. 4.Authorise in the browser

   The command opens a browser, you sign in to Asana, review the request and allow access. If your workspace blocks the app under Asana app management, you will instead be prompted to send an unblock request to an admin — that is a workspace policy, not a setup error.

5. 5.Prefer the community server if you need read-only

   The official server has no read-only mode. roychri/mcp-server-asana does: a local npm server on a personal access token from app.asana.com/0/my-apps, with READ_ONLY_MODE=true disabling every create, update and delete tool as well as the create-task prompt.

   shell

   claude mcp add asana -e ASANA_ACCESS_TOKEN=<TOKEN> -- npx -y @roychri/mcp-server-asana

What the V2 server exposes

Asana states this list changes over time and to run tools/list for current schemas. Read tools return data; write tools change it; interactive tools render a confirmation UI and exist only in Claude and ChatGPT.

What people use it for

Which one should you use?

Official versus community here is a straight trade between coverage and restraint.

Categories

Works With

Frequently Asked Questions

Related Guides