asana-admin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASANA_TOKEN | No | Asana Personal Access Token. If not provided, the server falls back to ~/.asana_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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| asana_whoamiA | The authenticated user and their workspaces. Call this first — almost every create call needs a workspace_gid. |
| asana_findA | Typeahead search that turns a name you can see in the Asana UI into the gid every other tool needs. |
| asana_list_custom_fieldsA | Custom fields in a workspace, or the ones attached to a project/portfolio. Returns enum_options with their gids — the input for every dropdown tool. |
| portfolio_createC | Create a portfolio in a workspace. |
| portfolio_updateA | Change a portfolio's name, color, or visibility. Only the fields you pass are touched. |
| portfolio_list_itemsC | The projects/portfolios inside a portfolio, in their current display order. |
| portfolio_add_itemA | Add a project (or sub-portfolio) to a portfolio, optionally at a chosen position. Adding an item that is already present moves it to that position. |
| portfolio_remove_itemA | Remove a project from a portfolio. This also drops any portfolio-level custom field values set on that project. |
| custom_field_createB | Create a workspace custom field. For a dropdown use type 'enum' (single-select) or 'multi_enum' (multi-select) and pass enum_options. |
| custom_field_updateA | Change a custom field's name or description. Enum values are edited with the enum_option_* tools. |
| enum_option_createA | Add a value to an enum / multi_enum custom field. Appended at the end unless you give a position. |
| enum_option_updateA | Rename, recolor, or disable a dropdown value. Asana has no delete — set enabled:false to retire a value; tasks already holding it keep it. |
| enum_option_reorderA | Move an existing dropdown value to a new position within its custom field. |
| custom_field_attachB | Make an existing custom field available on a project or a portfolio. |
| member_addA | Give a person or team access to a project or portfolio. NOTE Asana's own limits: a project can only be admin / editor / commenter — there is no view-only level for projects, so 'commenter' is the least access possible. A portfolio can be admin / editor / viewer. |
| member_listB | Who currently has access, and at what level. |
| project_createB | Create a project in a workspace (team_gid is required in an organization). |
| project_updateC | Change a project's name, notes, color, default view, or archived state. |
| project_duplicateA | Copy a project. Tasks, project views (List/Board/Dashboard tabs) and rules are always carried over — this is the only way to give a new project a preconfigured Dashboard, since Asana exposes no dashboard/chart API. Returns a job; duplication finishes asynchronously. |
| project_list_sectionsB | Sections of a project in display order — the gids needed by section_reorder. |
| section_createB | Add a section to a project, optionally at a chosen position. |
| section_updateA | Rename an existing section. |
| section_reorderC | Move an existing section to a new position within its project. |
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 23 tools
Each tool targets a distinct resource and action: user info, members, projects, portfolios, custom fields, sections, and search. There is no overlap in purpose, and descriptions clearly differentiate them.
Most tools follow a consistent 'resource_verb' pattern (e.g., portfolio_create, custom_field_attach, section_reorder), but a few use a generic 'asana_' prefix (asana_whoami, asana_find) and 'project_list_sections' mixes resource prefixes, creating minor inconsistency.
With 23 tools, the server is slightly on the higher side but still well-scoped for Asana administration. Each tool serves a clear purpose, and the count is justified by the breadth of admin operations covered.
The tool set covers core admin operations like project/portfolio/folder/section CRUD, custom field management, and member access. However, it lacks delete operations for projects, portfolios, and members, and is missing a general listing tool for projects/portfolios, which are notable gaps for an admin surface.