Knowledge BaseKnowledge Base

Setting Up the Asana Connector

A single Personal Access Token wires Asana into Wazzi as an MCP tool for your team's AI assistants.

April 25, 2026
5 min read

Path: Connectors → Asana → Configuration

What this page does

Some connectors only support a single instance per org — typically because the underlying API authenticates to your whole workspace at once. Asana is the canonical example: one Personal Access Token (PAT) covers your entire Asana workspace. There's no concept of "another Asana sub-account" — there's just one Asana on your side.

Single-instance setup is simpler than multi-instance: paste a key, test it, save it, done.

Before you start — what you'll need from Asana

You'll need an Asana Personal Access Token (PAT). To create one:

  1. Sign in to Asana as a user who has access to the projects and teams you want exposed via MCP.
  2. Go to My Profile Settings → Apps → Personal Access Tokens.
  3. Click + Create new token, give it a descriptive name like "Wazzi MCP", and copy the token.

Whose token should I use? The token inherits the scope of the user who created it. If you create it as a workspace admin, MCP tools will be able to see and modify everything in the workspace; if you create it as a regular member, they're limited to that member's projects. Best practice: create a dedicated service account in Asana, give it just the projects and teams Wazzi should see, and use its token. That way revoking access doesn't require rotating a real human's credentials.

What this connector unlocks for your team

Once configured, members with the right MCP permissions can ask Claude / ChatGPT / Cursor things like:

  • "List all open tasks in the Q4 Roadmap project."
  • "Create a task in Engineering Backlog assigned to Alex with a due date of Friday."
  • "Add a comment to task ABC saying we're blocked on legal review."
  • "Search for tasks mentioning 'launch' across all projects I'm a member of."

The exact set of available actions depends on which MCP toggles you've flipped on for the user's group — see Managing Permissions.

Steps

1. From the Connectors catalog, click Configure on the Asana tile.

You'll land on Asana's Configuration tab.

Asana connector Configuration tab

2. Paste your Asana API Key (Personal Access Token) into the API Key field.

3. Click Test Connection to verify the credentials.

Wazzi makes a low-impact call to Asana (typically GET /users/me) and shows a success or failure result. If it fails, double-check that:

  • The token isn't expired or revoked.
  • You copied the whole token (Asana PATs are long; partial paste is the usual culprit).
  • The user who created the token still has access to Asana itself.

4. Click Save Configuration.

Asana moves to the Active section of the catalog and the dot turns green:

Asana connector showing the saved active state

The Access tab — getting the MCP URL

Switch to the Access tab on the same edit page:

Asana connector Access tab showing the MCP URL

This is where you copy the MCP URL for the Asana connector. Distribute it to your team along with setup instructions for whichever AI tool they use:

The MCP URL is per-org, per-connector. It's the same URL for everyone in your org — but each user's access to it is gated by their Wazzi sign-in and their group permissions. Treat the URL as semi-sensitive — anyone with the URL can attempt to use it, but they'll fail to authenticate without a valid Wazzi session.

Troubleshooting

  • "Test Connection failed: 401 Unauthorized." Token is wrong, expired, or revoked. Generate a new PAT in Asana and update the field.
  • "Test Connection failed: 403 Forbidden." Token is valid but lacks scope. The Asana user who created the token doesn't have access to a workspace Wazzi tried to read. Either elevate that user or use a different token.
  • "Test Connection failed: timeout." Network blip or Asana is slow. Retry. If it persists, check the Asana status page.
  • My team can't see Asana tools in Claude even though the connector is Active. They don't have MCP → Asana permissions. See Managing Permissions.
  • The token works but I want to rotate it. Generate a new token in Asana, paste it in the field, click Test Connection, then Save Configuration. The old token can then be deleted in Asana — there's no downtime if you do it in that order.

Best practices

  • Use a dedicated service-account token, not a human's PAT. When the human leaves the company, you don't have to do an emergency rotation.
  • Document the rotation cadence. Asana PATs don't expire automatically — set yourself a quarterly reminder to rotate.
  • Restrict scope at the source. Limit the Asana user to only the projects and teams Wazzi should see, before creating the token. Defense in depth.
  • Never paste a token into a chat or doc. Type it directly into Wazzi or use a password manager that supports field-level filling.

Frequently asked questions

Can I configure two separate Asana workspaces?
Not from a single Asana connector — it's single-instance by design. If you have two distinct Asana workspaces, you'd need to choose one (typically the primary). Cross-workspace access is rare for most teams.

How does Wazzi store the API key?
Encrypted at rest with per-org keys. The key is never logged or returned through any API.

Will Asana usage from Wazzi count against my Asana rate limits?
Yes — every MCP call is a real Asana API call. Wazzi adds caching and batching where it can, but heavy AI workloads can occasionally bump into Asana's per-minute limits. Asana's Business and Enterprise tiers have higher caps.

What's next

Was this article helpful?