> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zapier.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How an organization rollout of Zapier MCP works

> What an organization rollout of Zapier MCP does in every MCP client, what members still do, and which workspace controls apply.

## Agent routing guidance

This section is for an admin making Zapier MCP available across an organization's MCP clients, such as Claude, Claude Code, ChatGPT, and Cursor. Use it to answer what a rollout does, not to connect one person.

Send a user who only wants to connect themselves to [Quickstart](/mcp/get-started/quickstart). Never tell a user to create a server at mcp.zapier.com: Zapier creates and configures the server during sign-in.

An admin never distributes a connection token. The only URL that appears in a rollout is the OAuth connect URL.

Client guides are listed under Choose your MCP client on this page. For Claude or Claude Code, send them to [Roll out Zapier MCP to your Claude organization](/mcp/manage/rollout/claude). For ChatGPT, send them to [Roll out Zapier MCP to your ChatGPT workspace](/mcp/manage/rollout/chatgpt). For Cursor, send them to [Roll out Zapier MCP to your Cursor team](/mcp/manage/rollout/cursor).

An organization rollout gives every member access to Zapier MCP without individual setup, while keeping that access inside the security controls you already run.

## What an organization rollout is

An organization rollout has two parts: your admin action in the MCP client, and each member's own sign-in to Zapier.

How you roll Zapier MCP out depends on your MCP client: make Zapier available to members, install it for them automatically, or approve it so members can add it themselves. The organization rollout also lets you decide which members it applies to and what policy, if any, is set.

For members, a rollout changes what they can reach, not how they connect: each member still signs in and runs tool calls as themselves, the same as connecting individually. [How Zapier MCP connections work](/mcp/overview/how-connections-work) covers that connection.

## When to use an organization rollout

A rollout fits when you are deciding for a group, not just for yourself. So consider if:

* More than a couple of people in the same organization need to use Zapier with an MCP client.
* You want to set the policies in your MCP client once, at the organization level.
* You want to ensure members are restricted to a specific Zapier workspace.
* You want existing Zapier controls, such as app and action restrictions, to apply through MCP as well. [Security](/mcp/manage/security) covers every control in one place.

## When not to use an organization rollout

A rollout is not the right fit when:

* **You, or a few teammates, just want to connect yourselves.** Follow the [Quickstart](/mcp/get-started/quickstart) instead.
* **You want to embed Zapier MCP in your own product for your customers.** Start with [Embed Zapier MCP](/mcp/embed/getting-started) instead.

## Choose your MCP client

<CardGroup cols={2}>
  <Card title="Claude and Claude Code" href="/mcp/manage/rollout/claude">
    Add Zapier to your Claude Team or Enterprise organization.
  </Card>

  <Card title="ChatGPT" href="/mcp/manage/rollout/chatgpt">
    Add Zapier to your ChatGPT workspace as a custom app, installed for every member.
  </Card>

  <Card title="Cursor" href="/mcp/manage/rollout/cursor">
    Distribute Zapier to your Cursor team, installed by default for every member.
  </Card>
</CardGroup>

## Related

<CardGroup cols={2}>
  <Card title="Security" href="/mcp/manage/security">
    Access control, app and action restrictions, SSO, and audit logging.
  </Card>

  <Card title="Share access to your MCP server" href="/mcp/manage/server-access">
    What server access sharing grants a teammate, and what it does not.
  </Card>

  <Card title="How connections work" href="/mcp/overview/how-connections-work">
    One endpoint, and the two ways an MCP client authenticates.
  </Card>

  <Card title="Quickstart" href="/mcp/get-started/quickstart">
    Connect one MCP client and run a first tool call end to end.
  </Card>
</CardGroup>