asana-admin-mcp
asana-admin-mcp
MCP server para estructurar Asana — portfolio, custom field / dropdown, project, section Cubre el hueco que el conector estándar de Asana no cubre (ese se centra en task/read)
⚠️ Dashboard no es posible — y no es una limitación de este MCP
Asana no expone una API pública para Dashboard / chart / widget / project view tab en absoluto (hemos recorrido los 175 endpoints en la OpenAPI spec oficial — no hay ni uno)
La única forma automatizable es project_duplicate — la spec indica que al duplicar un project,
Project Views (pestañas List / Board / Dashboard) siempre se copian y no se pueden desactivar
→ Configura el Dashboard en un "proyecto plantilla" y haz duplicate cada vez que necesites un proyecto nuevo
🟡 No comprobado: la spec dice que "Project Views" se copian, pero no aclara si los chart configurados en el Dashboard también se copian o solo se obtiene una pestaña vacía — no se puede verificar por API (no hay endpoint para leer chart), hay que mirarlo a ojo el smoke test del 2026-08-17 duplicó un proyecto sin chart, así que aún no responde a esta cuestión
Nota: Project Template no incluye el Dashboard (sigue siendo una feature request pendiente en el foro de Asana) Hay que usar duplicate, no template
Related MCP server: asana-mcp
Instalación
1. Consigue primero tu token de Asana (cada uno debe tener el suyo)
Sigue GET-TOKEN.md → guárdalo en ~/.asana_token
printf '%s' 'วาง_token_ตรงนี้' > ~/.asana_token && chmod 600 ~/.asana_tokenel token está vinculado a permisos individuales no uses el de otra persona — el log de Asana mostrará el nombre del propietario del token
2. Instala el plugin (recomendado)
En Claude Code escribe 2 líneas:
/plugin marketplace add plakorp/asana-admin-mcp
/plugin install asana-admin@asana-admin-mcpClaude Code clonará el repo + ejecutará npm ci por ti y registrará el MCP — no necesitas tocar ~/.claude.json
Para actualizarlo más tarde, usa /plugin update
Necesitas Node 20+ en tu equipo (compruébalo con node -v)
Método 2 — instalación manual (si no quieres usar el plugin)
clona el repo y haz doble clic en ติดตั้ง-asana-admin-mcp.command
El script pedirá el token, ejecutará npm install y escribirá ~/.claude.json por ti (con backup en cada ejecución)
No uses los 2 métodos a la vez — tendrás dos MCP llamados
asana-adminduplicados
El token se lee primero de la variable de entorno ASANA_TOKEN; si no existe, se hace fallback a ~/.asana_token
→ el token nunca está en el repo ni necesita estar en ~/.claude.json
Herramientas (21)
Cada tool recibe un gid, no un nombre — usa asana_find para convertir nombre → gid primero
Descubrimiento
Tool | Descripción |
| tú mismo + todos los workspaces (empieza aquí, porque casi todo create necesita |
| typeahead para buscar gid por nombre — project / portfolio / custom_field / task / team / user / tag / goal |
| custom fields en el workspace o vinculados a project/portfolio — devuelve |
Portfolio
Tool | Descripción |
| crear portfolio |
| renombrar / cambiar color / public |
| ver los proyectos del portfolio en el orden en que se muestran realmente |
| añadir un proyecto al portfolio + puedes especificar la posición ( |
| quitar un proyecto (hay que enviar |
Custom field / dropdown
Tool | Descripción |
| crear field — |
| renombrar / editar description |
| añadir valor al dropdown + se puede especificar la posición |
| renombrar / cambiar color / |
| reordenar los valores del dropdown |
| vincular field a un project o portfolio ( |
Asana no puede eliminar valores de dropdown — solo se puede usar
enabled:false; las tareas que ya tenían ese valor seleccionado conservarán el valor original
Project / Section
Tool | Descripción |
| crear proyecto (en organization se necesita |
| renombrar / notes / color / |
| duplicar proyecto incluye el Dashboard — la única solución para el dashboard (devuelve job, funciona async) |
| secciones en orden + gid |
| añadir section + se puede especificar la posición |
| renombrar section |
| reordenar section |
No hay ninguna tool para eliminar project / portfolio / custom field a propósito — borrarlos no tiene vuelta atrás, hazlo en la web
Colores (válidos para 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
Pruebas
ASANA_TOKEN=$(cat ~/.asana_token) npm run smokeCrea objetos reales en el primer workspace del token con nombres que empiecen por ZZ-mcp-smoke-* → comprueba todas las tools → borra todo tú mismo
Si no se proporciona token, solo se ejecutará la primera mitad (server boot + list tools)
Notas de funcionamiento
429 → retry automático 3 veces según
Retry-Afterlos errores de Asana se devuelven como el mensaje real de la API (indica qué field falta / qué gid es incorrecto), no solo el status code
los campos que no se envían no se tocan — un
portfolio_updateque solo envíanameno limpia el 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