Skip to main content
Back to the Zapier MCP server

MCP Gateway · Codex

Zapier icon

Connect Zapier to Codex

Engineering teams use Zapier MCP to reach thousands of apps through actions configured on the Zapier side. Codex can retrieve the link to that configuration whenever the available actions need to change. With Zapier behind the Speakeasy gateway, every engineer authenticates with your IdP, each team gets the Zapier access its role needs, and calls are logged against a named person.

Category
Productivity
Tools
1
Codex
CLI and ChatGPT desktop app

Behind the MCP Gateway

Run Zapier MCP behind the MCP Gateway

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

Deploy on MCP Gateway

Before you start

What Zapier needs first

No admin needed; the Zapier account manager only if MCP is disabled does the Zapier side of the setup.

  • Zapier MCP is available on every Zapier plan.
  • If Zapier MCP is disabled, the Zapier account manager must enable it for the workspace.
  • You do not need an app connection to establish the MCP connection.
Full Zapier setup guide in the docs

Set up

Add Zapier to Codex in 4 steps

  1. 01

    Add Zapier from the catalog

    An admin finds Zapier 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.

    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 Zapier

    Give teams the mcp:connect scope on the Zapier server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Zapier 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 Zapier from Codex

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

    From then on, Zapier'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 Zapier

Check actions before an automation

Ask Codex for the Zapier configuration link at the start of a task and confirm that the actions it will rely on are present before it begins.

get_configuration_url

Hand off action changes to a teammate

When an action needs to be added or edited by whoever owns the Zapier setup, Codex produces the configuration URL to drop into a pull request or handoff note.

get_configuration_url

Remove an action after a refactor

Once your code no longer calls an app through Zapier, have Codex return the configuration page so you can delete the stale action and keep the setup tidy.

get_configuration_url

Tools

1 tool

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

get_configuration_url

Returns the URL where users can configure this MCP server - adding, editing, or removing actions. Provide this URL to users who want to customize their available 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 Zapier call is logged with the person and the client that made it.

Access by role

Gateway

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

Request and response blocking

Gateway

A risk policy scoped to Zapier 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

Is Zapier MCP available on our Zapier plan?
Zapier MCP is available on every Zapier plan. If it is disabled for your workspace, your Zapier account manager can enable it.
Are Codex cloud tasks covered by Speakeasy's hooks?
No. 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.
How do Codex users get Zapier?
An admin adds Zapier 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 Zapier tools their access allows.
Are Zapier calls from Codex logged?
Yes. Zapier 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

Zapier in other clients

AI everywhere.

Control here.