Asana

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.

/plugin install asana@claude-plugins-official