Set up the Asana plugin for Claude Code

This guide sets up the Asana plugin from Anthropic's official plugin repository for Claude Code. Before relying on it in production, review the full [README](https://github.com/anthropics/claude-plugins-official/blob/main/external_plugins/asana/README.md) in the repository. Because Asana's V2 MCP server doesn't support Dynamic Client Registration, every user needs their own OAuth app – there's no way around this step.

Check the prerequisites

You need a current version of Claude Code (check with claude --version) and an Asana account with access to the Asana developer console at app.asana.com/0/my-apps. Existing access to the old V1 beta server won't help, since it was shut down in August 2026.

Create an Asana OAuth app

Open the [Asana developer console](https://app.asana.com/0/my-apps) and create a new app. Under OAuth, register the redirect URL as exactly http://localhost:8080/callback – this is Claude Code's local OAuth callback and must exactly match the --callback-port you use later. Note down the resulting client ID and client secret.

Install and connect the plugin

Install the plugin through Claude Code's built-in marketplace with /plugin install asana@claude-plugins-official, then launch the bundled wizard with /asana-setup. It walks through the same steps you could also run manually in a terminal:

claude mcp add --transport http \
  --client-id YOUR_CLIENT_ID --client-secret \
  --callback-port 8080 \
  asana https://mcp.asana.com/v2/mcp

Replace YOUR_CLIENT_ID with the client ID from the Asana developer console. Because --client-secret is passed with no value, Claude Code prompts for it at a hidden prompt and stores it encrypted in the OS keychain instead of writing it to disk.

Test the connection

The next time the asana server is used, Claude Code opens your browser for Asana's consent screen. Once approved, running /mcp shows the asana server listed as connected. A simple first test is a request like "list my Asana workspaces" or "what Asana tasks are assigned to me?".

Troubleshooting

If you see invalid_redirect_uri, the redirect URL registered in the Asana app doesn't exactly match http://localhost:8080/callback, or the --callback-port you used differs from 8080. invalid_client means the client ID or secret is wrong; remove the connection with claude mcp remove asana and set it up again. Errors mentioning Dynamic Client Registration aren't a bug – they simply confirm that V2 no longer offers an automatic flow for that.