MCP Gateway · Claude Cowork
Connect Zapier to Claude Cowork
Longer Cowork tasks often cross several apps, and Zapier MCP is one way to reach them through actions configured on Zapier's side. Before a multi-step job starts, Cowork can return the page where those actions are set so a team can confirm they are ready. The server arrives through the organization's synced plugin, and Speakeasy's agent hooks allow or deny each prompt before the step runs.
- Category
- Productivity
- Tools
- 1
- Claude Cowork
- Cowork tab in Claude Desktop
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 Cowork 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. Claude Cowork connects to the Zapier server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use Zapier from Claude Cowork
The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with Zapier
Prepare actions before a long job
At the start of a multi-step task, Cowork returns the Zapier configuration URL so you can add every action the job will need before it runs.
Recover when a step is missing
If a step needs an action that isn't configured, Cowork can share the configuration page so you can add the action before the rest of the task continues.
Tidy actions after a project ends
When a recurring project wraps up, have Cowork pull up the configuration page and delete the actions that were only set up for it.
Tools
1 tool
Each Zapier tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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 Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
Does the device agent manage Zapier in Cowork?
What if Zapier MCP is turned off for our workspace?
How do Claude Cowork users get Zapier?
Are Zapier calls from Claude Cowork logged?
Connect more