asana-project-ops

Asana Project Ops MCP Server provides a high-performance interface for managing Asana projects, tasks, sections, and subtasks directly from your AI workflow. It supports batch operations and direct section assignment to minimize API calls and improve throughput, with safeguards like continue_on_error and input validation. Use the enabled-tools and tool-category controls to tailor access to workspaces, projects, tasks, and batch operations, ensuring faster responses while maintaining security. The server is designed to operate within your AI application's context, letting you brainstorm, create, organize, and execute large task hierarchies without leaving your application.

To use the server, configure the MCP entry (for Claude Desktop or your local development) with the appropriate command, environment variable ASANA_ACCESS_TOKEN, and the Asana API access token. Once started, you can invoke batch creation of tasks, update sections, or manage nested subtasks using the provided tools. The enterprise-grade features include unified section operations, direct section assignment during task creation, and selective tool activation to optimize performance and minimize unnecessary API calls.

Prerequisites

• Node.js 18+ for development or Node.js 22+ for MCP Inspector
• An Asana account with an API access token

Environment setup

1. Create an Asana personal access token from the Asana Developer Console and set it as an environment variable:

export ASANA_ACCESS_TOKEN=your-asana-access-token

Installation Options Option A: Claude Desktop

1. Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "asana-project-ops": {
      "command": "npx",
      "args": ["-y", "@n0zer0d4y/asana-project-ops"],
      "env": {
        "ASANA_ACCESS_TOKEN": "your-asana-access-token"
      }
    }
  }
}

Option B: Local Development / Cursor

1. Build the project:

npm run build

2. Add to claude_desktop_config.json:

{
  "mcpServers": {
    "asana-project-ops-local": {
      "command": "node",
      "args": ["/path/to/your/project/dist/index.js"],
      "env": {
        "ASANA_ACCESS_TOKEN": "your-asana-access-token"
      }
    }
  }
}

Option C: Claude Code

claude mcp add asana-project-ops -e ASANA_ACCESS_TOKEN=<TOKEN> -- npx -y @n0zer0d4y/asana-project-ops

Prerequisites recap

• Node.js installed and accessible in your environment
• An Asana access token set in ASANA_ACCESS_TOKEN
• Optional: configure READ_ONLY_MODE or selective tool activation as needed

Tips and common issues:

• Ensure ASANA_ACCESS_TOKEN is set and not logged in outputs to prevent leaks.
• If you encounter rate-limit errors, fine-tune the enabled-tools or enabled-tool-categories to reduce concurrent requests.
• For local testing, use READ_ONLY_MODE=true to disable all mutating operations.
• When upgrading, re-build and restart the MCP server to pick up changes in batch handling or validation logic.
• Monitor batch operation results; continue_on_error helps prevent a single failure from halting large batches.
• If you see HTML content validation errors, review task descriptions to ensure compatibility with Asana’s allowed HTML tags.