Remove forced preview confirmation for bulk subtask add via AI agent

English Forum Product Feedback
,
1

Feature Request: Add direct create_task and create_subtask tools to the Asana MCP Server (remove forced preview confirmation)

The current Asana MCP server exposes a create_task_preview tool that surfaces a UI confirmation button before any task is created. While this may make sense for single, user-initiated task creation, it makes bulk programmatic operations completely unusable.

Real-world impact: I asked an AI agent to build out a project with 15 tasks and ~96 subtasks from a pre-approved document. Every subtask required a separate UI confirmation click — 96+ clicks — defeating the entire purpose of agent-driven automation. The Asana REST API itself supports POST /tasks with a parent GID to create subtasks directly. The MCP server should expose this natively without a forced confirmation gate.

Requested fix:

  1. Add a create_task tool (no preview/confirmation required) that accepts name, notes, parent, project, due_on, assignee, and priority

  2. Add a create_subtask convenience tool that wraps the above with a required parent task GID

  3. Keep create_task_preview for use cases where confirmation is desired — but make it opt-in, not the only option

1 Like