asana-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASANA_ACCESS_TOKEN | Yes | Asana personal access token | |
| ASANA_MCP_WRITE_MODE | No | Write mode: read_only (default), restricted, or full | read_only |
| ASANA_MCP_DEFAULT_WORKSPACE | No | Default workspace GID for list/search tools | |
| ASANA_MCP_WRITABLE_CUSTOM_FIELDS | No | Comma-separated custom field GIDs writable in restricted mode |
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 |
|---|---|
| asana_get_taskA | Get an Asana task by GID, including any requested opt_fields (name, notes, assignee, custom_fields, memberships, etc). |
| asana_list_tasksA | List tasks filtered by workspace+assignee, project, or section. Use completed_since="now" for incomplete tasks only. |
| asana_list_task_commentsB | List the stories (comments and system events) on a task. Filter client-side on type="comment" for human comments. |
| asana_list_task_attachmentsB | List attachments on a task (name, host, download_url). |
| asana_get_userA | Get an Asana user by GID (or "me") — name, email, etc. |
| asana_list_project_sectionsC | List the sections of a project. |
| asana_list_tasks_in_sectionC | List the tasks in a section. |
| asana_typeahead_searchB | Fast typeahead search in a workspace for tasks, projects, users, portfolios, or tags. |
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 or action: get_task, get_user, list_project_sections, list_task_attachments, list_task_comments, list_tasks, list_tasks_in_section, and typeahead_search all have clearly different purposes with minimal overlap.
Most tools follow a consistent 'verb_noun' pattern (e.g., get_task, list_tasks), but 'typeahead_search' breaks the verb-first convention, using a noun modifier instead. The inconsistency is minor.
With 8 tools, the server is reasonably scoped for a read-only Asana client. It covers essential retrieval operations without being too heavy, though it lacks write capabilities.
The tool surface is severely limited to read operations only, missing common CRUD (create, update, delete) and other important resources like projects, workspaces, and portfolios. This makes it incomplete for full Asana workflows.