Asana

Claude Code plugin shipped by Asana itself: a setup wizard for the OAuth connection to Asana's V2 MCP server.

Asana is a Claude Code plugin for connecting to Asana's own V2 MCP server (https://mcp.asana.com/v2/mcp), and like the Telegram, Discord, and iMessage plugins, it lives in Anthropic's officially curated anthropics/claude-plugins-official repository. Unlike those three messaging bridges, though, it doesn't come from Anthropic itself: the plugin's plugin.json names "Asana" as the author, meaning the company behind the work-management platform of the same name ships this integration directly. On its marketplace page at claude.com/plugins/asana, Anthropic's own count shows roughly 10,800 installs, though the plugin does not carry the "Anthropic verified" badge shown on entries such as the Telegram or Code Review plugin in the same directory.

Not a new MCP server, but a setup wizard

Unlike the messaging plugins, Asana doesn't add a new MCP server of its own and doesn't start any persistent background process. The external_plugins/asana folder in the repository just packages a README and a single slash command, /asana-setup, that walks through connecting to Asana's V2 MCP server – already documented separately in the "Asana MCP Server" catalog entry, with its own tools for creating, searching, and updating tasks. This plugin complements that entry with a guided setup experience tailored specifically to Claude Code, rather than replacing it.

Why setup needs its own wizard

Per the README, Asana shut down its original V1 beta server (https://mcp.asana.com/sse) in August 2026; the successor V2 server deliberately drops support for Dynamic Client Registration, so the old zero-config connection no longer works. Each user instead has to create their own OAuth app in the Asana developer console (app.asana.com/0/my-apps), register the redirect URL as exactly http://localhost:8080/callback, and hand the resulting client ID and client secret to Claude Code. The /asana-setup command automates exactly that multi-step process; alternatively it can be reproduced manually via claude mcp add --transport http --client-id YOUR_CLIENT_ID --client-secret --callback-port 8080 asana https://mcp.asana.com/v2/mcp. Per the documentation, the client secret is never passed as plain text – it's requested at a hidden prompt and stored encrypted in the OS keychain.

What you get once connected

Once the connection is live, Anthropic's marketplace page describes the resulting capabilities as creating and managing tasks, tracking project status, updating assignments, searching across workspaces via typeahead, and maintaining goals and sections – all driven by natural-language requests to Claude Code instead of the Asana web interface. The README's example prompts include creating a task in a specific project with an assignee, and asking for all tasks due this week.

Troubleshooting

The README dedicates a section to common errors: invalid_redirect_uri points to a redirect URL that doesn't match the registered one or the --callback-port used, invalid_client signals a wrong client ID or secret (fixable via claude mcp remove asana followed by re-adding it), and any Dynamic Client Registration errors simply confirm that V2 no longer offers an automatic flow for that.

Who the plugin is for

The wizard is useful for anyone already running Asana as their organization's work-management platform who wants to connect Claude Code to their own workspace without piecing together the OAuth setup by hand from separate Asana and Claude Code documentation. Both the plugin and the underlying server are free to use – it's only the connected Asana account's own plan that determines which data and features are actually reachable. That makes the /asana-setup route particularly well suited to teams setting up their first AI connection to an existing workspace without risking a misconfigured redirect port or client ID. Anyone who has already set up the underlying server manually doesn't need this plugin as well – it's technically the same V2 server, just with a guided rather than manual setup.

Installation instructions

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.

Step 1: 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.

bash
claude --version

Step 2: 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.

Step 3: 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:

Code
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.

Step 4: 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.

bash
claude mcp remove asana

Installation

/plugin install asana@claude-plugins-official
Free
Provider
Asana
License
Apache-2.0
Last reviewed
30.09.2026
GitHub stars
37,213

Categories

Compatible with

Claude Code