A setup command for connecting Claude Code to Asana's V2 MCP server, which lets an AI coding tool communicate with Asana. It guides you through creating an OAuth app and configuring the connection.

Use it to create the Asana OAuth app settings and add the Asana MCP server to Claude Code.

It explains the one-time credentials and redirect settings needed because this Asana connection requires your own OAuth client details. It also keeps the secret entry in your terminal.

asana-setup — Command by thevibeworks

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/thevibeworks/claude-code-docs/asana-setup

Clone the repo

git clone --depth 1 https://github.com/thevibeworks/claude-code-docs

Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 491 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00022	$0.00491
Opus 5	$0.00011	$0.00246
Sonnet 5	$0.00004	$0.00098
Haiku 4.5	$0.00002	$0.00049

Measured 2d ago against content hash 3d4d6079c76c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

asana-setup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to asana-setup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

content/github/claude-plugins-official/external_plugins/asana/commands/asana-setup.md · 43 lines

What it actually says

The user wants to connect Claude Code to Asana's V2 MCP server. Guide them through the one-time setup below. Do NOT run claude mcp add yourself — the --client-secret prompt needs a real terminal (a hidden TTY prompt), so the user must run it in their own terminal.

Their Asana OAuth Client ID (if provided): $1

Print these steps clearly, substituting the Client ID into the command if $1 is non-empty (otherwise leave the YOUR_CLIENT_ID placeholder):

Step 1 — Create an Asana OAuth app (one time)

Open the Asana developer console: https://app.asana.com/0/my-apps
Create a new app.
Under OAuth, add this exact Redirect URL:
```
http://localhost:8080/callback
```
Copy the Client ID and Client Secret.

Note: localhost is correct — Claude Code is a local client and catches the OAuth callback on your own machine. Asana's V2 server does not support Dynamic Client Registration, so you must bring your own client_id + client_secret.

Step 2 — Add the server (run this in YOUR terminal)

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

--client-secret (no value) triggers a hidden prompt; paste the Client Secret there. It is stored in your OS keychain.
The port in --callback-port must match the http://localhost:8080/callback redirect you registered.

Step 3 — Authenticate & verify

On first use, Claude Code opens your browser for Asana consent — approve it.
Run /mcp and confirm asana shows as connected.
Test it: ask "list my Asana workspaces".

After printing the steps, offer to help troubleshoot if they hit invalid_redirect_uri (redirect/port mismatch) or invalid_client (wrong id/secret).

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 43 lines · 22 tokens per session scan A 3d4d6079c76c

Subscribe to this mod's changes

asana-setup is a command published in the GitHub repository thevibeworks/claude-code-docs (38 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 491 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to asana-setup, differing in 0 lines, and is treated as a copy.

Security Writing and docs agent-sdk ai-agents anthropic claude claude-code documentation

asana-setup

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

What it actually says

Step 1 — Create an Asana OAuth app (one time)

Step 2 — Add the server (run this in YOUR terminal)

Step 3 — Authenticate & verify

What this file has done since we first saw it

Other commands, from other repositories

reconcile

review

audit

curate

create

from-spec