Skip to main content
mcpFirst-partyLow risk Safety Privacy
Asana logo

Asana MCP Server for Claude

Interact with Asana workspaces to manage projects and tasks

HarnessClaude CodeCursorClaude Desktop

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://developers.asana.com/docs/using-asanas-mcp-server, https://github.com/JSONbored/awesome-claude/blob/main/content/mcp/asana-mcp-server.mdx
Brand
Asana
Brand domain
asana.com
Brand asset source
brandfetch
Package URL
/downloads/mcp/asana-mcp-server.mcpb
Package SHA256
686fda20bfa3699a449ee489e34d4d57de5279ee41755d346bf90c8289e7a7a1
Safety notes
Use a least-privilege Asana token and test task or project writes in a non-critical workspace before connecting production workflows.
Privacy notes
Asana task text, project metadata, comments, assignees, due dates, and workspace details may be sent through model context.
Author
Asana
Claim status
unclaimed
Last verified
2025-09-18

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as first-party.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    Package marked verified.

    Done
  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

2 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

10 to clear

Platforms

3 listed

Difficulty

0/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

10 prerequisites to line up before setup. Have accounts and credentials ready first.

0/10 ready
Account & credentials6Network & hosting2General22 minutes

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 2 risk areas. Review closely: credentials & tokens.

2 areas
  • SafetyCredentials & tokensUse a least-privilege Asana token and test task or project writes in a non-critical workspace before connecting production workflows.
  • PrivacyGeneralAsana task text, project metadata, comments, assignees, due dates, and workspace details may be sent through model context.

Safety notes

  • Use a least-privilege Asana token and test task or project writes in a non-critical workspace before connecting production workflows.

Privacy notes

  • Asana task text, project metadata, comments, assignees, due dates, and workspace details may be sent through model context.

Prerequisites

  • OAuth 2.0 authentication (required for MCP server via SSE transport)
  • Asana account with access to at least one workspace
  • Workspace membership with Member role or higher (Guest role insufficient for task creation)
  • Internet connection for accessing Asana API (https://app.asana.com)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • SSE (Server-Sent Events) transport support in MCP client
  • Rate limit awareness: Free tier 150 requests/minute, Paid tier 1,500 requests/minute
  • Understanding of Asana workspace, project, and task structure
  • OAuth scopes: default (access to all endpoints) or specific scopes as needed
  • Access to ~/.mcp-auth directory for OAuth token storage (may need cleanup if authentication fails)

Schema details

Install type
package
Reading time
1 min
Difficulty score
0
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
686fda20bfa3699a449ee489e34d4d57de5279ee41755d346bf90c8289e7a7a1
Collection metadata
Estimated setup
2 minutes
Difficulty
beginner
Full copyable content
{
  "asana": {
    "url": "https://mcp.asana.com/sse",
    "transport": "sse"
  }
}

About this resource

Content

Connect Claude to Asana for comprehensive project management and team collaboration.

Features

  • Create and manage tasks with rich metadata
  • Update project status and milestones
  • Assign team members and collaborators
  • Set due dates and task dependencies
  • Generate progress reports and analytics
  • Advanced Asana project and task management with workspace organization, team collaboration features, and project portfolio tracking
  • Batch operations support for efficient bulk task creation, updates, and assignments with automatic rate limit handling and retry logic
  • Real-time task synchronization capabilities with webhook integration support for monitoring project changes and triggering automated workflows
  • Advanced Asana project and task management with workspace organization, team collaboration features, and project portfolio tracking
  • Batch operations support for efficient bulk task creation, updates, and assignments with automatic rate limit handling and retry logic
  • Real-time task synchronization capabilities with webhook integration support for monitoring project changes and triggering automated workflows

Use Cases

  • Create tasks from meeting notes
  • Update project timelines and deadlines
  • Assign work to team members efficiently
  • Track milestone progress across projects
  • Generate status reports for stakeholders
  • Build automated project management workflows that sync external systems with Asana projects for real-time task tracking and team coordination
  • Build automated project management workflows that sync external systems with Asana projects for real-time task tracking and team coordination

Installation

Claude Code

  1. claude mcp add --transport sse asana https://mcp.asana.com/sse
  2. Verify installation: claude mcp list
  3. Test connection: claude mcp status asana

Claude Desktop

  1. Open Claude Desktop configuration file
  2. Add the Asana server configuration with SSE transport
  3. Restart Claude Desktop
  4. Authenticate via OAuth when prompted

Requirements

  • OAuth 2.0 authentication (required for MCP server via SSE transport)
  • Asana account with access to at least one workspace
  • Workspace membership with Member role or higher (Guest role insufficient for task creation)
  • Internet connection for accessing Asana API (https://app.asana.com)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • SSE (Server-Sent Events) transport support in MCP client
  • Rate limit awareness: Free tier 150 requests/minute, Paid tier 1,500 requests/minute
  • Understanding of Asana workspace, project, and task structure
  • OAuth scopes: default (access to all endpoints) or specific scopes as needed
  • Access to ~/.mcp-auth directory for OAuth token storage (may need cleanup if authentication fails)

Configuration

{
  "asana": {
    "url": "https://mcp.asana.com/sse",
    "transport": "sse"
  }
}

Examples

Create a task for the new feature

Common usage pattern for this MCP server

Ask Claude: "Create a task for the new feature"

Show all tasks due this week

Common usage pattern for this MCP server

Ask Claude: "Show all tasks due this week"

Update project status to on-track

Common usage pattern for this MCP server

Ask Claude: "Update project status to on-track"

Assign task to team member

Common usage pattern for this MCP server

Ask Claude: "Assign task to team member"

Create Task with Dependencies

Create a new Asana task with project assignment, dependencies, and due date

// Create Asana task with dependencies
const task = await asana.createTask({
  workspace: "1234567890",
  name: "Complete project documentation",
  projects: ["9876543210"],
  dependencies: ["task-id-1", "task-id-2"],
  due_on: "2025-12-31",
});

Create Task with Dependencies

Create a new Asana task with project assignment, dependencies, and due date

// Create Asana task with dependencies
const task = await asana.createTask({
  workspace: "1234567890",
  name: "Complete project documentation",
  projects: ["9876543210"],
  dependencies: ["task-id-1", "task-id-2"],
  due_on: "2025-12-31",
});

Security

  • OAuth authentication for secure access
  • Workspace permissions apply automatically
  • Audit trail maintained for all actions
  • Regular permission reviews recommended
  • Asana API tokens and personal access tokens must be securely stored and never exposed in client-side code or public repositories - use environment variables and secure credential management
  • OAuth access tokens should be used for third-party integrations instead of personal access tokens to ensure proper access control and token lifecycle management
  • Asana workspace and project IDs may expose organizational structure and team information - ensure workspace IDs are kept private and not shared in public configurations
  • Rate limiting and API quota management are critical for Asana MCP servers - implement proper rate limit handling, retry logic, and quota monitoring to prevent service disruption
  • Asana webhook configurations and payloads may contain sensitive project and task data - ensure webhook endpoints are properly secured with authentication and HTTPS encryption
  • Asana API tokens and personal access tokens must be securely stored and never exposed in client-side code or public repositories - use environment variables and secure credential management
  • OAuth access tokens should be used for third-party integrations instead of personal access tokens to ensure proper access control and token lifecycle management
  • Asana workspace and project IDs may expose organizational structure and team information - ensure workspace IDs are kept private and not shared in public configurations
  • Rate limiting and API quota management are critical for Asana MCP servers - implement proper rate limit handling, retry logic, and quota monitoring to prevent service disruption
  • Asana webhook configurations and payloads may contain sensitive project and task data - ensure webhook endpoints are properly secured with authentication and HTTPS encryption

Troubleshooting

OAuth authentication fails or connection times out

Remove ~/.mcp-auth directory with rm -rf ~/.mcp-auth and re-authenticate. Verify SSE URL https://mcp.asana.com/sse is accessible. Logout and re-login to Asana account if errors persist.

Insufficient permissions to create or modify tasks

Verify workspace role is Member or higher (not Guest). Check project permissions allow task creation. Contact workspace admin to upgrade access level if needed.

Rate limit exceeded during bulk task operations

Free tier: 150 req/min limit. Paid tier: 1,500 req/min. Batch operations into groups of 10-20 tasks. Implement delays between batches. Check Retry-After header in 429 responses.

Tasks not appearing or data appears stale

Run tools/list command to refresh available endpoints. Restart MCP client connection. Verify you're querying correct workspace - switch workspaces if accessing wrong data.

Asana MCP server authentication errors with personal access tokens

Verify token is valid and not expired. Check token scopes match required permissions. Ensure token format is correct (Bearer token in Authorization header). For OAuth integrations, verify token refresh logic is working correctly.

Rate limit errors when managing large Asana projects

Implement exponential backoff retry logic with jitter. Use batch operations to reduce API calls. Cache frequently accessed data. Monitor rate limit headers and adjust request frequency accordingly.

Asana workspace or project access denied errors

Verify API token has access to the workspace and projects. Check workspace permissions and project sharing settings. Ensure OAuth scopes include required workspace and project access permissions.

Asana MCP server connection timeouts or network errors

Check network connectivity and firewall settings. Verify Asana API endpoints are accessible. Increase request timeout values. Implement connection pooling and retry mechanisms with exponential backoff.

Asana MCP server authentication errors with personal access tokens

Verify token is valid and not expired. Check token scopes match required permissions. Ensure token format is correct (Bearer token in Authorization header). For OAuth integrations, verify token refresh logic is working correctly.

Rate limit errors when managing large Asana projects

Implement exponential backoff retry logic with jitter. Use batch operations to reduce API calls. Cache frequently accessed data. Monitor rate limit headers and adjust request frequency accordingly.

Asana workspace or project access denied errors

Verify API token has access to the workspace and projects. Check workspace permissions and project sharing settings. Ensure OAuth scopes include required workspace and project access permissions.

Asana MCP server connection timeouts or network errors

Check network connectivity and firewall settings. Verify Asana API endpoints are accessible. Increase request timeout values. Implement connection pooling and retry mechanisms with exponential backoff.

Source citations

Add this badge to your README

Show that Asana MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/asana-mcp-server.svg)](https://heyclau.de/entry/mcp/asana-mcp-server)

How it compares

Asana MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Source provenance).

Field

Interact with Asana workspaces to manage projects and tasks

Open dossier

Task management and project tracking with ClickUp integration

Open dossier

Integrate with Linear's issue tracking and project management system

Open dossier

Manage monday.com boards, items, and CRM activities

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage verifiedPackage verifiedPackage verifiedPackage verified
Source provenanceDiffersSource-backedNo submission linkNo submission linkNo submission link
Submitter
Install riskLow riskLow riskLow riskLow risk
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
BrandAsana logoAsanaClickUp logoClickUpLinear logoLinearMonday.com logoMonday.com
Categorymcpmcpmcpmcp
Sourcefirst-partyfirst-partyfirst-partyfirst-party
AuthorAsanahauptsacheNetLinearMonday.com
Added2025-09-182025-09-182025-09-182025-09-18
Platforms
Claude CodeCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesUse a least-privilege Asana token and test task or project writes in a non-critical workspace before connecting production workflows.Scope the ClickUp API key to the intended team and review task, status, or project mutations before using it on active workspaces.Scope the Linear token to the intended workspace and review issue or project writes before changing active roadmaps.Scope the Monday API token to intended boards and review item, CRM, or automation changes before using live workflows.
Privacy notesAsana task text, project metadata, comments, assignees, due dates, and workspace details may be sent through model context.Tasks, comments, custom fields, assignees, due dates, and workspace metadata may be exposed through tool calls.Issue text, comments, assignees, labels, project context, customer references, and workspace metadata may be sent through tool calls.Board items, CRM records, comments, custom fields, users, and workspace automation metadata may be sent through tool calls.
Prerequisites
  • OAuth 2.0 authentication (required for MCP server via SSE transport)
  • Asana account with access to at least one workspace
  • Workspace membership with Member role or higher (Guest role insufficient for task creation)
  • Internet connection for accessing Asana API (https://app.asana.com)
  • ClickUp account with workspace access
  • ClickUp Personal API Token from https://app.clickup.com/settings/apps
  • ClickUp Team ID (found in ClickUp workspace settings)
  • Node.js and npm/npx available for running the @hauptsache.net/clickup-mcp package
  • Linear workspace account (Member or Admin role required, not Guest)
  • OAuth credentials or Personal API Key (generate from Linear Security & access settings)
  • SSE transport support (remote MCP server at https://mcp.linear.app/sse)
  • Internet connection (remote Linear API access required)
  • monday.com workspace account (Member role required, not Guest)
  • Personal V2 API token (generate from Developer Center or Administration tab) or OAuth credentials for hosted service
  • SSE transport support (remote MCP server at https://mcp.monday.com/sse or local npx installation)
  • Internet connection (remote monday.com API access required)
Install
claude mcp list && claude mcp status asana
claude mcp add clickup --env CLICKUP_API_KEY=YOUR_KEY --env CLICKUP_TEAM_ID=YOUR_TEAM_ID -- npx -y @hauptsache.net/clickup-mcp && claude mcp list
claude mcp list && claude mcp status linear
claude mcp list && claude mcp status monday
Config
{
  "mcpServers": {
    "asana": {
      "url": "https://mcp.asana.com/sse",
      "type": "sse"
    }
  }
}
{
  "mcpServers": {
    "clickup": {
      "env": {
        "CLICKUP_API_KEY": "${CLICKUP_API_KEY}",
        "CLICKUP_TEAM_ID": "${CLICKUP_TEAM_ID}"
      },
      "args": [
        "-y",
        "@hauptsache.net/clickup-mcp"
      ],
      "command": "npx",
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "linear": {
      "url": "https://mcp.linear.app/sse",
      "type": "sse"
    }
  }
}
{
  "mcpServers": {
    "monday": {
      "url": "https://mcp.monday.com/sse",
      "type": "sse"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.