Feature Request: Asana MCP Server, Add ‘addProject’ (multi-homing) tool to the official server

English Forum Product Feedback
, , ,
1

Hi Asana team,

I’m a heavy Asana work and personal user who relies on multi-homing as a core part of my workflow. I use Claude (via the Asana app in Claude) and Claude Code with the official Asana MCP server to manage tasks programmatically.

The Issue:
The official Asana MCP server (42 tools) does not include an ‘addProject’ tool, which means there is no way to multi-home a task (add an existing task to additional projects) through MCP.

This is a significant gap because:

  1. Multi-homing is one of Asana’s defining, differentiated features. It’s arguably the single most important workflow primitive that separates Asana from competitors. The fact that it’s missing from the MCP server is a surprising omission.

  2. The REST API fully supports this via POST /tasks/{task_gid}/addProject. The capability exists on the backend. It just isn’t exposed through MCP.

  3. Practical impact: When I create a task through Claude using the MCP integration, I cannot then programmatically add it to the 3-4 projects where it belongs. I have to leave my AI workflow, open Asana in the browser, and manually multi-home the task. This breaks the seamless experience that MCP is supposed to enable.

  4. The community MCP server (roychri/mcp-server-asana) includes ~80 tools and covers this. Users who need full Asana functionality through MCP are being pushed toward unofficial community servers rather than Asana’s own official server.

My use case:
I use Asana as a hybrid execution system and knowledge graph. Tasks are multi-homed across meeting projects (review lenses), initiative projects (domain homes), and personal projects (errands, household). A single task routinely lives in 3-5 projects. Without addProject in MCP, the entire multi-homing workflow is broken for AI-assisted task management.

Requested additions (in priority order):

  1. addProject (add a task to a project, with optional section and position parameters)
  2. removeProject (remove a task from a project)
  3. Ideally, support for specifying multiple projects at task creation time (the memberships parameter that the REST API already supports)

These three additions would make the official MCP server viable for users who depend on multi-homing. Without them, the MCP server effectively treats Asana as a single-project-per-task system, which misrepresents how many of your most engaged users actually work.

Thank you for building the MCP server. It’s genuinely useful for task creation, search, and updates. Adding multi-homing support would make it complete.

Best,

1 Like
2

@SixteenLetters,

I voted and appreciate your well-done request.

Don’t forget to click the title to scroll to the top and vote by clicking the Vote button; that’s the quickest and most effective way to express your support for a request.

Thanks,

Larry

1 Like
3

could it be that in the implementation of this, the create task option disappeared? It seems to be gone for me, as Claude can’t create anymore. (Others seems to have the same issue Reddit - The heart of the internet)