Skip to main content
Back to the Asana MCP server

MCP Gateway · Claude Cowork

Asana icon

Connect Asana to Claude Cowork

Quarterly planning in Asana touches goals, projects and dozens of tasks at once. In Cowork, Claude can work through that as one longer task: set next quarter's goals, audit overdue work across every project and lay out a launch plan with its dependencies. Agent hooks send each prompt to Speakeasy before the step runs, and Cowork's OTLP export ties sessions to people.

Category
Project management
Tools
44
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

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 Claude Cowork 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. Claude Cowork connects to the Asana server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Asana from Claude Cowork

    The first time Claude Cowork 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 Claude Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Asana

Draft next quarter's goals

Cowork finds the right time period, checks each parent goal, and creates the new goals with owners and due dates, so the OKR tree is ready for review.

asana_get_time_periodsasana_get_parent_goals_for_goalasana_create_goal

Audit overdue work across projects

Cowork goes through every project in the workspace, searches for incomplete tasks past their due date, and writes up which teams are behind and by how much.

asana_get_projects_for_workspaceasana_search_tasksasana_get_project_task_counts

Lay out a launch plan

From a launch checklist, Cowork creates the tasks, sets which ones block each other, and adds the right followers, so the plan is ready for owners on Monday.

asana_create_taskasana_set_task_dependenciesasana_add_task_followers

Tools

44 tools

Each Asana tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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 Claude Cowork

The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Claude Cowork. MCP-scoped policies are enabled per organization.

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

How do Cowork sessions pick up a new Asana plugin?
Cowork reads the synced plugin repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Can Cowork use Asana on Claude Enterprise with prompt checks?
On Claude Enterprise, prompts can be checked before inference (beta). Agent hooks also send each prompt to Speakeasy, which allows or denies it before the step runs.
How do Claude Cowork users get Asana?
An admin adds Asana from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Asana tools their access allows.
Are Asana calls from Claude Cowork 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.