[New] V2 MCP server now generally available!

English Forum Developers & API Changelog
43

Awesome, thank you! I am trying to get off of Monday.com, but I need MCP for VSCode to work! If this works, I would be ecstatic! I’ll report back and look forward to your update on the Oauth.

1 Like
44

Ok, I had to make a few modifications. I’ll list them here for anyone to reference. Maybe it has to do with me being on a Windows machine instead of a *nix system.

First, I had to modify your mcp.json file a bit:

{
  "servers": {
    "asana": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.asana.com/v2/mcp",
        "3334",
        "--static-oauth-client-info",
        "@C:\\PATH\\TO\\MY\\FILE\\asana_client.json",
        "--resource",
        "https://mcp.asana.com/v2"
      ]
    }
  }
}

There, I created a JSON file that was properly formatted. The issue, on Windows at least, was that VSCode was stripping the \" when passing to the mcp server, so when staticOAuthClientInfo = JSON.parse(staticOAuthClientInfoArg); ran on the mcp server (line 20781 of the mcp-remote chunk file), it complained about being an invalid JSON. Changing the line, while it leave my secret in an unencrypted .json file on my harddrive, is acceptable for the time being until you get the Oauth2 system working.

Oh, I also had to add http://localhost:3334/oauth/callback as a redirect URL in my MCP App in Asana.

45

@TJ_Vendios glad you worked through it and thanks for documenting those Windows specific steps, I have great news, the VS Code native authentication flow is working again and the original setup steps are back in our documentation and should work as documented.

If you ran into issues, try removing the existing Asana MCP authentication from VS Code by running the Authentication: Remove Dynamic Authentication Providers command. VS Code should prompt you for your client ID and secret as expected.

Thanks to everyone who reported the issue and shared details! it helped us move faster. Let us know here if you run into anything else.

1 Like
46

Taking a look at the new v2 updates, I see the following changes (thank you!)

  1. Asana:create_tasks — V2 now has a bulk task creation tool (1-50 tasks), supports project_id, section_id, parent, html_notes, custom_fields, followers, start_on, due_on, assignee
  2. Asana:add_comment — V2 now supports html_text (not just plain text like before - SUPER appreciate this), plus is_pinned
  3. Asana:update_tasks — V2 now supports add_projects/remove_projects, add_dependencies/remove_dependencies, add_dependents/remove_dependents, add_followers/remove_followers, parent, start_on
  4. Asana:search_tasks — V2 now has a proper advanced search tool (though this appears to be for Premium-tier and above).

Our organization now feels that we can properly move from the v1 server to v2 and maintain critical functionality. Again, we appreciate you getting these in place before the deadline. Please consider the impact your development cycle has on your customers and offer better visibility into the intended roadmap. The uncertainty with this change left a lot of us in the lurch and at least for my team, we seriously looked at alternative tools that were more aligned with our workflow.

2 Likes