Asanamcp MCP Server

1. Get an Asana Personal Access Token at https://app.asana.com/0/my-apps

Local serverstdio

What is the Asanamcp MCP server?

If you already use Asanamcp, the asanamcp mcp server is the piece that lets your assistant work with it directly. 1. Get an Asana Personal Access Token at https://app.asana.com/0/my-apps.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • asana_workspaces — List all workspaces
  • asana_get — Fetch any resource (projects, tasks, portfolios, etc.)
  • asana_create — Create resources (tasks, comments, projects, etc.)
  • asana_update — Update existing resources
  • asana_delete — Permanently delete resources (irreversible)
  • asana_link — Manage relationships (task↔project, dependencies, etc.)
  • asana_task_search — Search for tasks with rich filters (assignee, due date, etc.)
  • asana_resource_search — Search for resources by name (projects, templates, users, teams, etc.)

Credentials and setup notes

Configuration is passed through the environment: ASANA_TOKEN, ASANA_DEFAULT_WORKSPACE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Asanamcp's toolset — asana_workspaces, asana_get, asana_create and 5 more — is a fair guide to whether it matches your workflow. It is maintained by adlio; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Asanamcp's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
asana_workspacesList all workspaces
asana_getFetch any resource (projects, tasks, portfolios, etc.)
asana_createCreate resources (tasks, comments, projects, etc.)
asana_updateUpdate existing resources
asana_deletePermanently delete resources (irreversible)
asana_linkManage relationships (task↔project, dependencies, etc.)
asana_task_searchSearch for tasks with rich filters (assignee, due date, etc.)
asana_resource_searchSearch for resources by name (projects, templates, users, teams, etc.)

Configuration

VariableDescriptionRequired
ASANA_TOKENCredential the server authenticates with.Yes
ASANA_DEFAULT_WORKSPACEConfiguration value read at startup.Optional

Example prompts to try

  • Use Asanamcp to asana workspaces.
  • Use Asanamcp to asana get.
  • Use Asanamcp to asana create.

Frequently asked questions

It connects Asanamcp to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (asana_workspaces, asana_get, asana_create, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Asanamcp directly.