What can @roychri/mcp-server-asana do?

asana task crud operations via mcp protocol, project and workspace context retrieval, task filtering and search via custom fields and metadata, task attachment and comment management, task assignment and status workflow transitions, mcp server lifecycle and authentication management

@roychri/mcp-server-asana

MCP ServerFree

MCP Server for Asana

Open Source

/ 100

6 capabilities

Capabilities6 decomposed

asana task crud operations via mcp protocol

Medium confidence

Exposes Asana task creation, reading, updating, and deletion operations through the Model Context Protocol (MCP) interface, allowing Claude and other MCP-compatible clients to directly manipulate Asana tasks without custom API integration code. Implements MCP resource and tool handlers that translate client requests into authenticated Asana API calls, managing request/response serialization and error handling within the MCP server lifecycle.

Solves for

I want Claude to create, update, or delete Asana tasks directly from a conversationI need to expose Asana task operations as tools that an AI agent can invokeI want to build a chatbot that manages my Asana workflow without writing custom API glue code

Best for

Teams using Claude with Asana who want native task automation

Developers building MCP-compatible AI agents that need project management capabilities

Non-technical users wanting to control Asana through conversational AI

Requires

Asana Personal Access Token (PAT) with tasks:read and tasks:write scopes

Node.js 16+ runtime

MCP client compatible with stdio transport (Claude Desktop, custom implementations)

Limitations

Limited to Asana API capabilities and rate limits (15 requests/second standard tier)

No built-in caching of task state — each operation requires a fresh API call

Requires valid Asana Personal Access Token with appropriate scopes; token rotation not automated

What makes it unique

Implements MCP server pattern specifically for Asana, using stdio transport to enable seamless integration with Claude Desktop and other MCP clients without requiring HTTP endpoint management or webhook infrastructure

vs alternatives

Simpler than building custom Asana API integrations because MCP handles protocol negotience and tool discovery automatically; tighter than Zapier/Make because operations execute in-process with Claude's reasoning context

project and workspace context retrieval

Medium confidence

Fetches and exposes Asana workspace, team, and project metadata through MCP resources, allowing AI agents to discover available projects, teams, and organizational structure before executing task operations. Implements resource handlers that query Asana's organizational endpoints and cache results for the session, enabling context-aware task operations (e.g., 'add task to the Marketing project' resolved via project name lookup).

Solves for

I want Claude to know which Asana projects and teams exist so it can route tasks correctlyI need to list all projects in my workspace to let users select a target for new tasksI want the AI agent to understand my organizational structure before creating tasks

Best for

Multi-project Asana workspaces where task routing requires project discovery

Teams building conversational task creation flows that need to resolve project names to GIDs

Organizations with complex team hierarchies wanting AI-driven task distribution

Requires

Asana PAT with workspaces:read and projects:read scopes

Workspace GID (obtainable from Asana account settings or API discovery)

Limitations

No real-time sync — project/team changes in Asana require server restart to reflect

Asana API pagination limits project listing to 100 items per request; large workspaces require manual pagination handling

Custom fields and project templates not fully exposed — only standard Asana fields returned

What makes it unique

Uses MCP resource pattern to expose Asana organizational metadata as queryable context, enabling Claude to make informed decisions about task placement without requiring explicit user specification of project GIDs

vs alternatives

More discoverable than raw Asana API because MCP clients can introspect available resources; more flexible than hardcoded project mappings because it dynamically reflects workspace structure

task filtering and search via custom fields and metadata

Medium confidence

Implements task query capabilities that filter Asana tasks by standard fields (assignee, due date, status, priority) and custom fields, translating natural language filter expressions into Asana API query syntax. Uses Asana's opt_fields parameter to selectively fetch task attributes and supports pagination for large result sets, enabling AI agents to locate specific tasks before performing updates or analysis.

Solves for

I want Claude to find all overdue tasks assigned to meI need to search for tasks matching specific custom field values (e.g., 'all tasks with Status=In Review')I want to list tasks in a project filtered by assignee and due date range

Best for

Teams using Asana custom fields for workflow tracking who want AI-driven task discovery

Developers building task analytics or reporting agents

Users wanting conversational task search ('show me all high-priority tasks due this week')

Requires

Asana PAT with tasks:read scope

Project GID or assignee GID to scope the query

Custom field GID if filtering by custom fields

Limitations

Asana's query API does not support complex boolean logic (AND/OR combinations) — filters are ANDed together

Custom field filtering requires knowing the custom field GID; field name-to-GID mapping not automated

No full-text search on task descriptions — only metadata field filtering supported

What makes it unique

Abstracts Asana's query API complexity into a unified filter interface that MCP clients can invoke, handling opt_fields optimization and pagination transparently so Claude doesn't need to understand Asana API query syntax

vs alternatives

More capable than simple task listing because it supports custom field filtering; simpler than building a full search index because it leverages Asana's native query engine

task attachment and comment management

Medium confidence

Enables adding attachments (files, links) and comments to Asana tasks through MCP tool handlers, translating client requests into Asana's attachment and story (comment) API endpoints. Supports file uploads via URL attachment and inline comment creation with optional mentions, allowing AI agents to enrich tasks with context, decisions, or external references without manual Asana UI interaction.

Solves for

I want Claude to add a comment to a task with context or a decision rationaleI need to attach a document or link to an Asana task from an external systemI want the AI agent to mention team members in task comments for notifications

Best for

Teams using Asana comments for async decision-making and documentation

Workflows that need to attach external documents (reports, designs, logs) to tasks programmatically

Organizations wanting AI-driven task enrichment with context and analysis

Requires

Asana PAT with tasks:write scope

Task GID for the target task

For mentions: Asana user GID of the person to mention

Limitations

File attachments limited to URL-based links; direct file uploads require pre-uploading to a URL-accessible location

Comment mentions use Asana user GID, not email — requires user lookup to resolve names to GIDs

No support for comment editing or deletion — only creation

What makes it unique

Wraps Asana's story and attachment APIs in MCP tool handlers, enabling Claude to add context and external references to tasks as part of its reasoning process, creating an audit trail of AI-driven decisions within Asana

vs alternatives

More integrated than external logging because comments live in Asana's native interface; more flexible than webhooks because it's synchronous and can respond to Claude's reasoning in real-time

task assignment and status workflow transitions

Medium confidence

Implements task assignment and status update operations that respect Asana's workflow rules and custom status definitions, translating AI agent intents into valid Asana state transitions. Validates status changes against the project's custom status schema and enforces assignee constraints, preventing invalid state transitions and providing feedback on workflow violations.

Solves for

I want Claude to assign a task to a specific team member based on availability or expertiseI need to move a task through workflow stages (e.g., 'To Do' → 'In Progress' → 'Review' → 'Done')I want the AI agent to update task status based on external events or conditions

Best for

Teams with custom Asana workflows who want AI-driven task routing and status management

Automation scenarios where external events trigger task status changes

Organizations using Asana's custom status feature for domain-specific workflows

Requires

Asana PAT with tasks:write scope

Task GID

For assignment: target user GID

Limitations

Custom status validation requires fetching project schema first — no automatic schema caching

Assignee validation limited to users in the workspace; no cross-workspace assignment

No support for conditional assignments (e.g., 'assign to whoever has the least tasks') — requires explicit user GID

What makes it unique

Integrates Asana's custom status schema validation into MCP tool handlers, enabling Claude to understand and respect project-specific workflows rather than treating all status values as equivalent

vs alternatives

More workflow-aware than generic task update APIs because it validates transitions against project schema; more reliable than direct API calls because it prevents invalid state combinations

mcp server lifecycle and authentication management

Medium confidence

Manages the MCP server startup, shutdown, and authentication flow, handling Asana PAT initialization from environment variables or configuration, setting up stdio transport for client communication, and gracefully handling connection errors. Implements MCP server initialization protocol to advertise available tools and resources to connecting clients, enabling automatic tool discovery in Claude Desktop and other MCP-compatible applications.

Solves for

I want to run the Asana MCP server and have it automatically available in Claude DesktopI need to configure the server with my Asana credentials securelyI want the server to handle connection errors and reconnection gracefully

Best for

Claude Desktop users wanting to add Asana integration without manual API setup

Developers deploying MCP servers in containerized or serverless environments

Teams managing multiple MCP servers and needing standardized lifecycle patterns

Requires

Node.js 16+ with npm or yarn

Asana Personal Access Token set in environment variable

MCP client (Claude Desktop, custom implementation) with stdio transport support

Limitations

Asana PAT must be provided via environment variable (PAT_ASANA or similar) — no interactive credential prompt

No built-in credential rotation or expiration handling — expired tokens require manual server restart

Stdio transport only — no HTTP or WebSocket support for remote deployment

What makes it unique

Implements MCP server pattern with stdio transport, enabling zero-configuration integration with Claude Desktop via config file entry rather than requiring HTTP endpoint management or webhook registration

vs alternatives

Simpler than building a custom HTTP API because MCP handles protocol negotiation; more secure than API keys in URLs because credentials stay in environment variables and never transit over HTTP

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with @roychri/mcp-server-asana, ranked by overlap. Discovered automatically through the match graph.

MCP Server29

@roychri/mcp-server-asana

MCP Server for Asana

asana task retrieval and filteringasana project and workspace enumerationasana task update and status managementasana task creation via mcp protocol

4 shared capabilities

MCP Server22

Todoist

** - Full implementation of Todoist Rest API for MCP server

task-retrieval-and-filteringtask-update-and-modificationtask-creation-via-mcp-protocolproject-and-section-management

4 shared capabilities

MCP Server25

targetprocess-mcp-server

MCP server for Tartget Process

targetprocess-entity-search-and-filteringtargetprocess-project-and-portfolio-context-retrievaltargetprocess-resource-crud-operations

3 shared capabilities

MCP Server46

Asana MCP Server

Create and manage Asana tasks, projects, and workspaces via MCP.

full-text task search with workspace-scoped filteringmcp-protocol task creation and mutation with schema validation

2 shared capabilities

MCP Server23

Taskeract

** - Official Taskeract MCP Server for integrating your [Taskeract](https://www.taskeract.com/) project tasks and load the context of your tasks into your MCP enabled app.

taskeract-project-task-enumerationtask-context-loading-into-mcp-clients

2 shared capabilities

MCP Server25

Dart

** - Interact with task, doc, and project data in [Dart](https://itsdart.com), an AI-native project management tool

mcp-based task creation with metadata bindingconfiguration retrieval for workspace context

2 shared capabilities

Best For

✓Teams using Claude with Asana who want native task automation
✓Developers building MCP-compatible AI agents that need project management capabilities
✓Non-technical users wanting to control Asana through conversational AI
✓Multi-project Asana workspaces where task routing requires project discovery
✓Teams building conversational task creation flows that need to resolve project names to GIDs
✓Organizations with complex team hierarchies wanting AI-driven task distribution
✓Teams using Asana custom fields for workflow tracking who want AI-driven task discovery
✓Developers building task analytics or reporting agents

Known Limitations

⚠Limited to Asana API capabilities and rate limits (15 requests/second standard tier)
⚠No built-in caching of task state — each operation requires a fresh API call
⚠Requires valid Asana Personal Access Token with appropriate scopes; token rotation not automated
⚠No transaction support — multi-step operations (create task, add subtasks, assign) execute sequentially with failure risk
⚠No real-time sync — project/team changes in Asana require server restart to reflect
⚠Asana API pagination limits project listing to 100 items per request; large workspaces require manual pagination handling

Requirements

Asana Personal Access Token (PAT) with tasks:read and tasks:write scopesNode.js 16+ runtimeMCP client compatible with stdio transport (Claude Desktop, custom implementations)Network access to api.asana.comAsana PAT with workspaces:read and projects:read scopesWorkspace GID (obtainable from Asana account settings or API discovery)Asana PAT with tasks:read scopeProject GID or assignee GID to scope the query

Input / Output

Accepts: JSON task objects with fields like name, description, assignee_gid, due_on, custom_fields, Task GID (global identifier) for read/update/delete operations, Project GID for task listing and filtering, Workspace GID, Optional project name filter string for search, Filter object with optional fields: assignee_gid, due_on_before, due_on_after, completed, priority, custom_field_gid, custom_field_value, Pagination parameters: limit (1-100), offset, Comment text (string, up to Asana's character limit ~4000 chars), Optional mention array with user GIDs, Attachment URL (for URL-based attachments), Attachment name/title, Task GID, Assignee user GID (or null to unassign), Status name or GID (string), Optional due date update, Environment variable: ASANA_PAT or similar, MCP initialization message from client

Produces: JSON task objects with full Asana schema (id, name, description, assignee, due_date, custom_fields, etc.), Task lists with pagination metadata, Operation confirmation with updated task state, JSON array of workspace objects with id, name, is_organization, JSON array of project objects with id, name, owner, team, archived status, JSON array of team objects with id, name, organization, JSON array of task objects matching filters, Pagination metadata (next_page offset if more results exist), JSON story object with id, text, created_at, created_by, JSON attachment object with id, name, url, created_at, JSON task object with updated assignee, status, due_date fields, Error message if status transition is invalid, MCP server initialization response with tool and resource schemas, Tool invocation responses, Error messages on connection failure

UnfragileRank

Adoption35%(30% weight)

Quality14%(25% weight)

Ecosystem59%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

6 capabilities

Visit @roychri/mcp-server-asana→

Repository Details

Package Details

npm

Registry

1.8.0

Version

2,738

Weekly Downloads

About

MCP Server for Asana

Alternatives to @roychri/mcp-server-asana

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of @roychri/mcp-server-asana?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

npm

Looking for something else?

Search →

Capabilities6 decomposed

asana task crud operations via mcp protocol

Medium confidence

Solves for

Best for

Teams using Claude with Asana who want native task automation

Developers building MCP-compatible AI agents that need project management capabilities

Non-technical users wanting to control Asana through conversational AI

Requires

Asana Personal Access Token (PAT) with tasks:read and tasks:write scopes

Node.js 16+ runtime

MCP client compatible with stdio transport (Claude Desktop, custom implementations)

Limitations

Limited to Asana API capabilities and rate limits (15 requests/second standard tier)

No built-in caching of task state — each operation requires a fresh API call

Requires valid Asana Personal Access Token with appropriate scopes; token rotation not automated

What makes it unique

vs alternatives

project and workspace context retrieval

Medium confidence

Solves for

Best for

Multi-project Asana workspaces where task routing requires project discovery

Teams building conversational task creation flows that need to resolve project names to GIDs

Organizations with complex team hierarchies wanting AI-driven task distribution

Requires

Asana PAT with workspaces:read and projects:read scopes

Workspace GID (obtainable from Asana account settings or API discovery)

Limitations

No real-time sync — project/team changes in Asana require server restart to reflect

Asana API pagination limits project listing to 100 items per request; large workspaces require manual pagination handling

Custom fields and project templates not fully exposed — only standard Asana fields returned

What makes it unique

vs alternatives

More discoverable than raw Asana API because MCP clients can introspect available resources; more flexible than hardcoded project mappings because it dynamically reflects workspace structure

task filtering and search via custom fields and metadata

Medium confidence

Solves for

Best for

Teams using Asana custom fields for workflow tracking who want AI-driven task discovery

Developers building task analytics or reporting agents

Users wanting conversational task search ('show me all high-priority tasks due this week')

Requires

Asana PAT with tasks:read scope

Project GID or assignee GID to scope the query

Custom field GID if filtering by custom fields

Limitations

Asana's query API does not support complex boolean logic (AND/OR combinations) — filters are ANDed together

Custom field filtering requires knowing the custom field GID; field name-to-GID mapping not automated

No full-text search on task descriptions — only metadata field filtering supported

What makes it unique

vs alternatives

More capable than simple task listing because it supports custom field filtering; simpler than building a full search index because it leverages Asana's native query engine

task attachment and comment management

Medium confidence

Solves for

Best for

Teams using Asana comments for async decision-making and documentation

Workflows that need to attach external documents (reports, designs, logs) to tasks programmatically

Organizations wanting AI-driven task enrichment with context and analysis

Requires

Asana PAT with tasks:write scope

Task GID for the target task

For mentions: Asana user GID of the person to mention

Limitations

File attachments limited to URL-based links; direct file uploads require pre-uploading to a URL-accessible location

Comment mentions use Asana user GID, not email — requires user lookup to resolve names to GIDs

No support for comment editing or deletion — only creation

What makes it unique

vs alternatives

More integrated than external logging because comments live in Asana's native interface; more flexible than webhooks because it's synchronous and can respond to Claude's reasoning in real-time

task assignment and status workflow transitions

Medium confidence

Solves for

Best for

Teams with custom Asana workflows who want AI-driven task routing and status management

Automation scenarios where external events trigger task status changes

Organizations using Asana's custom status feature for domain-specific workflows

Requires

Asana PAT with tasks:write scope

Task GID

For assignment: target user GID

Limitations

Custom status validation requires fetching project schema first — no automatic schema caching

Assignee validation limited to users in the workspace; no cross-workspace assignment

No support for conditional assignments (e.g., 'assign to whoever has the least tasks') — requires explicit user GID

What makes it unique

Integrates Asana's custom status schema validation into MCP tool handlers, enabling Claude to understand and respect project-specific workflows rather than treating all status values as equivalent

vs alternatives

More workflow-aware than generic task update APIs because it validates transitions against project schema; more reliable than direct API calls because it prevents invalid state combinations

mcp server lifecycle and authentication management

Medium confidence

Solves for

Best for

Claude Desktop users wanting to add Asana integration without manual API setup

Developers deploying MCP servers in containerized or serverless environments

Teams managing multiple MCP servers and needing standardized lifecycle patterns

Requires

Node.js 16+ with npm or yarn

Asana Personal Access Token set in environment variable

MCP client (Claude Desktop, custom implementation) with stdio transport support

Limitations

Asana PAT must be provided via environment variable (PAT_ASANA or similar) — no interactive credential prompt

No built-in credential rotation or expiration handling — expired tokens require manual server restart

Stdio transport only — no HTTP or WebSocket support for remote deployment

What makes it unique

vs alternatives

Simpler than building a custom HTTP API because MCP handles protocol negotiation; more secure than API keys in URLs because credentials stay in environment variables and never transit over HTTP

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to @roychri/mcp-server-asana

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

@roychri/mcp-server-asana

Capabilities6 decomposed

asana task crud operations via mcp protocol

project and workspace context retrieval

task filtering and search via custom fields and metadata

task attachment and comment management

task assignment and status workflow transitions

mcp server lifecycle and authentication management

Related Artifactssharing capabilities

@roychri/mcp-server-asana

Todoist

targetprocess-mcp-server

Asana MCP Server

Taskeract

Dart

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Repository Details

Package Details

About

Categories

Alternatives to @roychri/mcp-server-asana

Are you the builder of @roychri/mcp-server-asana?

Get the weekly brief

Data Sources

@roychri/mcp-server-asana

Capabilities6 decomposed

asana task crud operations via mcp protocol

project and workspace context retrieval

task filtering and search via custom fields and metadata

task attachment and comment management

task assignment and status workflow transitions

mcp server lifecycle and authentication management

Related Artifactssharing capabilities

@roychri/mcp-server-asana

Todoist

targetprocess-mcp-server

Asana MCP Server

Taskeract

Dart

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Repository Details

Package Details

About

Categories

Alternatives to @roychri/mcp-server-asana

Are you the builder of @roychri/mcp-server-asana?

Get the weekly brief

Data Sources