asana-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| READ_ONLY_MODE | No | Set to 'true' to disable all write operations | |
| ASANA_ACCESS_TOKEN | Yes | Your Asana access token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| asana_list_workspacesB | List all available workspaces in Asana |
| asana_get_users_in_workspaceC | Get users in a workspace or organization |
| asana_get_users_in_teamB | Get users in a team |
| asana_get_userB | Get a user by their GID |
| asana_get_multiple_usersD | Get multiple users |
| asana_search_projectsA | Search for projects in Asana using name pattern matching |
| asana_search_tasksB | Search tasks in a workspace with advanced filtering options |
| asana_get_taskB | Get detailed information about a specific task |
| asana_create_taskB | Create a new task in a project |
| asana_get_task_storiesB | Get comments and stories for a specific task |
| asana_update_taskC | Update an existing task's details |
| asana_get_projectC | Get detailed information about a specific project |
| asana_get_project_task_countsB | Get the number of tasks in a project |
| asana_get_project_sectionsB | Get sections in a project |
| asana_create_task_storyA | Create a comment or story on a task. Either text or html_text is required. |
| asana_add_task_dependenciesC | Set dependencies for a task |
| asana_add_task_dependentsB | Set dependents for a task (tasks that depend on this task) |
| asana_create_subtaskB | Create a new subtask for an existing task |
| asana_get_multiple_tasks_by_gidA | Get detailed information about multiple tasks by their GIDs (maximum 25 tasks) |
| asana_get_project_statusC | Get a project status update |
| asana_get_project_statusesB | Get all status updates for a project |
| asana_create_project_statusB | Create a new status update for a project |
| asana_delete_project_statusA | Delete a project status update |
| asana_set_parent_for_taskA | Set the parent of a task and position the subtask within the other subtasks of that parent |
| asana_get_tasks_for_tagC | Get tasks for a specific tag |
| asana_get_tags_for_workspaceA | Get tags in a workspace |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| task-summary | Get a summary and status update for a task based on its notes, custom fields and comments |
| task-completeness | Analyze if a task description contains all necessary details for completion |
| create-task | Create a new task with specified details |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 26 tools
Every tool targets a specific resource and action, with clear separation between user, task, project, workspace, and tag operations. Retrieve operations like get, list, and search are clearly differentiated by their parameters and purpose.
All tools follow the asana_verb_noun pattern with mostly consistent snake_case. The only notable deviation is use of 'list' for workspaces while other plural retrievals use 'get' (e.g., get_users_in_workspace), but this is a minor irregularity.
With 26 tools, the set exceeds the 25-tool threshold considered too heavy. The count is inflated by multiple user retrieval variants and status endpoints, making it more difficult for agents to navigate.
The server lacks fundamental CRUD operations: projects cannot be created, updated, or deleted, and tasks have no delete operation. Tag management is similarly limited, leaving significant gaps that will cause agent failures in basic workflows.