Asana is where project tasks live — but updating them means opening a browser, finding the right project, clicking to the right task, and making the change. The Asana MCP server puts your entire Asana workspace inside Claude. Ask it to create a task, check what's due today, or update a project status, and it handles the Asana API call for you.
What is Asana?
Asana is a project and task management platform used by marketing, product, and operations teams to coordinate work across individuals and departments. It organizes work into a hierarchy of projects, tasks, and subtasks, with support for due dates, assignees, custom fields, and status updates. Teams use Asana to track everything from content calendars and product launches to engineering sprints and client deliverables. Whether you are a solo user on the free tier or a large enterprise on Business, Asana's API exposes the same core data model — which is exactly what the MCP server hooks into.
What the Asana MCP Server Does
The Asana MCP server acts as a bridge between Claude and the Asana REST API. Once installed, Claude gains access to a set of tools it can invoke during your conversations. The core tools include:
- List tasks in a project — retrieve all tasks within a specific project, optionally filtered by assignee or completion status.
- Create new tasks — add tasks to any project with a name, description, assignee, and due date specified in natural language.
- Mark tasks complete — close out finished work without opening the Asana interface.
- Search across workspace — find tasks by keyword, tag, or assignee across all your projects at once.
- Get project status — retrieve the overall health and progress of a project including completion percentages.
- Update task details — change assignees, due dates, descriptions, or custom field values on existing tasks.
Under the hood, Claude decides which tool to call based on your natural-language request, passes the right parameters, and formats the response in a readable way. You never write API calls yourself. For a deeper look at how Claude decides which tools to invoke, see our MCP security and trust levels guide.
Prerequisites
Before installing the Asana MCP server, make sure you have the following:
- Asana account — any plan works, including the free tier.
- Asana personal access token — go to app.asana.com/0/my-apps, click "Create new token", give it a name, and copy the generated token. Treat this like a password.
- Workspace GID — navigate to any project in Asana and look at the URL; the long numeric string after
/0/contains your workspace identifier. You can also retrieve it via the Asana API. - Node.js 18 or higher — check with
node --versionin your terminal. Download from nodejs.org if needed. - Claude Desktop — the MCP server connects via Claude Desktop's MCP integration.
How to Install the Asana MCP Server
- Generate your personal access token. Log into Asana and navigate to app.asana.com/0/my-apps. Click "Create new token", give it a descriptive name like "Claude MCP", and copy the token immediately — you cannot view it again after closing the dialog.
-
Get your workspace GID. Open any project in Asana and look at the browser URL. Your workspace GID is the long numeric string that identifies your workspace. Alternatively, call the Asana API at
https://app.asana.com/api/1.0/workspaceswith your token to list all workspaces and their GIDs. -
Open your Claude Desktop config file. This file is called
claude_desktop_config.json. On macOS it lives at~/Library/Application Support/Claude/claude_desktop_config.json; on Windows it is at%APPDATA%\Claude\claude_desktop_config.json. See our full claude_desktop_config.json guide for details. - Add the Asana server block using the config JSON below, replace both placeholder values with your real token and workspace GID, then save the file and restart Claude Desktop. The Asana server will appear in Claude's tool list within a few seconds of launch.
The Config JSON
Add this block to your claude_desktop_config.json. The npx command pulls the latest server version automatically — no manual installation required.
{
"mcpServers": {
"asana": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-asana"],
"env": {
"ASANA_ACCESS_TOKEN": "your_personal_access_token",
"ASANA_WORKSPACE_GID": "your_workspace_gid"
}
}
}
}
claude_desktop_config.json entry for the Asana MCP server. Replace both placeholder values with your actual Asana personal access token and workspace GID.If you are unsure about keeping API credentials in your config file, read our MCP security and trust levels guide. The token lives only in your local config file and is passed to the local server process — it does not travel to Anthropic's servers.
Real Use Cases
Once the server is connected, these are the kinds of requests Claude can handle immediately:
- "What tasks are due this week in the Q1 Marketing project?" Claude queries the project for all tasks with due dates falling in the current week, formats them as a list with assignee names and exact dates, and flags anything that is already overdue.
- "Create a task 'Update website copy' in the Website project, due Friday, assigned to Sarah." Claude creates the task via the API, sets the due date to the nearest upcoming Friday, and assigns it to the matching team member — no form-filling required.
- "Mark the homepage redesign task complete." Claude searches for the task by name within the workspace, confirms it found the right one, and marks it complete via the API.
- "Show me everything assigned to me." Claude retrieves all open tasks assigned to the authenticated user across every project in the workspace and groups them by project for easy scanning.
- "What's the status of the Product Launch project?" Claude pulls the project's status update, completion percentage, and any open blockers or at-risk tasks, giving you a quick health check without opening Asana.
Pros
- Great for project managers — cross-project task queries and status checks that would take minutes of clicking take seconds with a single sentence.
- Works with Asana free tier — you do not need a paid plan to use the MCP server; the core task and project API is available on all tiers.
- Combines well with Slack MCP for notifications — pair the Asana MCP server with a Slack MCP server to create tasks and immediately notify your team in one conversation.
- Natural language task creation saves time — describing a task conversationally is faster than filling out Asana's task form, especially for bulk creation.
Cons / Limitations
- Workspace GID required — finding your workspace GID is a slightly awkward extra step during setup compared to servers that only need a single API key.
- Complex project hierarchies need careful querying — deeply nested sections, custom fields, and portfolio structures may require more specific prompts to get the right data.
- Asana API has rate limits — the Asana API enforces rate limits per token. Heavy bulk operations (listing hundreds of tasks across many projects) may hit these limits; space out large queries.
Frequently Asked Questions
Yes. The Asana MCP server works with both personal and team workspaces. You provide your workspace GID in the config, and Claude can then access all projects and tasks within that workspace that your personal access token has permission to read or write. If you have multiple workspaces, you will need to choose one per server instance.
Subtask creation depends on the version of the MCP server package you are running. The core operations — creating tasks, updating task details, and marking tasks complete — are broadly supported. For subtasks, check the package README for the current list of supported write operations, as this feature may require specifying a parent task GID.
The primary package (@modelcontextprotocol/server-asana) is maintained by the MCP community. Asana has not released an official first-party MCP server as of early 2026, though the Asana API is well-documented and the community server covers the most common use cases. Always verify the package source before installing.
Goals and portfolios are higher-tier Asana features available on Business and Enterprise plans. Support for these endpoints in the MCP server varies by package version. The core task and project operations work across all Asana plan tiers including the free tier. Check the package changelog for the latest supported endpoints if you need goals or portfolio access.