# asana-setup

Walks through creating an Asana OAuth app and saving its client ID and secret as environment variables for Asana MCP.

Skill by Asana. Category: Security.

## Install

Project (for this project only):

```sh
npx skills add asana/cursor-marketplace-plugin --skill asana-setup
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

Global (for every project on this machine):

```sh
npx skills add asana/cursor-marketplace-plugin --skill asana-setup -g
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

## Tags

- Runs on your computer: It runs as a program on your machine, with your access.

## Security audits

- Gen Agent Trust Hub: Pass
- Socket: Pass
- Snyk: Fail

Installs: 1. Installs counted by skills.sh. [Open on skills.sh](https://www.skills.sh/asana/cursor-marketplace-plugin/asana-setup)

## Source

[Open the source](https://github.com/asana/cursor-marketplace-plugin/tree/HEAD/skills/asana-setup). Checked 2026-10-10. This summary may contain AI-generated text, so it can be wrong. Check the source before you rely on it.

## SKILL.md

````markdown
---
name: asana-setup
description: Detect and configure Asana MCP credentials. Run this before using any Asana tools.
---

# Asana MCP Setup

## Purpose

This skill ensures the Asana MCP server is correctly authenticated before any Asana tools are used.

The Asana MCP connection requires two credentials from a registered Asana OAuth app:
- `ASANA_CLIENT_ID`
- `ASANA_CLIENT_SECRET`

These must be set as environment variables in the user's shell profile.

## When to run this skill

Run this skill automatically if:
- The user asks to connect to Asana
- The user asks to use any Asana tool and the MCP connection fails
- The user says something like "set up Asana" or "configure Asana"

## Steps

### 1. Check if credentials are set

Check whether `ASANA_CLIENT_ID` and `ASANA_CLIENT_SECRET` are set in the user's environment. You can do this by running:

```bash
echo $ASANA_CLIENT_ID
echo $ASANA_CLIENT_SECRET
```

If both return non-empty values, skip to Step 4.

### 2. Guide the user to create an Asana OAuth app

If credentials are missing, tell the user:

> To connect Cursor to Asana, you need to register an OAuth app in Asana's developer console. Here's how:
>
> 1. Go to https://app.asana.com/0/my-apps
> 2. Click **Create new app** and select "MCP App" as the app type
> 3. Give it a name (e.g. "Cursor MCP")
> 4. Under **OAuth**, add this redirect URI: `cursor://anysphere.cursor-mcp/oauth/callback`
> 5. Copy your **Client ID** and **Client Secret**

### 3. Help the user set environment variables

Once the user has their credentials, instruct them to add these lines to their shell profile:

**For zsh (macOS default)** — add to `~/.zshrc`:

```bash
export ASANA_CLIENT_ID="your_client_id_here"
export ASANA_CLIENT_SECRET="your_client_secret_here"
```

**For bash** — add to `~/.bashrc` or `~/.bash_profile`:

```bash
export ASANA_CLIENT_ID="your_client_id_here"
export ASANA_CLIENT_SECRET="your_client_secret_here"
```

**For Windows (WSL)** — add to `~/.bashrc`:

```bash
export ASANA_CLIENT_ID="your_client_id_here"
export ASANA_CLIENT_SECRET="your_client_secret_here"
```

After saving, tell the user to run:

```bash
source ~/.zshrc   # or ~/.bashrc depending on their shell
```

Then restart Cursor.

### 4. Verify the connection

After credentials are set, confirm the MCP server is reachable by attempting to call an Asana tool (e.g. list workspaces). If it succeeds, confirm to the user that setup is complete.

If it fails, ask the user to verify:
- The redirect URI `cursor://anysphere.cursor-mcp/oauth/callback` is registered in their Asana app
- The Client ID and Client Secret were copied correctly (no extra spaces)
- They restarted Cursor after setting the environment variables
````

- Previous: [asana-mcp-troubleshooting](https://syn4pse.dev/terminal/asana-mcp-troubleshooting.md)
- Next: [asana-usage](https://syn4pse.dev/terminal/asana-usage.md)
- [Terminal](https://syn4pse.dev/terminal.md)
- [Suggest a change](mailto:terminal@syn4pse.dev?subject=Terminal%20suggestion)
