asana-local-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASANA_ACCESS_TOKEN | Yes | Asana personal access token. Must have attachments:read and data-access scopes for your projects. | |
| ASANA_INLINE_IMAGE_MAX_BYTES | No | Optional cap for inline image bytes. Default is 2097152, maximum 5242880. | 2097152 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List up to |
| search_tasksA | Search tasks across up to 25 selected projects. |
| get_taskA | Fetch one task's detail fields and normalized attachments. |
| list_task_commentsB | List up to |
| search_commentsC | Search comments across selected projects. |
| get_attachmentB | Fetch one attachment, optionally rendering its image inline. |
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 6 tools
Each tool targets a clearly distinct resource and action: projects, tasks, task comments, project-scoped comments, and attachments. The two comment tools are separated by scope (single task vs. selected projects), so an agent should be able to select the correct one.
All tool names use lowercase snake_case with an action-plus-noun pattern like list_projects, search_tasks, get_task, and get_attachment. The naming is consistent and predictable.
Six tools is a well-scoped size for a focused read/search integration. Each tool has a distinct purpose and none feel redundant or extraneous.
For the apparent read-only/local-search purpose, the major Asana resources are covered: projects, tasks, comments, and attachments, with reasonable retrieval chains. The main limitation is the lack of any create/update/delete tools, which would be a gap if full Asana lifecycle management were expected.