Overview
What is MCP Server for Asana?
MCP Server for Asana is a Model Context Protocol server implementation that enables AI assistants like Claude Desktop to interact with the Asana API. It provides a set of tools for managing tasks, projects, workspaces, and comments directly from a natural language interface.
How to use MCP Server for Asana?
Install the npm package and configure your Asana access token. In the AI tool of your choice, simply ask questions or give commands about Asana tasks, projects, workspaces, or comments—mentioning "asana" helps the LLM pick the right tool. No specific config file keys are shown beyond environment variables (ASANA_ACCESS_TOKEN, DEFAULT_WORKSPACE_ID).
Key features of MCP Server for Asana
- 20+ tools for Asana tasks, projects, workspaces, and comments
- Search tasks with advanced filters (assignee, custom fields, dates)
- Create, update, and get task details including custom fields
- Manage project status updates and sections
- Add task dependencies, dependents, and followers
- Support for custom fields of all types (enum, text, number, date, multi-enum)
Use cases of MCP Server for Asana
- Ask "How many unfinished tasks in our Sprint 30 project?" from Claude Desktop
- Create tasks with custom fields, assignees, and due dates via natural language
- Search for projects by name pattern and retrieve their task counts
- Add comments or status updates to tasks and projects
- Manage task dependencies and subtasks across workspaces
FAQ from MCP Server for Asana
What tools does MCP Server for Asana provide?
It provides 20 tools covering workspaces, projects, tasks, stories, subtasks, followers, dependencies, and project statuses—all documented with required and optional inputs.
What custom field types are supported?
Enum fields (use enum_option.gid), text fields (string), number fields (number), date fields (YYYY-MM-DD string), and multi-enum fields (array of enum option GIDs). See the README for details on finding custom field GIDs.
How do I find the GID for a custom field or enum option?
Use the asana_get_task tool with opt_fields set to custom_fields,custom_fields.enum_options. The response includes each field's gid, name, resource_subtype, and for enums, the enum_options array.
What are the runtime requirements?
Node.js and an Asana personal access token. The server uses the Asana REST API; no local database is stored—all data lives in Asana.
What transport does the server use?
The README does not specify the transport protocol (assumed MCP stdio or HTTP). Authentication is via an Asana API token set as an environment variable.
