asana-admin-mcp
It is an Asana administration MCP server for structuring workspaces — managing portfolios, custom fields/dropdowns, projects/sections, and access — rather than task-level or dashboard work.
Discovery:
asana_whoamireturns the user and workspaces;asana_findconverts names to gids;asana_list_custom_fieldslists custom fields with enum options.Portfolios: create, rename/update color & visibility, list items in display order, add/remove projects, and position items by inserting before/after.
Custom fields & dropdowns: create fields (enum, multi_enum, text, number, date, people), rename/update them, add/reorder/enable-disable dropdown values, and attach fields to projects or portfolios.
Projects & sections: create and update projects (name, notes, color, default view, archived), duplicate projects (the only way to carry a Dashboard to a new project), list/create/reorder/rename sections.
Access: add users or teams to projects/portfolios with access level (admin/editor/commenter/viewer) and list current members.
Provides tools for managing Asana structure, including portfolios, custom fields and enum options, projects, and sections.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@asana-admin-mcp Duplicate project 'Q3 Marketing' and name the copy 'Q4 Marketing'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
asana-admin-mcp
MCP server for structuring Asana — portfolio, custom field / dropdown, project, section Fills the gaps that the standard Asana connector can't do (that one focuses on task/read)
⚠️ Dashboard isn't possible — and it's not a limitation of this MCP
Asana does not expose any public API for Dashboard / chart / widget / project view tab at all (I went through all 175 endpoints in the official OpenAPI spec — not a single one)
The only way to automate this is project_duplicate — the spec states that when duplicating a project,
Project Views (List / Board / Dashboard tabs) are always copied along and cannot be disabled
→ Set up the Dashboard in one "template project", then duplicate it every time you need a new project
🟡 Not yet verified: the spec says "Project Views" are copied, but it doesn't clearly say whether the charts configured in the Dashboard are also copied or only the empty tab — it can't be checked via API (no endpoint to read charts), you have to check visually The 2026-08-17 smoke test duplicated a project without charts, so it still doesn't answer this question
Note: Project Template does not carry the Dashboard with it (this is still a pending feature request in the Asana forum) You must use duplicate, not template
Related MCP server: asana-mcp
Installation
1. Get an Asana token first (everyone needs their own)
Follow GET-TOKEN.md → save it to ~/.asana_token
printf '%s' 'วาง_token_ตรงนี้' > ~/.asana_token && chmod 600 ~/.asana_tokenThe token is tied to individual permissions — do not use someone else's — the log in Asana will show the token owner's name
2. Install the plugin (recommended)
In Claude Code, type 2 lines:
/plugin marketplace add plakorp/asana-admin-mcp
/plugin install asana-admin@asana-admin-mcpClaude Code will clone the repo + run npm ci for you, then register the MCP for you — no need to touch ~/.claude.json
To update later, use /plugin update
You need Node 20+ on your machine (check with node -v)
Method 2 — manual installation (if you don't want to use the plugin)
Clone the repo, then double-click ติดตั้ง-asana-admin-mcp.command
The script will ask for your token, run npm install, and write ~/.claude.json for you (it backs up every time)
Don't use both methods at the same time — you'll get two duplicate MCPs named
asana-admin
The token is read from the env ASANA_TOKEN first; if it's not set, it falls back to ~/.asana_token
→ The token is never in the repo and doesn't need to be in ~/.claude.json
Tools (21)
Every tool takes a gid, not a name — use asana_find to convert a name → gid first
Discovery
Tool | What it does |
| Yourself + all workspaces (start here, because almost every create requires |
| typeahead to find gid from name — project / portfolio / custom_field / task / team / user / tag / goal |
| custom fields in the workspace or attached to a project/portfolio — returns |
Portfolio
Tool | What it does |
| create a portfolio |
| rename / change color / public |
| view projects in the portfolio in the order actually displayed |
| add a project to the portfolio + specify the position ( |
| remove a project (must pass |
Custom field / dropdown
Tool | What it does |
| create a field — |
| rename / edit description |
| add a value to the dropdown + specify the position |
| rename / change color / |
| reorder the dropdown values |
| attach a field to a project or portfolio ( |
Asana cannot delete dropdown values — you can only set
enabled:false; tasks that had selected that value will keep the old value
Project / Section
Tool | What it does |
| create a project (requires |
| rename / notes / color / |
| duplicate a project including the Dashboard — the only solution for the dashboard issue (returns a job, runs async) |
| sections in order + gid |
| add a section + specify the position |
| rename a section |
| reorder sections |
There is intentionally no tool for deleting project / portfolio / custom field — these can't be recovered once deleted, so do it in the web UI
Colors (valid for portfolio / project / enum option)
none red orange yellow-orange yellow yellow-green green blue-green
aqua blue indigo purple magenta hot-pink pink cool-gray
Testing
ASANA_TOKEN=$(cat ~/.asana_token) npm run smokeCreates real items in the token's first workspace with names starting with ZZ-mcp-smoke-* → checks every tool → deletes all of them itself
If no token is provided, it only runs the first half (server boot + list tools)
Working notes
429 → automatically retries 3 times using
Retry-AfterErrors from Asana are returned as the actual API message (says which field is missing / which gid is wrong), not just a status code
Fields not sent are left untouched — a
portfolio_updatethat only sendsnamedoesn't clear the color
Available Tools
23 toolsasana_findFind gid by nameA
Typeahead search that turns a name you can see in the Asana UI into the gid every other tool needs.
Inputs: type (required), query (required), workspace_gid (required), count.
asana_list_custom_fieldsList 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.
Inputs: project_gid, portfolio_gid, workspace_gid.
asana_whoamiWho am IA
The authenticated user and their workspaces. Call this first — almost every create call needs a workspace_gid.
Inputs: no named parameters.
custom_field_attachAttach custom field to project or portfolioB
Make an existing custom field available on a project or a portfolio.
Inputs: custom_field_gid (required), project_gid, insert_after, is_important, +2 more.
custom_field_createCreate custom fieldB
Create a workspace custom field. For a dropdown use type 'enum' (single-select) or 'multi_enum' (multi-select) and pass enum_options.
Inputs: name (required), type (required), workspace_gid (required), precision, +2 more.
custom_field_updateRename / update custom fieldA
Change a custom field's name or description. Enum values are edited with the enum_option_* tools.
Inputs: custom_field_gid (required), name, description.
enum_option_createCreate dropdown valueA
Add a value to an enum / multi_enum custom field. Appended at the end unless you give a position.
Inputs: name (required), custom_field_gid (required), color, insert_after, +1 more.
enum_option_reorderReorder dropdown valueA
Move an existing dropdown value to a new position within its custom field.
Inputs: enum_option_gid (required), custom_field_gid (required), after_enum_option, before_enum_option.
enum_option_updateRename / disable dropdown valueA
Rename, recolor, or disable a dropdown value. Asana has no delete — set enabled:false to retire a value; tasks already holding it keep it.
Inputs: enum_option_gid (required), name, color, enabled.
member_addAdd member to project or portfolioA
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.
Inputs: member_gid (required), parent_gid (required), access_level (required).
member_listList members of a project or portfolioB
Who currently has access, and at what level.
Inputs: parent_gid (required).
portfolio_add_itemAdd project to portfolioA
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.
Inputs: item_gid (required), portfolio_gid (required), insert_after, insert_before.
portfolio_createCreate portfolioC
Create a portfolio in a workspace.
Inputs: name (required), workspace_gid (required), color, public.
portfolio_list_itemsList portfolio itemsC
The projects/portfolios inside a portfolio, in their current display order.
Inputs: portfolio_gid (required).
portfolio_remove_itemRemove item from portfolioA
Remove a project from a portfolio. This also drops any portfolio-level custom field values set on that project.
Inputs: confirm (required), item_gid (required), portfolio_gid (required).
portfolio_updateRename / update portfolioA
Change a portfolio's name, color, or visibility. Only the fields you pass are touched.
Inputs: portfolio_gid (required), name, color, public.
project_createCreate projectB
Create a project in a workspace (team_gid is required in an organization).
Inputs: name (required), workspace_gid (required), color, notes, +3 more.
project_duplicateDuplicate projectA
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.
Inputs: name (required), project_gid (required), include, team_gid.
project_list_sectionsList project sectionsB
Sections of a project in display order — the gids needed by section_reorder.
Inputs: project_gid (required).
project_updateRename / update projectC
Change a project's name, notes, color, default view, or archived state.
Inputs: project_gid (required), name, color, notes, +3 more.
section_createCreate sectionB
Add a section to a project, optionally at a chosen position.
Inputs: name (required), project_gid (required), insert_after, insert_before.
section_reorderReorder sectionC
Move an existing section to a new position within its project.
Inputs: project_gid (required), section_gid (required), after_section, before_section.
section_updateRename sectionA
Rename an existing section.
Inputs: name (required), section_gid (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Read and write Mission Control state via MCP — projects, tasks, subtasks, templates, status updates.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Official Todoist MCP server. Manage tasks and projects. Hosted, no API key needed.
A MCP server built for developers enabling Git based project management with project and personal…
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server that uses AI to generate structured Asana project plans from diverse sources like text, PDFs, and meeting transcripts. It enables users to preview, generate, and directly sync detailed task lists, subtasks, and dependencies into Asana.1MIT
- AlicenseBqualityCmaintenanceMCP server for the Asana API that allows AI agents to read and optionally write to Asana tasks, comments, and custom fields, with tiered access controls and no delete tools.858 npmMIT
- AlicenseNot gradedqualityDmaintenanceHigh-performance MCP server that transforms how AI assistants interact with Asana, enabling complex task hierarchies and batch operations for efficient project management.6 npm3MIT
- AlicenseAqualityDmaintenanceA local MCP server for Asana that uses a personal access token to read and manage Asana projects, tasks, sections, and comments via the standard Asana REST API.820 npmMIT