MCP Gateway · Claude
Connect Zapier to Claude
For operations and marketing teams, Zapier is often the bridge between Claude and the rest of their apps. Which actions Claude can take is decided on a Zapier configuration page, and Claude can hand anyone that link on request. Once an Owner adds the Speakeasy gateway as a custom connector, each person connects from Customize > Connectors and only sees the servers their role can reach.
- Category
- Productivity
- Tools
- 1
- Claude
- Web, desktop and mobile
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 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
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.
- 04
Sign in and use Zapier from Claude
The first time Claude 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, 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 Zapier
Ask Claude where actions are managed
If you're not sure how Claude's Zapier actions are set up, ask for the configuration link and review the list of actions in one place.
Add an action for a new request
When a colleague asks Claude to do something in an app that isn't connected yet, Claude replies with the page where the matching Zapier action can be added.
Remove actions after a process changes
When a team stops using an app or a workflow, open the configuration page from Claude and delete the actions that no longer apply.
Tools
1 tool
Each Zapier tool can be allowed or denied per team and role at the MCP Gateway before Claude 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
The gateway covers every client the same way. The rest depends on what Claude 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. 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
Do Speakeasy budgets cover Zapier use in Claude?
Does every Zapier plan include Zapier MCP?
How do Claude users get Zapier?
Are Zapier calls from Claude logged?
Connect more