# roychri/mcp-server-asana [Health: Active]

**Category:** 🛠️ Other Tools and Integrations  
**Repository:** https://github.com/roychri/mcp-server-asana  
**GitHub Stars:** 148  
**npm Downloads (last month):** 10600  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/roychri-mcp-server-asana

## Description
This Model Context Protocol server implementation of Asana allows you to talk to Asana API from MCP Client such as Anthropic's Claude Desktop Application, and many more.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-server-asana": {
    "command": "npx",
    "args": ["-y","@roychri/mcp-server-asana"],
    "env": {
      "ASANA_ACCESS_TOKEN": "",
      "READ_ONLY_MODE": ""
    }
  }
}
```

**Requires environment variables:** `ASANA_ACCESS_TOKEN`, `READ_ONLY_MODE` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What roychri/mcp-server-asana MCP server does

The roychri/mcp-server-asana MCP server connects an MCP client to Asana’s API. It gives an agent structured operations for inspecting and changing Asana workspaces, projects, tasks, and task activity. The repository specifically identifies Anthropic’s Claude Desktop application as a supported example, while the implementation is intended for MCP clients more generally.

Read operations cover workspace listing, project lookup, task search, task details, task stories, project details, project task counts, project sections, multiple-task retrieval, and project status information. Search can use task text and several Asana attributes, including completion state, subtasks, attachments, dependencies, assignees, projects, sections, tags, teams, and custom fields.

Write operations include creating and updating tasks, creating subtasks, adding task comments or stories, and setting task dependencies and dependents. Task creation and updates can include names, notes, due dates, assignees, followers, parent tasks, projects, resource subtypes, completion state, and custom fields where supported by the individual tool.

## How it works

An MCP client sends tool calls to the local server. The server uses the supplied Asana access token to make API requests and returns the resulting workspace, project, task, or story data to the client. Most tools accept an `opt_fields` value so callers can request selected response fields.

For example, an agent can search a workspace for unfinished tasks, retrieve a task by ID, inspect its comments, and create a follow-up task. Project searches require a workspace and a regular-expression name pattern. Task searches require a workspace and can apply additional filters and sorting. Multiple-task retrieval accepts up to 25 task IDs.

## Setup and configuration

Install and run the roychri/mcp-server-asana MCP server through its npm package, then register the local process with the MCP client of your choice. The server requires `ASANA_ACCESS_TOKEN`, containing an Asana access token. The README does not specify a particular token creation workflow or client configuration file format, so those details depend on the client being used.

Set `READ_ONLY_MODE` to `true` to disable operations that create, update, or delete Asana data. In that mode, the create-task prompt is also disabled and only read operations remain available. This setting is useful when testing or when the client must not modify the connected workspace.

## Tools and capabilities

The documented tool groups include:

- Listing available Asana workspaces.
- Searching projects by workspace and name pattern.
- Searching tasks with filters, sorting, and custom-field criteria.
- Reading individual tasks, projects, stories, sections, counts, and project statuses.
- Creating tasks, subtasks, and task stories.
- Updating tasks and setting dependencies or dependents.
- Retrieving details for up to 25 tasks by GID in one request.

Tool inputs use Asana identifiers such as workspace IDs, project IDs, task IDs, and project status GIDs. Date fields documented for tasks use `YYYY-MM-DD` format.

## Limitations and notes

The roychri/mcp-server-asana MCP server requires an Asana access token and therefore cannot operate without credentials. Write access is available unless read-only mode is enabled, so clients should treat task creation, updates, comments, and dependency changes as state-changing actions. The documented multiple-task lookup is limited to 25 tasks per call. The available README excerpt lists project-status retrieval tools but does not provide details for every status-related operation.

_Full upstream README: https://allmcps.com/mcp/roychri-mcp-server-asana/readme_