Skip to main content
Glama

asana-admin-mcp

MCP server for Asana 구조화 — portfolio, custom field / dropdown, project, section 표준 Asana connector가 채우지 못하는 부분을 채움 (그쪽은 task/read 중심)


⚠️ Dashboard는 할 수 없음 — 이 MCP의 한계가 아님

Asana는 Dashboard / chart / widget / project view tab용 public API를 전혀 제공하지 않음 (공식 OpenAPI spec의 175개 endpoints를 전부 확인 — 하나도 없음)

자동화할 수 있는 유일한 방법은 project_duplicate — 스펙에 duplicate project 시 Project Views (List / Board / Dashboard 탭)는 항상 함께 복사되며 끌 수 없다고 명시 → “프로토타입 프로젝트” 하나에 Dashboard를 설정해 두고 새 프로젝트가 필요할 때마다 duplicate

🟡 아직 검증되지 않음: 스펙에는 “Project Views”가 따라간다고 되어 있지만, Dashboard에 설정한 chart가 함께 가는지 아니면 빈 탭만 가는지는 명확하지 않음 — API로 확인 불가 (chart를 읽을 endpoint 없음) 눈으로 직접 확인해야 함 2026-08-17 smoke test에서는 chart가 없는 프로젝트를 duplicate 했으므로 이 질문에 아직 답할 수 없음

참고: Project Template은 Dashboard를 가져가지 않음 (Asana 포럼에 남아 있는 feature request) template이 아니라 duplicate를 사용해야 함


Related MCP server: asana-mcp

설치

1. 먼저 Asana token을 준비하세요 (각자 자신의 것이 필요함)

**GET-TOKEN.md**를 따라 진행 → ~/.asana_token에 저장

printf '%s' 'วาง_token_ตรงนี้' > ~/.asana_token && chmod 600 ~/.asana_token

token은 개인 권한에 연결됨 다른 사람의 것 사용 금지 — Asana 로그에 token 소유자 이름이 표시됨

2. plugin 설치 (권장)

Claude Code에서 2줄을 입력하세요:

/plugin marketplace add plakorp/asana-admin-mcp
/plugin install asana-admin@asana-admin-mcp

Claude Code가 repo를 clone하고 npm ci를 직접 실행한 다음 MCP를 등록해 줌 — ~/.claude.json을 건드릴 필요 없음 나중에 업데이트는 /plugin update

컴퓨터에 **Node 20+**가 필요함 (node -v로 확인)

방법 2 — 수동 설치 (plugin을 사용하고 싶지 않다면)

repo를 clone한 뒤 ติดตั้ง-asana-admin-mcp.command를 더블클릭 스크립트가 token을 요청하고, npm install을 실행한 다음 ~/.claude.json을 작성해 줌 (매번 backup)

두 방법을 동시에 사용하지 마세요 — asana-admin이라는 MCP가 2개 중복됩니다

Token은 env ASANA_TOKEN을 먼저 읽고, 없으면 ~/.asana_token으로 fallback → token은 repo에 절대 없으며 ~/.claude.json에 있을 필요도 없음


Tools (21)

모든 tool은 이름이 아닌 gid를 받음 — asana_find로 이름 → gid 변환 먼저

Discovery

Tool

설명

asana_whoami

자신 + 모든 workspace (거의 모든 create에 workspace_gid가 필요하므로 여기서 시작)

asana_find

typeahead로 이름에서 gid 검색 — project / portfolio / custom_field / task / team / user / tag / goal

asana_list_custom_fields

workspace 또는 project/portfolio에 연결된 custom field — dropdown 그룹의 모든 tool 입력인 enum_options와 gid를 반환

Portfolio

Tool

설명

portfolio_create

portfolio 생성

portfolio_update

rename / 색상 변경 / public

portfolio_list_items

portfolio의 프로젝트를 실제 표시 순서대로 보기

portfolio_add_item

portfolio에 프로젝트 추가 + 위치 지정 가능 (insert_before / insert_after) — 이미 있는 item에 다시 호출 = 위치 이동

portfolio_remove_item

프로젝트 제거 (confirm: true를 보내야 함)

Custom field / dropdown

Tool

설명

custom_field_create

field 생성 — enum (하나만 선택하는 dropdown) / multi_enum / text / number / date / people

custom_field_update

rename / description 수정

enum_option_create

dropdown에 값 추가 + 위치 지정 가능

enum_option_update

rename / 색상 변경 / enabled:false로 사용 중지

enum_option_reorder

dropdown 값 순서 정렬

custom_field_attach

field를 project 또는 portfolio에 연결 (is_important:true = 열로 표시)

Asana는 dropdown 값을 삭제할 수 없음 — enabled:false만 가능, 그 값을 선택한 작업은 원래 값을 계속 유지함

Project / Section

Tool

설명

project_create

프로젝트 생성 (organization에서는 team_gid 필요)

project_update

rename / notes / 색상 / default_view / archive

project_duplicate

프로젝트 복사 Dashboard도 함께 가져감 — dashboard 문제의 유일한 해결책 (job 반환, async로 동작)

project_list_sections

section 순서 + gid

section_create

section 추가 + 위치 지정 가능

section_update

section rename

section_reorder

section 순서 정렬

project / portfolio / custom field를 삭제하는 tool은 의도적으로 없음 — 삭제하면 복구할 수 없으니 웹 페이지에서 수행


색상 (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


테스트

ASANA_TOKEN=$(cat ~/.asana_token) npm run smoke

token의 첫 번째 workspace에 ZZ-mcp-smoke-*로 시작하는 실제 데이터를 생성 → 모든 tool 검증 → 전부 직접 삭제 token을 넣지 않으면 전반부만 실행 (server boot + list tools)


작업 참고 사항

  • 429 → Retry-After에 따라 자동 retry 3회

  • Asana의 error는 status code만이 아니라 API의 실제 메시지로 반환 (어떤 field가 누락됐는지 / 어떤 gid가 잘못됐는지 알려줌)

  • 보내지 않은 필드는 건드리지 않음 — name만 보낸 portfolio_update는 색상을 지우지 않음

Available Tools

23 tools
asana_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

    B3.4/5.0

    Scored across 23 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      An 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.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      High-performance MCP server that transforms how AI assistants interact with Asana, enabling complex task hierarchies and batch operations for efficient project management.
      6 npm
      3
      MIT