Asana MCP Server (official remote)
OfficialAsana's official hosted MCP server (V2) for tasks, projects, and workspace analytics.
Add to your client
Copy the config for your MCP client and paste it into its config file.
Add remote MCP URL https://mcp.asana.com/v2/mcp and complete OAuthPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"asana-mcp-server-official-remote": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.asana.com/v2/mcp"
]
}
}
}Claude Desktop connects to remote servers through the `mcp-remote` proxy (installed on first run via npx). Restart Claude Desktop after saving.
Before you start
- An Asana account with access to the workspace you want to query
- An MCP client that supports Streamable HTTP transport and OAuth (e.g. Claude, ChatGPT, Claude Code, Cursor, VS Code)
- No API token to manage — authentication is handled via OAuth in the browser at connect time
- On Enterprise+/Legacy Enterprise plans, the MCP client must not be blocked in your workspace's app-management settings
About Asana MCP Server (official remote)
The Asana MCP Server is Asana's official, hosted (remote) Model Context Protocol server. It is a managed endpoint at https://mcp.asana.com/v2/mcp that lets compatible AI clients read and act on your Asana data through natural language — creating and updating tasks and projects, searching across your workspace, and generating status overviews and AI-powered summaries.
This is the V2 server. The earlier beta SSE endpoint (https://mcp.asana.com/sse) and the V1 server are being retired (V1 shut down May 11, 2026), so new integrations should target the V2 Streamable HTTP endpoint. V2 trimmed the surface to roughly 15-17 focused tools versus V1's larger set.
Because it is hosted by Asana, there is nothing to install or run locally: you point a Streamable-HTTP + OAuth-capable client at the URL and authorize via your Asana account. Access respects your existing Asana permissions, and Enterprise+/Legacy Enterprise admins can allow or block MCP clients through Asana's app-management controls.
Tools & capabilities (15)
search_objectsSearch across Asana objects (tasks, projects, etc.) by text and filters
search_tasksAdvanced task search by text, date, status, assignee, project, portfolio, tag, and custom fields
get_taskFetch a single task with its fields
get_tasksFetch multiple tasks
create_taskCreate a task in a project, workspace, or as a subtask
update_taskUpdate fields on an existing task
create_projectCreate a new project
get_projectFetch a single project
get_projectsList/fetch multiple projects
get_status_overviewGet an AI status overview/summary for a project
get_portfolioFetch a single portfolio
get_portfoliosList portfolios
get_items_for_portfolioList the items contained in a portfolio
get_userFetch a user's profile
get_workspace_usersList users in a workspace
When to use it
- Use it when you want to create or update Asana tasks and projects from natural-language prompts inside Claude, ChatGPT, or your IDE
- Use it when you need to search across tasks by assignee, due date, status, tag, or custom field without leaving your AI client
- Use it when you want an AI-generated status overview or summary of a project for a standup or stakeholder update
- Use it when you're rolling work up across portfolios and want quick read access to portfolio items and project state
- Use it when you want a zero-install, OAuth-secured Asana integration instead of running a local server
Quick setup
- 1In a Streamable-HTTP + OAuth MCP client, add a remote server pointing to https://mcp.asana.com/v2/mcp
- 2Trigger the connection and complete the OAuth flow in the browser, authorizing access to your Asana account
- 3(Enterprise+) Confirm the client isn't blocked in Asana's app-management settings
- 4Run the tools/list MCP command to see the current tools and parameters
- 5Verify by asking the assistant to search your tasks or fetch a known project
Security notes
Access is delegated through Asana OAuth and constrained to your existing workspace permissions; no API key is stored locally. Use the V2 /v2/mcp endpoint, as the V1 SSE endpoint was retired in May 2026.
Asana MCP Server (official remote) FAQ
What is the server URL and transport?
The current V2 endpoint is https://mcp.asana.com/v2/mcp over Streamable HTTP. The older SSE endpoint (https://mcp.asana.com/sse) and the V1 server are being deprecated, so use V2.
How does authentication work? Do I need an API token?
No manual token is needed. The server uses OAuth — you authorize in the browser with your Asana login, and the integration inherits your existing Asana permissions.
Which AI clients can connect?
Any MCP client that supports Streamable HTTP and OAuth, including Claude, ChatGPT, Claude Code, Codex, Cursor, and VS Code. Asana also ships native app integrations for Claude and ChatGPT.
Can it delete tasks or post comments?
V2 is intentionally scoped. As of its launch it focuses on search, task/project read-write, status overviews, portfolios, and users; comment/story endpoints and some V1 features (subtasks, dependencies, followers) are not exposed.
Can my company restrict which clients use the MCP server?
Yes. Enterprise+ and Legacy Enterprise admins manage MCP client access via Asana's app-management system; other tiers must contact Asana Support to restrict access.
Alternatives to Asana MCP Server (official remote)
Self-hosted MCP server for Jira and Confluence Cloud and Server/Data Center.
Official Notion server to read, search, create, and update pages and databases in your workspace.
Read, search, and edit your Obsidian vault through the Local REST API community plugin.
Compare Asana MCP Server (official remote) with: