Asana

An Asana account with access to the developer console.
Membership in every Asana workspace you plan to select under Specific workspaces.
If your Enterprise+ or Legacy Enterprise organization uses App management, confirmation from an organization super admin that the V2 MCP client is allowed before users authorize it.
Access to your organization’s approved password manager.

Open the developer console

Select your profile photo in the top-right corner.
Select Settings.
Select Apps.
Select View developer console.

This opens the developer console, where you create the app. You can also open it directly at app.asana.com/0/my-apps.

Create the MCP app

Select Create new app.
Enter a recognizable app name, such as Speakeasy AI Control Plane.
Select MCP app as the app type.
Select Create app.
Copy the generated Client ID into your approved password manager.
Copy the generated Client secret into your approved password manager.

Configure the OAuth redirect

Select OAuth in the left sidebar.
Under Redirect URLs, select + Add redirect URL.
In Add redirect URL, enter this value in Redirect URL:
```
https://ai.speakeasy.com/mcp/remote_login_callback
```
Select Add.

Configure workspace distribution

Select Manage distribution in the left sidebar.

For an internal deployment limited to named workspaces:

Under Distribution method, select Specific workspaces.
Select + Add workspace.
Choose an intended workspace from the dropdown.
Select Add.
Repeat the workspace steps for every workspace whose users should connect.
Select Save changes.

To let users from any Asana workspace authorize the app:

Under Distribution method, select Any workspace.
Select Save changes.

If authorization says the app is explicitly blocked, an organization super admin must unblock it:

Return to Asana.
Select your profile photo.
Select Admin console.
Select Apps.
Select Manage apps.
Select Connected apps.
Select the associated MCP client app.
Select Unblock.

Add the server in Speakeasy

In the Speakeasy AI Control Plane sidebar, under MCP Gateway, select MCP.
Click Add new to open Add MCP server.
Choose From the catalog.
On the MCP Catalog page, find Asana using Search MCP servers….
Open the Asana entry and click Add.
In the Add to Project dialog, under Identity, select User Identity. The dialog may preselect No Identity.
Click Add to Project. If the dialog offers a Guardrails step, finish it or click Skip for now.

Asana needs a client registered by hand, so the result says to finish setup in Settings > Identity, and the server stays Disabled for now. This is expected. Click Finish setup on the server’s result to open its Settings.

Connect your credentials

In the server’s Settings, find the Identity section.

Select User Identity.
In Choose an identity provider, confirm the provider is https://app.asana.com. It may be badged Will be created. If no provider or a different one is selected, open the picker, search for app.asana.com in Search identity providers…, and choose it.
Under the provider, choose Manual.
Paste the Client ID from Create the MCP app into Client ID.
Paste the Client secret from Create the MCP app into Client secret. Asana requires it, even though the field shows “Optional”.
Open Advanced and enter default in Scope. Do not add other scopes; Asana rejects them with “Invalid scope(s) requested”.
Click Save.

This section does not show the redirect URI. Asana accepts the connection only if Configure the OAuth redirect registered https://ai.speakeasy.com/mcp/remote_login_callback.

Then turn the server on:

In Settings, open Danger Zone.
Under Server Availability, turn on Enable MCP server so it shows Enabled.

Each user sees Asana’s authorization prompt the first time they use the server.

This guide covers setup only. For anything beyond it — billing, tool behavior, limits — see Asana’s MCP documentation.