Asana MCP setup: V2, OAuth and project access

Before connecting, note a task that you can open in Asana: its title, project and assignee provide a useful first comparison. Prefer a dedicated test project without confidential content. The returned result should identify that exact task. A completed sign-in alone does not confirm that the connection can read your intended project.

Use V2 and register an MCP app

The current endpoint is https://mcp.asana.com/v2/mcp. It replaces the former V1 connection at /sse. Register an app of type “MCP app” in the Asana developer console. A standard API app or personal API token does not replace this OAuth setup. In the distribution settings, choose the workspace in which the app should be available.

Connect VS Code

Add both redirect URLs to the MCP app: http://127.0.0.1:33418/ and https://vscode.dev/redirect. Keep the trailing slash on the local URL. In VS Code, run “MCP: Add Server”, select HTTP and enter the V2 endpoint. For an existing .vscode/mcp.json, the server entry looks like this:

{
  "servers": {
    "asana": {
      "type": "http",
      "url": "https://mcp.asana.com/v2/mcp"
    }
  }
}

VS Code requests the registered app’s client ID and client secret during authentication because Asana does not offer dynamic client registration. Enter the secret in that flow, not in your project file, then complete browser authorisation. The VS Code guide explains the configuration formats and first start.

Bound the first request

1. Check the signed-in account and workspace. The same project name can appear in different workspaces.

2. Inspect the offered tools and choose a read operation. Request the prepared task within the explicitly named project.

3. Compare title, task identifier and assignee with the Asana interface. Follow a returned task link only after checking its domain and destination.

4. Record the date, project identifier and result. Repeat the request after restarting the client before including additional projects.

Diagnose the relevant layer

MCP acts with the authorising person’s permissions. Asking for a read does not remove write permissions from the account. Enable only the tools required for the first trial and use the access planner. An empty search response is not proof that data is absent: compare the same project scope in Asana first. The Asana registry search also lists declarations from different providers; it does not replace app registration.

Can I keep an old SSE configuration?

Set up the documented V2 connection. Replacing the URL alone is insufficient when the registered MCP app and its OAuth settings are missing.

Why does VS Code request a client ID?

Asana V2 requires an MCP app registered in advance. Use credentials from your own app and verify that its distribution settings include the intended workspace.

Is this connection automatically read-only?

No. Access follows the authorising account’s permissions. Check the account rights separately from the tools enabled in your client.

What belongs in a handover note?

Endpoint, workspace, project identifier, client and a repeatable read test. Keep client secrets and access tokens out of shared documentation.

Find more options in the team and project app directory.

Vendor documentation checked on 2 October 2026. The checks are a suggested procedure for your environment, not an authenticated account test.

1. Asana: MCP integration
   Show retrieval command

   curl -s https://developers.asana.com/docs/integrating-with-asanas-mcp-server
2. Asana: client setup
   Show retrieval command

   curl -s https://developers.asana.com/docs/connecting-mcp-clients-to-asanas-v2-server
3. VS Code: MCP configuration
   Show retrieval command

   curl -s https://code.visualstudio.com/docs/agent-customization/mcp-servers

All posts