Asana
Asana's MCP server lets an agent read and act on your Asana Work Graph - finding tasks, creating and updating work, and summarizing project status through natural language.
The current server is V2, which requires OAuth 2.0 with a Client ID and Client Secret you register yourself. Asana does not support Dynamic Client Registration, so creating an Asana app is mandatory - you cannot connect with OAuth Connect alone.
See Overview for shared prerequisites and secret-handling guidance.
Connection Details
The V1 beta server (https://mcp.asana.com/sse) was deprecated and scheduled to shut down on 5 August 2026. Use the V2 URL for every configuration.
Prerequisites
- An Asana account with access to the workspace you want to connect.
- Permission to create an app in the Asana developer console for that account.
- The QuilrAI callback URL. Copy it from the MCP setup screen when you click Add MCP; production is normally
https://mcpgateway.quilrai.com/oauth/callback.
Create The Asana MCP App
This produces the Client ID and Client Secret that every V2 connection requires.
- Go to the Asana developer console at app.asana.com/0/my-apps and sign in.
- Click Create new app.
- Enter a name, for example
QuilrAI MCP. - Select MCP app as the app type. This matters - tokens issued to an MCP app only work with the MCP server.
- Click Create app, then copy the Client ID and Client secret shown.
The Client Secret is a credential. Never commit it to version control or paste it into a shared document. You can rotate it at any time from the OAuth tab of the app in the developer console.
Set The OAuth Redirect URL
In the app's left sidebar, click OAuth and add the QuilrAI callback URL exactly as QuilrAI displays it. A mismatch here is the most common cause of a failed authorization.
Configure Workspace Distribution
- In the left sidebar, click Manage distribution.
- Choose Specific workspaces or Any workspace.
- If you chose Specific workspaces, add at least one workspace. Leaving it empty causes a "This app is not available to your Asana workspace" error.
- Click Save changes.
Add Asana MCP To QuilrAI
- In QuilrAI, go to MCP Gateway and click Add MCP.
- Paste the Asana MCP endpoint URL:
https://mcp.asana.com/v2/mcp - Set Auth Mode to Auto-detect.
- Paste the Client ID and Client Secret from the Asana app.
- Click Create to start Asana's OAuth flow. A new screen opens and asks you to approve access.
- After authorization, QuilrAI connects and fetches the available tools.

The installed MCP card shows the QuilrAI gateway URL your agents point at, the original Asana MCP URL behind it, and the tool count fetched from Asana. Give this gateway URL - not https://mcp.asana.com/v2/mcp - to your MCP clients so traffic passes through the gateway's controls.
Keep In Mind
- No Dynamic Client Registration. Asana V2 always needs a provider-owned app with a manually entered Client ID and Client Secret.
- Use the MCP app type. Tokens from a standard Asana OAuth app do not work against the MCP server.
- One app per environment. Create a separate Asana app for each QuilrAI tenant or environment whose callback URL differs, so rotation and testing stay isolated.
- Access follows the authorizing user. Each user authorizes individually, and tools operate with that user's own Asana permissions.
- Restrict write tools before rollout. The MCP can create and update tasks and projects. Use Tools Management, Access Control, and Security Guardrails to limit which operations agents can reach.