I can add a task to an existing project/section, but I’m not able to move the task to a different section in the project?
1 Like
@John_Baldo - Hey! I’m not sure if anyone else is experiencing this issue with the new MCP, but when I try to update a task’s start_at or start_on field, the change does not seem to persist.
The update request appears to run, but the start date/time does not actually stick on the task afterward.
For context, updating due_on and due_at works without any issues, so the problem seems to be specific to the start date/time fields.
Has anyone been able to successfully update start dates through MCP? I’m trying to determine whether this is a bug, a current limitation, or something I may be doing incorrectly in my request.
Any confirmation or guidance would be greatly appreciated.
Thank you!
I have a similar case in which we’re paying for multiple Asana Workspaces and would love the ability to access more than 1 workspace from the same Claude chat session.
We set it up this way as we operate programs and staff within 2 different non-profits and prefer to keep team members, templates, data etc completely separate, though I am one of the Program Directors in charge of projects across multiple non-profits. In other words, I’m basically hired / appointed by two separate entities to develop and run programs for these separate non-profit entities. I opted to use 2 different workspaces rather than breaking one workspace up into portfolios etc.
Right now, I have to choose only 1 to work with in Claude.
I do understand the desire to keep things streamlined however so can appreciate why you did this. But that would be useful for us and others if it ever was possible again.
My main feature requests would be MCP access to the following API functionalities:
-
- Due Date Recurrence
(currently can read but not write/update - would be HUGE time saver)
- Due Date Recurrence
-
-
Stories (reading and writing comments)
-
Moving Tasks Between Sections
-
1 Like
Anyone else having trouble with the Claude connector today?
I ran into a few issues setting up the v2 MCP server with Codex in WSL2 on Windows, sharing in case it helps others.
Docs referenced: https://developers.asana.com/docs/integrating-with-asanas-mcp-server (as of 2026-03-22)
1) Env vars naming
The docs mention ASANA_CLIENT_ID / ASANA_CLIENT_SECRET, but these are not special names. Custom names work fine, e.g.:
ASANA_MY_WORKSPACE_NAME_CLIENT_ID
ASANA_MY_WORKSPACE_NAME_CLIENT_SECRET
Just make sure you reference them correctly in the npx command.
2) Codex config (WSL2)
This worked for me in ~/.codex/config.toml:
[mcp_servers.asana]
command = "bash"
args = [
"-lc",
'''npx -y mcp-remote@latest https://mcp.asana.com/v2/mcp 3334 \
--static-oauth-client-info "{\"client_id\":\"$ASANA_MY_WORKSPACE_NAME_CLIENT_ID\",\"client_secret\":\"$ASANA_MY_WORKSPACE_NAME_CLIENT_SECRET\"}" \
--resource https://mcp.asana.com/v2'''
]
The config from the docs didn’t work in my setup without adjustments. Somehow substitution of env variables didn’t work “out of the box”.
3) WSL2 networking
OAuth redirect requires Asana to hit http://localhost:3334, so Windows ↔ WSL2 port forwarding must work.
I had to enable:
[wsl2]
localhostForwarding=true
in C:\Users\<user>\.wslconfig, then run:
wsl --shutdown
Optional sanity check:
python3 -m http.server 3334
Opening http://localhost:3334 in a web browser on Windows should work.
4) Handshake failure / white page issue
Even after fixing networking, Codex was failing with:
MCP startup failed: handshaking with MCP server failed: connection closed
The browser would briefly open a blank page and close.
Fix: run the MCP command manually once in WSL2:
npx -y mcp-remote@latest https://mcp.asana.com/v2/mcp 3334 \
--static-oauth-client-info "{\"client_id\":\"$ASANA_MY_WORKSPACE_NAME_CLIENT_ID\",\"client_secret\":\"$ASANA_MY_WORKSPACE_NAME_CLIENT_SECRET\"}" \
--resource https://mcp.asana.com/v2 \
--debug
This completed the OAuth flow properly. After that, starting Codex worked and MCP initialized correctly.
3 Likes
Welcome and thank you for posting your solution; it’s so appreciated when people post solutions that can help others going forward ! 
2 Likes
If you get errors related to Asana MCP connection error after reopening codex app, just re-run:
npx -y mcp-remote@latest ``https://mcp.asana.com/v2/mcp`` 3334 --static-oauth-client-info “{“client_id”:“$ASANA_MY_WORKSPACE_NAME_CLIENT_ID”,“client_secret”:“$ASANA_MYWORKSPACE_NAME_CLIENT_SECRET”}” --resource https://mcp.asana.com/v2
before opening codex cli app.
Thanks to everyone who shared feedback and workarounds in this thread — this has been helpful as we worked on improving the setup experience.
We’ve updated our Connecting Coding Clients to Asana’s V2 Server guide with native OAuth setup instructions for Cursor (using Static OAuth) and VS Code (using its built-in client credentials flow). Both methods connect directly to the V2 server without requiring mcp-remote.
If you run into any issues with the updated steps, let us know here — we’re happy to help.
V2 tool consolidation breaks power-user and automation workflows — please offer a direct-action mode
I’m the Director of System Administration at a grocery chain operating 20+ retail locations across three data centers. My team runs Agile sprints entirely through Asana, and over the past year I’ve built deep AI-assisted workflows using Claude’s MCP integration with the V1 server. I want to share feedback on how the V2 tool consolidation is impacting users like me, because I don’t think our use case is well-represented in the “too many tools” feedback that drove this decision.
What my workflow looks like today with V1:
In a single conversational turn, I can ask Claude to create a parent task with 8-10 subtasks, set custom fields (Impact Level, Effort Level, Points) on each, establish dependency chains between them, assign them to team members, and add structured comments — all without leaving the conversation. This is not a novelty. This is how I run sprint planning for a 15-person systems team managing enterprise infrastructure (Fortinet security fabric migrations, Prometheus/VictoriaMetrics monitoring stacks, internal web portals, etc). A single sprint planning session might create 15-20 tasks with complex dependency relationships in under two minutes. This doesn’t even consider project management work!
What breaks with V2:
-
create_task_previewrequires per-task human confirmation. If I need to create a parent task with 10 subtasks, that’s 11 separate clicks. The entire point of AI-assisted project management is removing that friction. I’m not asking Claude to guess what tasks to create — I’m giving it explicit, detailed instructions and trusting it to execute. The preview/confirm pattern assumes I don’t know what I want, which is patronizing to power users. -
Dependency management tools (
set_task_dependencies,set_task_dependents) appear absent from V2. These are critical for any team doing real project management. My infrastructure projects have strict sequencing requirements — you can’t migrate a FortiGate security fabric root until you’ve completed the hardware refresh fleet-wide and upgraded firmware across all devices. Without dependency tools, I lose the ability to model these relationships programmatically. -
The consolidation penalizes structured, high-volume workflows. The V2 FAQ says large tool sets “cause models to struggle with tool selection.” That may be true for casual users asking vague questions, but it’s not true for users who have built explicit, tested workflows that call specific tools by name. Reducing the tool set to help models guess better actively harms users who don’t need the model to guess at all.
-
No programmatic subtask creation path. V1 allowed creating subtasks by passing
parentwithoutproject_id, which was essential for avoiding task duplication. The consolidated V2 tool set doesn’t clearly preserve this pattern, and the preview confirmation model makes batch subtask creation impractical.
What I’d like to see:
-
A direct-action mode or tool tier. Let power users and admin-controlled Team/Enterprise plans opt into the full tool set without preview gates. The confirmation pattern can remain the default for individual users. This is the same pattern Asana already uses for App Management — give admins the control to decide what’s appropriate for their organization.
-
Restore dependency management tools.
set_task_dependenciesandset_task_dependentsare not niche. They’re fundamental to project management. Dropping them signals that Asana sees MCP as a casual assistant feature rather than a real automation layer. -
Preserve the subtask creation pattern (
parentwithoutproject_id) without requiring confirmation clicks. -
Publish a tool roadmap. The V2 announcement says tools “may be added” based on feedback, but there’s no visibility into what’s planned. Users building workflows on top of MCP need to know what’s coming so they can plan migrations from V1 with confidence rather than hoping their critical tools come back.
I’ve invested thousands of hours building Asana-integrated automation — procurement portals, outage tracking systems, sprint management workflows — all routing through MCP. The V1 shutdown on May 11 gives me 5 weeks to either migrate to a diminished tool set or find an alternative. That’s not enough time, and the V2 tool set as it stands today doesn’t support the workflows I’ve built.
I’d appreciate hearing whether restoring direct-action task creation and dependency tools is on the near-term roadmap, or whether the V2 design philosophy is fundamentally moving away from supporting these use cases.
Thanks, Michael Kenning
2 Likes
Hi @Michael_Kenning,
I appreciate the detailed feedback. Thanks for trusting Asana with critical workflows. Apologies for the delayed reply. I was away recently and wanted to get the latest info before replying.
Over the last few weeks, we’ve made v2 tool enhancements which I believe will amount to a big improvement over our initial set and also address many of the issues you raised. More details soon on those exact changes!
But as you mentioned, right now we require the preview and confirmation experience in Claude and GPT when creating tasks and not all of the enhancements are available in that interface. I understand your frustration with that. We are working on improving on that right now to better serve all Claude and GPT users. I’m aiming to have an update about that by sometime next week. I appreciate your patience as we work through this.
It sounds like your already on this path, but I wanted to point out for others benefit that we still have the original v1 tools operational right now. If you have the ability to add a custom connector, you can connect at: https://mcp.asana.com/mcp
3 Likes
Thanks, John. I hope that those v2 enhancements are available before the v1 deprication deadline.
Where was this advice at the end of January when I posted the same question (albeit in a much shorter version)?! 
What’s the ETA on either V1 deprecation or V2 upgrade? Is it worth reverting to V1 for those of us who miss it?
Tried to connect to both https://mcp.asana.com/mcp and https://mcp.asana.com/v2/mcp with my client/secret
Claude code: auth worked with client_id and callbackPort, but claude code don’t send Authorization to /token as header
Error: The `client_id` and `client_secret` must authorize the app.
Cursor: already configured cursor://anysphere.cursor-mcp/oauth/callback
invalid_request: This app is not available to your Asana workspace or organization. If you are the app owner, adjust settings under "Manage Distribution" in the Asana developer console.
Hi @Allen_Yu1,
Thank for your message, The URL https://mcp.asana.com/mcp is not the correct V2 server address. The correct URL is https://mcp.asana.com/v2/mcp. Make sure you’re pointing at that endpoint.
You are mentioning two separate issues here, let me help you with each one.
Claude Code error
For the Claude Code setup specifically, we have a dedicated guide with the exact command to run: https://developers.asana.com/docs/connecting-mcp-clients-to-asanas-v2-server#claude-code
Before running it, work through the prerequisites section first — particularly step 3, which covers configuring the correct redirect URL for your app in the Asana developer console. Claude Code requires http://localhost:8080/callback. If that redirect URL isn’t set in your app settings, the auth flow will fail: https://developers.asana.com/docs/connecting-mcp-clients-to-asanas-v2-server#prerequisites
Cursor error
That “not available to your workspace” message is a distribution settings issue, not an auth issue. Your app exists but hasn’t been configured to allow access to your workspace yet.
Fix it by going to your app in the developer console, navigating to “Manage distribution,” and either selecting your specific workspace under “Specific workspaces” or switching to “Any workspace.” Full steps here: https://developers.asana.com/docs/integrating-with-asanas-mcp-server#this-app-is-not-available-to-your-workspace
Let us know if you run into anything else after those changes.
1 Like
@Michael_Kenning @JVD @Parker_Short
Thanks for your patience. As of a 10:30 AM PDT / 17:30 PM UTC today April 13, both UI and non-UI based tools for creating tasks should be available for Claude. This requires creating a new session to refresh tools. In the descriptions, we’ve given guidance to use create_tasks / text-based tool when creating multiple tasks or when the user asks to take action without preview / confirmation. In Claude, you can also explicitly disable the Interactive Preview task creation tool.
The create_tasks tool allows for creating tasks in a project or section or creating subtasks. The update_tasks tool allows for add / remove dependencies or sections via add / remove projects (we may re-visit this design, but I expect changing sections to be possible). Both tools allow bulk action which should be much faster than v1.
Currently:
- ChatGPT still requires UI widget for task creation
- Creating projects still uses UI widgets in both Claude and Chat
- Claude Code CLI is experiencing an issue where it attempts to use UI widgets in the terminal but fails
We are actively working on these things, and I expect to update again this week. In the meantime, I’d be happy to hear about any issues you run into when using create_tasks.
Hello @KevinBlanco , I am still having issues with the VS Code to Asana MCP connection.
I have followed the steps on the website you linked, but no where has VS Code asked for the ClientID or Secret.
Windows 11 25H2 (26200.8117)
VS Code 1.115.0
I have my app created in Asana with the credentials and the correct 2 Redirect URLs (including the trailing slash)
I’ve followed the steps to add a new server (MCP: Add Server), it is using https://mcp.asana.com/v2/mcp as the URL with type “http”.
When trying to start the server, a popup says: “The MCP Server Definition ‘asana’ wants to authenticate to Asana MCP.” with an “Allow” or “Cancel”. Clicking “Allow” just takes me to a standard Asana Oauth 2 page with “Cancel” or “Allow”.
Also, in the MCP output in VS Code I see this:
[warning] Error fetching resource metadata: Error: Protected Resource Metadata ‘resource’ property value “{{base MCP URL}}.com/v2” does not match expected value “{{base MCP URL}}.com/v2/mcp” for URL {{redacted because of post limits}}.com/.well-known/oauth-protected-resource/v2. Per RFC 9728, these MUST match. See {{link redacted because of new user post limits}}
I just don’t know what I am doing wrong 
Thank you for any help,
TJ
P.S. This stupid link limitation for new users is a PITA
To note, step 4 in the VS Code instructions (“Provide your client credentials”) never happened for me. This is also a brand new install of VS Code.
Any help? I tried resetting VSCode from scratch and nothing
Hi @TJ_Vendios,
Thank you for the detailed report and for your patience!
You are not doing anything wrong. The behavior you are seeing is the result of a recent change in how VS Code handles MCP OAuth discovery, which broke the step where VS Code prompts for your client ID and secret. We are investigating what is causing this and working toward a fix. In the meantime, we have updated our VS Code setup documentation to use mcp-remote, which works reliably right now.
Review the updated docs here: Connecting Coding Clients to Asana's V2 server
We will update this thread and the documentation once the native VS Code flow is restored. Apologies for the back and forth, and thank you for your valuable feedback.
1 Like