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

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_token

The 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-mcp

Claude 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

Portfolio

Custom field / dropdown

Asana cannot delete dropdown values — you can only set enabled:false; tasks that had selected that value will keep the old value

Project / Section

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 smoke

Creates 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-After

• Errors 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_update that only sends name doesn't clear the color