# Asana setup for PopMCP

You paste a single Asana Personal Access Token, generated in the Asana developer console and shown only once.

- Auth: API credentials
- Setup time: 3 min
- API base URL: https://app.asana.com/api/1.0
- Credentials screen: https://app.asana.com/0/my-apps
- Provider docs: https://developers.asana.com/docs/personal-access-token

## Before you begin

- An Asana account on any plan: Personal, Starter, Advanced or Enterprise.
- The token acts as you. It reaches only the workspaces, teams and projects your own user can already see.
- On Enterprise, an admin may have restricted app and token creation.

## Get your credentials

### 1. Open the Asana developer console

Go to https://app.asana.com/0/my-apps. From inside Asana, click your profile photo, then My Settings → Apps → Manage Developer Apps.

Screen: https://app.asana.com/0/my-apps

### 2. Create a new personal access token

In the console sidebar click Personal access tokens, then click + Create new token.

Screen: https://app.asana.com/0/my-apps

### 3. Name the token and accept the API terms

Type `PopMCP` in Token name, tick I agree to the Asana API Terms, and click Create token.

Screen: https://app.asana.com/0/my-apps

### 4. Copy the token into PopMCP

Click Copy in the dialog, then paste the string into PopMCP's Personal Access Token field.

## Fields PopMCP asks for

- Personal Access Token (accessToken) [required]: Asana → your profile photo → My Settings → Apps → Developer console (or app.asana.com/0/my-apps) → Personal access tokens → Create new token. The token is shown only once. Stored encrypted.

## Verify

The Asana connection shows Connected in PopMCP and the Asana tools load. Listing your workspaces or the tasks assigned to you returns real Asana records.

## Troubleshooting

### You closed the dialog before copying the token

Cause: Asana reveals the full string once and never again.

Fix: Delete that entry on the Personal access tokens page and create a new token.

### 401 Unauthorized

Cause: The token was truncated on copy, or it has since been deleted from the developer console.

Fix: Open app.asana.com/0/my-apps, go to Personal access tokens, delete the old entry, create a fresh token and paste the whole string.

### 403 Forbidden on a specific project

Cause: The token inherits your access, and your user is not a member of that project or team.

Fix: Add your user to the project or team in Asana, or generate the token from a user that already has access.

### 429 Too Many Requests

Cause: The domain's per-minute quota was exceeded: 150 on free domains, 1,500 on paid, 60 for search.

Fix: Wait the number of seconds given in the Retry-After header before retrying. Early retries still count against the quota.

### The token works but sees none of your team's work

Cause: It was created from a personal Asana account that is not a member of the organisation's workspace.

Fix: Sign in to the Asana account that belongs to the organisation, switch to that workspace, and create the token again from app.asana.com/0/my-apps.

---

Source: https://www.docs.popmcp.com/docs/integrations/asana/