Skip to content

smartworldarafath/Google_Antigravity_Plugins / plugins/asana/skills/asana-setup

asana-setup

Verified

Set up the Asana V2 MCP server connection (one-time OAuth app + claude mcp add)

The user wants to connect Google Antigravity 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)

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

Note: localhost is correct — Google Antigravity 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

  1. On first use, Google Antigravity opens your browser for Asana consent — approve it.
  2. Run /mcp and confirm asana shows as connected.
  3. 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).

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall