Skip to main content
Back to the Asana MCP server

MCP Gateway · Codex

Asana icon

Connect Asana to Codex

Reviewing a change is easier when you know the decisions behind the task. With Asana behind the Speakeasy MCP Gateway, Codex can read a task's comment and status history during review, file follow-up tasks in the right section, and add the people who need to hear about it. Agent hooks let Speakeasy allow or deny each Asana call before Codex runs it.

Category
Project management
Tools
44
Authentication
OAuth
Codex
CLI and ChatGPT desktop app

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

    Add the gateway as an MCP server, then log in.

    Run the first command with your organization gateway URL.

    Run the second command to sign in.

    codex mcp add 'speakeasy' \
      --url 'https://<organization host>/mcp/gateway/<organization slug>'
    codex mcp login 'speakeasy'
  4. 04

    Sign in and use Asana from Codex

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

To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.

Use cases

What Codex users do with Asana

Read the history behind a task

During review, Codex reads the task's activity, including comments and status changes, so it can tell whether the pull request matches what was agreed.

asana_get_stories_for_task

File follow-ups in the right section

When review turns up work for later, Codex finds the project's sections and creates each follow-up task in the right one instead of an unsorted list.

asana_get_project_sectionsasana_create_task

Loop in the people who need to know

Codex looks up the members of the owning team and adds them as followers on the task, so they get notified when it changes.

asana_get_team_usersasana_add_task_followers

Tools

44 tools

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

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

Prompt and tool-call blocking

Codex

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Codex runs it.

User attribution

Codex

An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.

Budgets

Codex

Spend limits can block Codex traffic once a budget is reached.

Device agent and MDM

Codex

The device agent keeps Codex's configuration in sync on managed laptops.

  • Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
  • The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.

Questions

Frequently asked questions

Does Codex cloud reach Asana through the same controls?
Codex cloud tasks and GitHub code review run off the device, so neither the plugin nor OpenTelemetry covers them. OpenAI's Compliance Logs record them after the fact.
Which Asana workspaces can Codex reach?
That depends on how the Asana MCP app is distributed: to specific workspaces or to any workspace. The person who creates the app must be a member of every workspace they add under Specific workspaces.
How do Codex users get Asana?
An admin adds Asana from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway as an MCP server, then log in. Each person then sees only the Asana tools their access allows.
Are Asana calls from Codex 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.