Asana Official Remote MCP Server

🛡️ Official✓ VerifiedSSEOAuth 2.14 tools·Online305ms·30d uptime: 100%·Last checked 18m ago

Asana's hosted MCP (mcp.asana.com/sse) puts tasks, projects and sections into agent reach — authorized per user with Asana OAuth.

https://mcp.asana.com/sse

Provider: Asana ↗
Categories: 📋 Project Management & Productivity

中文简介

Asana 官方远程 MCP 服务器。通过 SSE 传输与 OAuth，AI 代理可搜索任务、创建工作项并读取项目结构。

SSEhttps://mcp.asana.com/sse

Install in Cursor →

Or add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "asana": {
      "url": "https://mcp.asana.com/sse"
    }
  }
}

🔬 Test Live in Online Inspector 🔐 Audit OAuth 2.1 Config

🧰 Tools exposed by Asana MCP (4)

Tool	Safety	Description	Parameters
search_tasks	🟢 Read	Search Asana tasks by text, assignee or project.	text*: stringassignee: stringproject: string
create_task	🟠 Write	Create a task in an Asana project.	name*: stringproject: stringnotes: stringdueOn: string
get_project_sections	🟢 Read	List the sections/columns of an Asana project.	project*: string
update_task_status	🟠 Write	Update a task's completion state or move it between sections.	task*: stringcompleted: booleansection: string

🔐 OAuth 2.1 & Security

Auth type: OAuth 2.1
Dynamic Client Registration: ✅ Supported
PKCE S256: ✅ Supported
Protected resource metadata: https://mcp.asana.com/.well-known/oauth-protected-resource (expected location)

🔐 Audit OAuth 2.1 Config →

🧩 Recommended Agent Skills

Task management skills ↗

📖 Guide

Asana MCP — Remote MCP Server

Asana's remote MCP gives agents structured access to workspaces, projects, sections and tasks — enough to run 'file this bug' or 'what's on my plate' workflows end to end. It uses the legacy SSE transport and Asana's standard OAuth grant flow.

Endpoint & Transport

Endpoint URL: https://mcp.asana.com/sse
Transport: HTTP+SSE (legacy SSE transport)

Authentication

Asana MCP uses OAuth 2.1 — the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow — PKCE and Dynamic Client Registration, so no manual client setup is needed — and simply open a browser consent screen.

Available Tools (4)

Tool	Safety	Description
`search_tasks`	read	Search Asana tasks by text, assignee or project.
`create_task`	write	Create a task in an Asana project.
`get_project_sections`	read	List the sections/columns of an Asana project.
`update_task_status`	write	Update a task's completion state or move it between sections.

Connect in 30 Seconds

Claude Code — one command:

claude mcp add --transport sse asana https://mcp.asana.com/sse

Cursor — add to ~/.cursor/mcp.json:

{ "mcpServers": { "asana": { "url": "https://mcp.asana.com/sse" } } }

VS Code — add to .vscode/mcp.json:

{ "servers": { "asana": { "type": "sse", "url": "https://mcp.asana.com/sse" } } }

Claude Desktop & stdio clients — bridge with mcp-remote:

{ "mcpServers": { "asana": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.asana.com/sse"] } } }

On first connect your client opens a browser OAuth consent screen — approve it and tools become available immediately.

Troubleshooting

401 Unauthorized on connect — that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact WWW-Authenticate challenge.
Client says "unsupported transport" — this endpoint only speaks the legacy SSE transport. Use a client with SSE support (Claude Code: claude mcp add --transport sse) or bridge it with mcp-remote.
"Session expired" / stale Mcp-Session-Id — just re-send initialize; stateless clients can ignore session headers entirely.
SSE-only endpoint — pick an SSE-capable client or bridge.
Access mirrors the authorizing user's Asana permissions.

🚀 How to Connect

Copy the Asana MCP endpoint URL
The remote endpoint is https://mcp.asana.com/sse.
Add it to your MCP client
Claude Code: claude mcp add --transport sse asana https://mcp.asana.com/sse. Cursor: add "asana": { "url": "https://mcp.asana.com/sse" } under mcpServers in ~/.cursor/mcp.json. Other clients work similarly.
Complete the OAuth consent
On first connection your client opens a Asana consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
Verify with the online inspector
Paste https://mcp.asana.com/sse into remotemcp.net/inspector, run initialize and tools/list, and confirm Asana MCP's 4 tools respond.

❓ FAQ

What is the Asana MCP remote MCP endpoint?

The primary endpoint is https://mcp.asana.com/sse. It is an official first-party server operated by Asana, speaking the HTTP+SSE (legacy SSE transport) transport.

How do I authenticate with Asana MCP?

Asana MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.

I'm getting a 401 Unauthorized from Asana MCP — what's wrong?

A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.

Which MCP clients work with Asana MCP?

Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport sse asana https://mcp.asana.com/sse`), VS Code Copilot, ChatGPT connectors, Windsurf, and Claude Desktop via the `mcp-remote` bridge. Note this server only offers the SSE transport, so the client must support SSE.

What tools does Asana MCP expose?

4 tools are cataloged in this directory — including `search_tasks`, `create_task`, `get_project_sections` and more. Use our online inspector to fetch the live tool list straight from the endpoint.

🔗 Connect Guides

Cursor

Connect Asana MCP →

📛 Embed Status Badge in README

[![Remote MCP Status](https://remotemcp.net/api/badge/status/asana.svg)](https://remotemcp.net/servers/asana)

[![Test in Inspector](https://remotemcp.net/api/badge/inspect/asana.svg)](https://remotemcp.net/inspector?url=https%3A%2F%2Fmcp.asana.com%2Fsse)

Related Servers

Notion MCPNotion Labs

Notion's official hosted MCP server. Agents can search your workspace, read and create pages, and query databases over Streamable HTTP or SSE.

https://mcp.notion.com/mcp

🛡️ Official✓ VerifiedHTTP + SSEOAuth 2.15 toolsOnline26ms

Linear MCPLinear Orbit Inc.

Linear's official remote MCP server. Agents can search, create and update issues and query your team's workflow over Streamable HTTP or SSE.

https://mcp.linear.app/mcp

🛡️ Official✓ VerifiedHTTP + SSEOAuth 2.14 toolsOnline7ms

Atlassian MCPAtlassian

Atlassian's official remote MCP server for Jira and Confluence. Search and create issues and pages over the legacy SSE transport with OAuth 2.1.

https://mcp.atlassian.com/v1/sse

🛡️ Official✓ VerifiedSSEOAuth 2.14 toolsOnline61ms

Intercom MCPIntercom

Intercom's official remote MCP server for customer support data. Agents can search conversations, look up contacts and reply to threads over OAuth.

https://mcp.intercom.com/mcp

🛡️ Official✓ VerifiedStreamable HTTPOAuth 2.13 toolsOnline58ms