Skip to main content
Back to the Asana MCP server

MCP Gateway · Claude

Asana icon

Connect Asana to Claude

Project leads spend Friday afternoons turning Asana into status updates. With Asana behind the Speakeasy MCP Gateway, Claude can read a project's past updates and post a new one, check how team goals are tracking, and turn meeting notes into assigned tasks. Each person only sees the servers their role can reach, and no client ID or secret is needed to connect.

Category
Project management
Tools
44
Authentication
OAuth
Claude
Web, desktop and mobile

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 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 Claude

    Add the gateway URL as a custom connector, then connect it from Customize > Connectors.

    On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.

    Each person opens Customize > Connectors and clicks Connect to sign in.

    On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.

  4. 04

    Sign in and use Asana from Claude

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

No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.

Use cases

What Claude users do with Asana

Write the weekly status update

Claude reads the project's earlier status updates and posts this week's, with a green, yellow or red color and a short note on blockers.

asana_get_project_statusesasana_create_project_status

Check how team goals are tracking

Ask which goals belong to your team, read each one's owner and latest status, and update the current metric value when a number comes in.

asana_get_goalsasana_get_goalasana_update_goal_metric

Turn meeting notes into tasks

Paste the notes from a meeting and Claude finds the right project, then creates a task for each action item with an owner and due date.

asana_typeahead_searchasana_create_task

Tools

44 tools

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

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

Anthropic inference hooks

Claude

On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.

Conversation import

Claude

Claude conversations can be imported through Anthropic's Compliance API for review after the fact.

  • Custom connectors need a Claude plan that supports them.
  • Budgets don't cover Claude web and desktop usage.

Questions

Frequently asked questions

Can Claude post Asana status updates for everyone?
Only for people whose role allows asana_create_project_status. Tools are allowed or denied per team and role at the gateway, so some teams can read Asana without writing to it.
Can Claude conversations that touch Asana be reviewed later?
Yes. Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
How do Claude users get Asana?
An admin adds Asana from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway URL as a custom connector, then connect it from Customize > Connectors. Each person then sees only the Asana tools their access allows.
Are Asana calls from Claude 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.