Skip to main content
Back to the Asana MCP server

MCP Gateway · Cursor

Asana icon

Connect Asana to Cursor

An Asana task often carries the mockups and acceptance notes for the code you're writing. With Asana behind the Speakeasy MCP Gateway, the Cursor agent can open those attachments in the editor, record which tasks block which, and mark work complete when you finish. Cursor hooks send each prompt and tool call to Speakeasy and fail closed if the check can't run.

Category
Project management
Tools
44
Authentication
OAuth
Cursor
Editor and terminal

Behind the MCP Gateway

Run Asana MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Asana call inspected and logged.

Deploy on MCP Gateway

Before you start

What Asana needs first

An Asana user with developer console access; an organization super admin if App management blocks the app does the Asana side of the setup.

  • You need an Asana account with access to the developer console.
  • You must be a member of every workspace you add under Specific workspaces.
  • On Enterprise+ or Legacy Enterprise with App management, a super admin must allow the MCP client first.

In Asana

  1. Open the developer console from Settings > Apps.
  2. Create an MCP app and save its Client ID and Client secret.
  3. Add the Speakeasy redirect URL under OAuth.
  4. Set distribution to specific workspaces or any workspace.
  5. If the app is blocked, have a super admin unblock it in the Admin console.
Full Asana setup guide in the docs

Set up

Add Asana to Cursor in 4 steps

  1. 01

    Add Asana from the catalog

    An admin finds Asana in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Asana uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Asana

    Give teams the mcp:connect scope on the Asana server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Asana to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Cursor

    Add the gateway to Cursor in one click from the Organization Gateway page.

    On the Organization Gateway page in Speakeasy, choose Cursor under Install.

    Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.

  4. 04

    Sign in and use Asana from Cursor

    The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Asana needs its own OAuth grant, so each person connects it once. Until they do, Asana calls fail while the rest of the gateway keeps working.

    From then on, Asana's tools appear in Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.

For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.

Use cases

What Cursor users do with Asana

Read the attachments on a task

Cursor lists the files attached to the task you're implementing and gets their view and download links, so the mockup or spec sits beside the component you're building.

asana_get_attachments_for_objectasana_get_attachment

Record which tasks block yours

When your change depends on another team's work, Cursor sets that task as a prerequisite and marks the tasks waiting on yours, so the dependency is visible in Asana.

asana_set_task_dependenciesasana_set_task_dependents

Close the task from the editor

Once the feature works, Cursor reads the task's current state and updates it to complete, with notes and custom fields filled in for the person who reviews it.

asana_get_taskasana_update_task

Tools

44 tools

Each Asana tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.

asana_get_allocations

List allocations filtered by either workspace + assignee or parent (project). Returns allocation details including start/end dates, effort (hours or percentage), and associated projects or portfolios. Use for capacity planning and resource management.

asana_get_attachment

Get detailed attachment data including name, resource type, download_url, view_url, and parent. Returns complete attachment information needed for accessing attached files.

asana_get_attachments_for_object

List all attachments for a project, project brief, or task. Returns attachment names, IDs, and URLs (download_url, permanent_url, view_url). Use for accessing files attached to Asana objects. Supports pagination for objects with many attachments.

asana_get_goals

List goals filtered by context (portfolio, project, task, workspace, or team). One context required. Returns goal names, IDs. Use for goal overview or reporting.

asana_get_goal

Get detailed goal data including name, owner, current_status_update, and due_on. Use after finding goal ID via typeahead. Returns complete goal configuration needed for goal operations.

asana_create_goal

Create a new goal. REQUIRES name, time_period, and either workspace or team. Use to establish objectives and key results. Returns created goal details with ID. Supports start/due dates and goal ownership assignment.

See all 44 tools

Control

What Speakeasy can see and stop in Cursor

The gateway covers every client the same way. The rest depends on what Cursor exposes to Speakeasy.

Tool logs

Gateway

Every Asana call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Asana tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Asana can reject a tool request before it reaches the server, or withhold a result from Cursor. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Cursor

Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.

User attribution

Cursor

Every Cursor hook event carries the user's email.

Budgets

Cursor

Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.

Device agent and MDM

Cursor

The device agent installs the marketplace and plugins and reapplies them every minute.

  • Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
  • After a plugin update, members run Developer: Reload Window.

Questions

Frequently asked questions

Who has to set up Asana before Cursor can use it?
An Asana user with developer console access creates an MCP app, saves its Client ID and secret, and adds the Speakeasy redirect URL. If your Enterprise+ or Legacy Enterprise organization uses App management, a super admin must allow the MCP client first.
Does every Cursor event show who made the Asana change?
Yes. Every Cursor hook event carries the user's email, so prompts and tool calls are tied to a named person.
How do Cursor users get Asana?
An admin adds Asana from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the Asana tools their access allows.
Are Asana calls from Cursor logged?
Yes. Asana calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Asana in other clients

AI everywhere.

Control here.