asana-mcp-troubleshooting

asana-mcp-troubleshooting is a skill for Claude Code, Codex from Asana/cursor-marketplace-plugin. It costs 41 tokens per session (968 once invoked), scanned A, original, MIT.

A troubleshooting guide for connecting Asana to Cursor through MCP, a protocol that lets an AI coding tool use external services. Asana is a task and project management service.

In plain words
What is it for?
Checking Asana MCP credentials, diagnosing failed connections, and resolving setup or authentication issues.
Why use it?
It helps identify connection, authentication, and setup problems when Asana tools are missing or fail to work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Checking Asana MCP credentials, diagnosing failed connections, and resolving setup or authentication issues.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/asana/cursor-marketplace-plugin/asana-mcp-troubleshooting
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.

Any agent
npx skills add Asana/cursor-marketplace-plugin --skill asana-mcp-troubleshooting
Clone the repo
git clone --depth 1 https://github.com/Asana/cursor-marketplace-plugin

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for asana-mcp-troubleshooting

README.md
[![agentmods](https://agentmods.dev/badge/skills/asana/cursor-marketplace-plugin/asana-mcp-troubleshooting/github.svg)](https://agentmods.dev/skills/asana/cursor-marketplace-plugin/asana-mcp-troubleshooting)
Your own site
<a href="https://agentmods.dev/skills/asana/cursor-marketplace-plugin/asana-mcp-troubleshooting"><img src="https://agentmods.dev/badge/skills/asana/cursor-marketplace-plugin/asana-mcp-troubleshooting/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for asana-mcp-troubleshooting

Your own site · 80×15
<a href="https://agentmods.dev/skills/asana/cursor-marketplace-plugin/asana-mcp-troubleshooting"><img src="https://agentmods.dev/badge/skills/asana/cursor-marketplace-plugin/asana-mcp-troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 968 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.00968
Opus 5 $0.00020 $0.00484
Sonnet 5 $0.00008 $0.00194
Haiku 4.5 $0.00004 $0.00097

Measured 11d ago against content hash 9ecb598f1d0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

asana-mcp-troubleshooting scanned grade A with 1 finding 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 11d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -I https://mcp.asana.com/v2/mcp
skills/asana-mcp-troubleshooting/SKILL.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Asana MCP Troubleshooting

When to use this skill

Use this skill when:

  • The user says Asana tools are not available or not showing up in Cursor
  • The user reports an authentication error when using Asana tools
  • The user says "I'm stuck" or "it's not working" after installing the plugin
  • Any Asana MCP tool call fails with a connection or auth error

Diagnosis flow

Work through these checks in order. Stop at the first one that fails and resolve it before continuing.

Check 1: Are the environment variables set?

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

  1. Go to https://app.asana.com/0/my-apps
  2. Click Create new app and select "MCP App" as the app type
  3. Name it anything (e.g. "Cursor MCP")
  4. Under OAuth, add this exact redirect URI: cursor://anysphere.cursor-mcp/oauth/callback
  5. Copy your Client ID and Client Secret

Step 2: Set environment variables

Add these lines to your shell profile and save the file:

  • macOS/zsh → ~/.zshrc
  • Linux/bash → ~/.bashrc
  • Windows WSL → ~/.bashrc
export 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.


Check 2: Is the redirect URI registered correctly?

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:

Read the full file on GitHub · 122 lines

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.

  1. 11d ago First seen · 122 lines · 41 tokens per session scan A 9ecb598f1d0b

Subscribe to this mod's changes

asana-mcp-troubleshooting is a skill published in the GitHub repository Asana/cursor-marketplace-plugin (0 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 968 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systemic-issue-triage

Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.

Gentleman-Programming/gentle-ai · 57 tokens

triage-issue

Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…

atlassian/atlassian-mcp-server · 116 tokens

bug-triage

Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.

Donchitos/Claude-Code-Game-Studios · 59 tokens

investigation

Create an investigation ticket + live-doc for sustained root-cause work (retros, bug archaeology, regression hunts).

me2resh/apexyard · 26 tokens

browse-flows

Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.

microsoft/power-platform-skills · 31 tokens

operating-cadence

Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…

cbrock84/headcount · 95 tokens