@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
Most tools target distinct resources (sections, comments, projects) or distinct actions (list vs. get vs. create vs. update vs. search). The main potential confusion is between list_tasks and search_tasks, but their descriptions clarify the scope (project-scoped vs. workspace-wide search).
All tool names follow a consistent verb_noun pattern in snake_case: list_sections, add_comment, list_tasks, get_task, create_task, update_task, search_tasks. The sole exception is 'add_comment' rather than 'create_comment', but it still adheres to the same grammatical style.
Eight tools is well-scoped for an Asana integration, covering the essential operations on tasks, projects, sections, and comments without redundancy. This is within the typical 3-15 range and each tool earns its place.
The tool surface covers the core task lifecycle (create, get, update, list, search) plus project listing, section listing, and comment creation. Missing operations like task deletion or project creation are notable gaps, but agents can work around them for most workflows.