@duytnb79/asana-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASANA_TIMEOUT_MS | No | Request timeout in milliseconds; defaults to 10000. | 10000 |
| ASANA_ACCESS_TOKEN | Yes | Your Asana personal access token. Required. | |
| ASANA_MAX_PAGE_SIZE | No | Maximum page size exposed by list/search tools; defaults to 100 and must be between 1 and 100. | 100 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List Asana projects in a workspace with offset pagination. |
| list_sectionsA | List sections in an Asana project with offset pagination. |
| add_commentB | Add a plain-text comment to an Asana task. This operation writes to Asana. |
| list_tasksA | List tasks in an Asana project in project priority order. |
| get_taskB | Get details for one Asana task. |
| create_taskC | Create an Asana task. This operation writes to Asana. |
| update_taskC | Update fields on an Asana task. This operation writes to Asana. |
| search_tasksB | Search tasks in an Asana workspace. Search indexing is eventually consistent and may lag writes by 10-60 seconds. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: single task retrieval, task listing, project listing, section listing, commenting, creating, updating, and searching. Even list_tasks and search_tasks are clearly differentiated by scope (project vs. workspace).
All tool names follow a consistent verb_noun snake_case pattern (e.g., get_task, list_projects, add_comment, create_task). No mixed conventions or vague verbs.
With 8 tools, the set is well-scoped for an Asana integration, covering tasks, projects, sections, and comments without unnecessary bloat. Each tool serves a clear purpose.
The core task lifecycle is covered with get, list, create, update, and search, but missing a delete_task operation leaves a notable gap. Sections and projects are only listable, but that may be acceptable for the server's scope.