Terminal
Terminal/Skill
Steps through diagnosing Asana MCP connection and login failures, from environment variables to redirect URI and server reachability.
By Asana
Works with
npx skills add asana/cursor-marketplace-plugin --skill asana-mcp-troubleshootingUse this skill when:
Work through these checks in order. Stop at the first one that fails and resolve it before continuing.
Run:
echo "CLIENT_ID: $ASANA_CLIENT_ID"
echo "CLIENT_SECRET: $ASANA_CLIENT_SECRET"
If either prints empty or the literal string $ASANA_CLIENT_ID: The env vars are not set. This is the most common cause of failure.
Tell the user:
The Asana plugin needs two environment variables to authenticate. You'll need to create an Asana OAuth app to get them.
Step 1: Create an Asana OAuth app
cursor://anysphere.cursor-mcp/oauth/callbackStep 2: Set environment variables
Add these lines to your shell profile and save the file:
~/.zshrc~/.bashrc~/.bashrcexport ASANA_CLIENT_ID="paste_your_client_id_here"
export ASANA_CLIENT_SECRET="paste_your_client_secret_here"
Step 3: Apply and restart
source ~/.zshrc # use ~/.bashrc if on bash
Then fully quit and restart Cursor.
After the user confirms they've done this, re-run Check 1.
If env vars are set but auth still fails, the redirect URI may be missing or wrong.
Tell the user to go back to https://app.asana.com/0/my-apps, open their app, and confirm this exact URI is listed under OAuth redirect URIs:
cursor://anysphere.cursor-mcp/oauth/callback
Common mistakes:
cursor://anysphere.cursor-mcp/oauth/callback/)cursor:// schemeEnvironment variables set in a shell profile are only available to processes started after that profile was sourced. If the user set the vars but didn't restart Cursor, the plugin won't see them.
Confirm the user fully quit Cursor (not just closed the window) and reopened it after running source.
On macOS, "quit" means Cmd+Q, not just closing the window.
If all of the above look correct, test whether the Asana MCP server is reachable:
curl -I https://mcp.asana.com/v2/mcp
A 4xx response (like 401 or 405) means the server is up and rejecting unauthenticated requests — that's expected and means connectivity is fine. A timeout or DNS failure means a network issue on the user's side.
If the plugin is installed but Asana tools don't appear in the agent's tool list:
If none of the above resolves the issue, direct the user to: