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:
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.
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.
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.
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):
addProject (add a task to a project, with optional section and position parameters)
removeProject (remove a task from a project)
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.
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.
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)
the MCP on Asana is really bad compare to Notion. On the new Asana we have “Knowledge” part that is great but why the MCP can access to it at all? It sounds crazy to me.
Thanks for bringing this to our attention, @Phil_Seeman!
To answer @SixteenLetters’s original question: Asana MCP does support task multi-homing. While there aren’t dedicated addProject or removeProject tools, the update_tasks tool supports updating a task’s project memberships. In practice, this means you can ask your LLM to add a task to another project or remove it from a project, and it will use the appropriate API functionality under the hood.
I’m not completely sure whether this capability was already available back in March when this thread was started, but I wanted to post an update since it has been supported for some time now.
Thanks as well for the feedback @François-Xavier! The Knowledge tab is one of Asana’s newer features, and we’re actively working on bringing support for it to the API, which will be the first step to exposing it through the MCP as well. I mentioned this in another thread discussing the Pages API. I’ve also logged your feedback with our Product team so they’re aware of the growing interest in exposing this functionality. While I can’t share a timeline just yet, I can say that the API work is already being scoped, so we’re making progress in that direction.
@Dominik_Brdak thanks for the reply. Wondering if that update_tasks tool supports adding a project to a portfolio as well, or if that has been discussed as additional functionality for the MCP.
At the moment, our MCP doesn’t support adding/removing projects to/ from portfolios. This was also raised in another thread: Let Claude create portfolios and add projects to them in Asana . Our PM acknowledged this feature request, so while I can’t share a clear timeline yet, the team will definitely consider it in the future.
Agreed @François-Xavier - as someone who is eager and actively getting more context into the Work Graph, the fact that Knowledge objects are inaccessible to anything programmatic is a non-starter for adoption.