### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet - [x] This is a single feature request (not multiple features) ### Problem Statement # Asana MCP Limitation Report for Anthropic **Date:** 2025-11-01 **Reporter:** Alex Chapko (via Claude Code) **Project:** Sales Enablement Revamp - Asana Integration --- ## Executive Summary The Asana MCP has criti

[FEATURE] Asana MCP: Add Section Assignment and Task Reordering Support

Resolved 💬 3 comments Opened Nov 1, 2025 by alexchapko Closed Jan 10, 2026

Preflight Checklist

[x] I have searched existing requests and this feature hasn't been requested yet
[x] This is a single feature request (not multiple features)

Problem Statement

Asana MCP Limitation Report for Anthropic

Date: 2025-11-01
Reporter: Alex Chapko (via Claude Code)
Project: Sales Enablement Revamp - Asana Integration

---

Executive Summary

The Asana MCP has critical limitations that make it unreliable for project management workflows requiring structured task organization. Specifically, the MCP cannot:

Create tasks in specific sections (all tasks default to first section)
Reorder tasks within sections
Create sections programmatically

These limitations significantly reduce the MCP's utility for complex project management use cases.

---

Critical Limitation #1: Cannot Create Tasks in Specific Sections

Current Behavior

When using asana_create_task with a project_id parameter, all tasks are created in the first section of the project (alphabetically or by creation order), regardless of intent.

Expected Behavior

Tasks should be created in a specified section, similar to the Asana API's support for:

memberships parameter with section GID
Creating tasks directly within a section context

Impact

High: Makes bulk task creation unusable for multi-section projects
Workaround: Manual task moving or CSV import (defeats automation purpose)
User Experience: Frustrating - requires significant manual cleanup after MCP operations

Example Use Case

Creating 20+ tasks for "Phase 1.1 - First-Call Deck (Media)" section resulted in all tasks being placed in "Phase 0: Foundation & Team Assembly" section instead.

Reproduction Steps

1. Project has sections: ["Phase 0", "Phase 1.1", "Phase 1.2", "Phase 3", ...]
2. Call asana_create_task with project_id="XXX", name="Task A"
3. Task is created in "Phase 0" instead of intended section "Phase 1.1"

Recommended Fix

Add section or section_gid parameter to asana_create_task tool:

{
  "name": "asana_create_task",
  "parameters": {
    "project_id": "string",
    "section": "string (optional) - GID of section to create task in",
    "name": "string",
    // ... other parameters
  }
}

---

Critical Limitation #2: Cannot Reorder Tasks Within Sections

Current Behavior

No MCP tool exists to reorder tasks within a section. Tasks appear in creation order or random order within sections.

Expected Behavior

Ability to specify task position using:

insert_before parameter (task GID)
insert_after parameter (task GID)
Or bulk reorder operation

Impact

Medium-High: Tasks appear in non-logical order, reducing project clarity
Workaround: Manual drag/drop in Asana UI, or sort by due date (partial solution)
User Experience: Requires manual cleanup for proper task sequencing

Example Use Case

17 tasks in "Phase 1.1" section are out of order:

Foundation tasks (Week 1-2) appear at bottom
Design tasks (Week 7-9) appear in middle
Content tasks (Week 3-6) scattered throughout

Asana API Support

The Asana API supports task reordering via:

POST /tasks/{task-id}/addProject with insert_before or insert_after parameters
POST /sections/{section-id}/addTask with positioning parameters

Recommended Fix

Add new MCP tool: asana_reorder_task

{
  "name": "asana_reorder_task",
  "parameters": {
    "task_id": "string - Task to reorder",
    "section": "string - Section GID",
    "insert_before": "string (optional) - Task GID to insert before",
    "insert_after": "string (optional) - Task GID to insert after"
  }
}

---

Limitation #3: Cannot Create Sections Programmatically

Current Behavior

No MCP tool exists to create sections. Users must manually create sections in Asana UI before MCP can reference them.

Expected Behavior

Ability to create sections programmatically as part of project structure setup.

Impact

Low-Medium: Sections are typically created once, so this is less critical
Workaround: Manual section creation in Asana UI
User Experience: Breaks automation flow for complete project setup

Recommended Fix

Add new MCP tool: asana_create_section

{
  "name": "asana_create_section",
  "parameters": {
    "project_id": "string",
    "name": "string",
    "insert_before": "string (optional) - Section GID",
    "insert_after": "string (optional) - Section GID"
  }
}

---

Proposed Solution

Recommended MCP Enhancements

Priority 1: Add Section Parameter to create_task

Impact: High - Makes MCP usable for structured project management
Effort: Low - API already supports this via memberships parameter
User Benefit: Eliminates need for manual task moving

Priority 2: Add Task Reordering Tool

Impact: Medium - Improves task organization and clarity
Effort: Low - API already supports via insert_before/insert_after
User Benefit: Automated task sequencing, reduces manual cleanup

Priority 3: Add Section Creation Tool

Impact: Low - Sections created infrequently
Effort: Low - API already supports section creation
User Benefit: Complete project setup automation

---

Use Case Context

Project: Sales Enablement Revamp

Scale: 9 phases, 45+ tasks across multiple sections
Complexity: Multi-team coordination (Media WG, Non-Media WG)
Need: Structured task organization by phase and timeline
Current MCP Limitations: Required extensive manual cleanup and workarounds

Ideal Workflow:

Plan project structure in local PLAN.md file
Use MCP to create sections programmatically
Use MCP to create tasks in specific sections with proper ordering
Use MCP to track progress and generate reports

Actual Workflow with Current MCP:

Plan project structure in local PLAN.md file
Manually create sections in Asana UI ❌
Use MCP to create tasks → All go to wrong section ❌
Manually move all tasks to correct sections ❌
Manually reorder tasks within sections ❌
Use MCP to track progress and generate reports ✅

50% of workflow requires manual intervention due to MCP limitations.

---

Technical Details

Asana API Endpoints That Should Be Exposed

For Section Assignment:

Existing endpoint: POST /tasks with memberships parameter
Current MCP: Doesn't support memberships or section parameter

For Task Reordering:

Existing endpoint: POST /tasks/{task-id}/addProject
Parameters: insert_before, insert_after
Current MCP: No equivalent tool exists

For Section Creation:

Existing endpoint: POST /projects/{project-gid}/sections
Parameters: name, insert_before, insert_after
Current MCP: Cannot create sections (tried resource_subtype: section - returned error)

---

Suggested MCP Tool Specifications

1. Enhanced asana_create_task

interface CreateTaskParams {
  name: string;
  project_id?: string;
  section?: string; // NEW - Section GID to create task in
  parent?: string;
  workspace?: string;
  assignee?: string;
  due_on?: string;
  notes?: string;
  custom_fields?: Record<string, string>;
  // ... existing parameters
}

2. New asana_reorder_task

interface ReorderTaskParams {
  task_id: string; // Task to reorder
  project_id: string; // Project context
  section?: string; // Optional - Section GID
  insert_before?: string; // Optional - Task GID to insert before
  insert_after?: string; // Optional - Task GID to insert after
}

3. New asana_create_section

interface CreateSectionParams {
  project_id: string;
  name: string;
  insert_before?: string; // Optional - Section GID
  insert_after?: string; // Optional - Section GID
}

---

User Impact Assessment

Current State:

Asana MCP is useful for read operations and basic updates
Not suitable for project structure creation or bulk task management
Requires significant manual intervention for complex projects

With Proposed Enhancements:

Asana MCP becomes fully functional for project management workflows
90%+ automation possible for structured project setup
Users can plan locally, execute via MCP with minimal manual work

---

References

Asana API Documentation:

Tasks: https://developers.asana.com/reference/tasks
Add task to project: https://developers.asana.com/reference/addprojectfortask
Sections: https://developers.asana.com/reference/sections

Stack Overflow Examples:

Task reordering: https://stackoverflow.com/questions/12019085/getting-task-order-and-rearranging-in-asana-api
Move tasks between sections: https://stackoverflow.com/questions/25653982/move-asana-tasks-from-section-to-section-via-api

---

Priority: High - Significantly impacts MCP usability for project management use cases

Alternative Solutions

Current Workarounds in Use

For Task Creation

CSV Import: Claude generates CSV file with section assignments
User manually imports or creates tasks from CSV
Tasks created in correct sections from start

For Task Reordering

Sort by Due Date in Asana UI (gets tasks ~90% in order if due dates are sequential)
Manual drag/drop for fine-tuning

For Section Creation

Manual creation in Asana UI before MCP operations
Document section GIDs in project structure file for MCP reference

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗