MCP Gateway · Claude Code
Connect Zapier to Claude Code
Zapier MCP links an agent to thousands of apps and actions, and the actions it exposes are chosen on a Zapier configuration page. When a terminal task needs an action that isn't set up yet, Claude Code can point you straight to that page. Speakeasy's gateway signs each developer in through your identity provider, and agent hooks check every prompt and tool call before Claude Code runs it.
- Category
- Productivity
- Tools
- 1
- Claude Code
- CLI
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.
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.
Set up
Add Zapier to Claude Code in 4 steps
- 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.
- 02
Choose who can use Zapier
Give teams the
mcp:connectscope 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. - 03
Connect Claude Code
Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.
Run the command below with your organization gateway URL.
Open
/mcpin Claude Code and choose Authenticate to sign in.claude mcp add --transport http --scope user \ 'speakeasy' \ 'https://<organization host>/mcp/gateway/<organization slug>' - 04
Sign in and use Zapier from Claude Code
The first time Claude Code 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 Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.
Use cases
What Claude Code users do with Zapier
Add a missing action mid-task
When Claude Code needs a Zapier action the server doesn't expose yet, it returns the configuration URL so you can add that action and pick the task back up.
Trim actions for a focused session
Before a long terminal session, open the configuration page and remove the actions this work won't touch, so Claude Code chooses from a shorter, relevant list.
Fix an action that behaves unexpectedly
If a Zapier action returns something other than what a script expects, ask Claude Code for the configuration link and edit how that action is set up.
Tools
1 tool
Each Zapier tool can be allowed or denied per team and role at the MCP Gateway before Claude Code 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 Claude Code
The gateway covers every client the same way. The rest depends on what Claude Code 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 Claude Code. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Claude Code
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.
User attribution
Claude Code
Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.
Budgets
Claude Code
Spend limits can block Claude Code traffic once a budget is reached.
Device agent and MDM
Claude Code
The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.
Anthropic inference hooks
Claude Code
On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).
- Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
- Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.
Questions
Frequently asked questions
Do I need a Zapier app connection before Claude Code can connect?
Can I block Claude Code from using Zapier on some teams?
How do Claude Code users get Zapier?
Are Zapier calls from Claude Code logged?
Connect more