Skip to main content
To use Zapier across your Claude Team or Enterprise organization, you must add it as a directory connector that every member can use in Claude chat, Claude Desktop, Claude Cowork, and Claude Code, on sessions signed in with a Claude account. Each member still needs to sign in to Zapier. Learn more about what an organization rollout of Zapier MCP is before using this tutorial.

​
Before you begin

To do an organization rollout of Zapier in your Claude organization, you need:
  • A Claude Team or Enterprise plan. Organization-level connectors are a Team and Enterprise feature.
  • The Owner or Primary Owner role in Claude. Only Owners and Primary Owners can enable a connector for the whole organization.
  • A Zapier Enterprise account. Enterprise provides the workspace-level app access controls, SSO, and audit logging this rollout relies on.
  • Every member provisioned into your organization and into a User Group with access to your workspace. Manage members and User Groups covers both requirements.

​
Add Zapier to your Claude organization

To add Zapier to your Claude organization, you must be an Owner or Primary Owner. You’ll set this up once for your whole organization.
1

Open organization settings

In Claude, open Organization settings.
2

Open connectors

Select Connectors. If Connectors is not listed, your role may not be Owner or Primary Owner.
3

Add a connector

Click Add +.
4

Open the full directory

Select All available.
5

Search for Zapier

Search for Zapier.
6

Select Zapier

Select Zapier in the results. Zapier’s connector details open.
7

Set tool permission restrictions

Under Tool permission restrictions, select Always allow, Needs approval, or Blocked for each tool.
8

Connect Zapier for your team

Click Connect for your team.
Tool permission restrictions apply organization-wide, including in Claude Code. Claude Code has its own permission modes that otherwise reduce or skip prompts, but an organization’s Needs approval setting overrides them: the tool still prompts on every call in every mode except dontAsk, where the call is denied instead of prompted. Blocked hides the tool from Claude entirely, so it never appears in the tool list.

​
How members connect

Enabling a connector does not grant access on its own: each member must connect to their Zapier account. In Claude Code on a Claude-account session, Zapier is listed in /mcp, collapsed under Show unused connectors until they first sign-in.

​
Put Zapier in Claude Code

Claude Code picks up the Zapier connector automatically when a member signs in with their Claude account, even through your identity provider. To confirm which credential a session uses, ask the person to run /status. A session that was already running when you added Zapier may require them to log out and back in with /login before Zapier appears in /mcp. Sessions that authenticate another way, such as an API key, Amazon Bedrock, or Google Cloud’s Agent Platform, do not inherit the connector. Learn how to set them up in Anthropic’s managed MCP documentation.

​
Connect as a member

Once Zapier MCP is rolled out in Claude, your members can sign in to Claude or Claude Code.
Never distribute a connection token or a connection-token URL. A connection token is long-lived, tied to one server, and grants whoever holds it the ability to run the server’s tools and read the data they return.
Replace WORKSPACE_NAME with the workspace your members select:

​
If members have already connected Zapier themselves

In Claude Code, members who ran claude mcp add previously will have a user-configured Zapier server in their settings, in addition to the inherited connector. Ask them to remove it with claude mcp remove Zapier-MCP, then sign in to the inherited connector. This way, the organization’s tool permission restrictions govern their session.

​
Verify the result

  • Check a member-level account. Sign in as a member and confirm Zapier is listed under Customize → Connectors and in /mcp.
  • As a member, run one call. Ask Claude to list the Zapier actions you have enabled. A completed call, whatever the reply contains, confirms your connection.

​
If Zapier does not appear

  • In Claude Code, log out and back in with /login, then check /mcp again. A session that was running when you added Zapier can miss the connector until you sign in again.
  • In Claude Code, run /status. If the session uses an API key, Amazon Bedrock, or a credential other than a Claude account login, it will not inherit the connector.
  • If /mcp reports Zapier as connected · session token rejected, run /login to sign in again, then reconnect Zapier from /mcp.
  • If the connector is signed in but its tools are missing, learn how to troubleshoot missing tools in an MCP client.

Roll out to your organization

The rollout model every client guide relies on, and the Zapier controls that govern it.

Claude

The member flow in Claude, including the authorization screen.

Claude Code

Connecting Claude Code directly, for anyone outside an organization rollout.

Security

Access control, app and action restrictions, SSO, and audit logging.
Last modified on September 25, 2026