Zapier

Reach 9,000+ apps via Zapier.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Zapier connector does

The Zapier MCP server connects Claude, ChatGPT and any MCP-compatible agent to Zapier's library of 9,000+ app integrations. It is not a fixed connector: Zapier documents 14 always-present meta-tools that let an agent search Zapier's action catalogue, switch actions on, and run them — so the tool surface is assembled per user rather than published.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Zapier tools (14)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The OAuth grant draws no capability boundary. Zapier's RFC 9728 descriptor and its server card both declare exactly three scopes — openid, profile, email — which identify you and authorise nothing in particular. There is no scope between reading a calendar and sending an email, and no per-app choice at MCP consent. Whatever your Zapier account can reach, the grant covers.
  • You cannot know the tool surface from the listing. Anthropic's directory publishes no tool names and no permission label for this connector. The 14 meta-tools on this page come from Zapier's documentation, and the actions they reach depend on your own account.
  • Write confirmation is not enforced by the server. It is a rule file in Zapier's optional plugin repository. A client connecting directly to the endpoint gets no such instruction.
  • MCP-only restrictions do not exist. Zapier states app and action restrictions "cannot currently be set exclusively for Zapier MCP" and apply account-wide across all Zapier features.
  • Every successful call costs two tasks from your Zapier plan, and batches multiply — Zapier's own worked example puts "search and update 10 records" at 11 tool calls and 22 tasks. Hitting the plan limit stops tool calls until the billing period resets.
  • One server per named client. Zapier documents that each AI client needs its own MCP server, and you can hold only one server per named client.
  • Auto-provisioning ignores shared connections. It covers only app connections you own. Apps another Zapier user shared with you are not provisioned.
  • Editors cannot authenticate tools. On shared servers, an editor can add tools but the owner must authenticate them before they run.
  • No prompts or resources. Zapier's server card declares only a tools capability, so there is no prompts or resources surface to read. We could not confirm this over the wire because the endpoint is gated.
  • listChanged is declared false while the tool set changes by design. The server card sets it false, yet enable_zapier_action alters the tool list mid-session. Clients are not notified, which is why stale tool lists are Zapier's first documented troubleshooting case.
  • Data residency is US-only. Zapier states customer data is stored in AWS US-East 1 and that region-specific residency is not available unless separately agreed. Dedicated VPC and on-premises deployments are not offered.
  • We could not read tool schemas or annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here.

Frequently asked questions

How many tools does the Zapier MCP server have?

Fourteen static meta-tools, plus every action they can reach. Anthropic's directory lists zero tool names for Zapier, but Zapier documents 14 meta-tools that are always present. Those 14 are not the capability surface — two of them execute actions drawn from Zapier's library of 40,000+ actions across 9,000+ apps, so the reachable surface has no fixed size.

Why does the Zapier connector show no tools in Anthropic's directory?

Because the tool list is built per user, after sign-in. Zapier's server does not ship a fixed catalogue; it auto-provisions tools from the apps you already connected in your Zapier account, then lets the agent enable more mid-conversation. There is no single list Anthropic could publish, so the field is empty rather than stale.

Can the Zapier MCP connector send email or post to Slack?

Yes, if you have connected those apps to Zapier. Zapier documents execute_zapier_write_action as the tool that runs write actions, giving send, create and update as examples. Zapier's own docs name sending messages, creating tasks and updating records as the point of the product. Nothing in the tool name identifies which app it will reach.

What OAuth permissions does Zapier MCP request?

Three, and none of them limits anything. Zapier's RFC 9728 resource descriptor and its published server card both declare scopes_supported as openid, profile and email on 2026-08-22. Those are OpenID identity claims. No scope separates reading a spreadsheet from sending an email, because the boundary lives in your Zapier account rather than in the grant.

Does the agent ask before running a Zapier write action?

Only if your client is configured to. Zapier ships a lifecycle rule in its plugin repository stating reads are free and writes need confirmation, and instructing the agent to show the payload first. That is guidance loaded into the model's context, not a server-side gate. A client without the plugin never receives it.

How much does each Zapier MCP tool call cost?

Two tasks from your existing Zapier plan, at a fixed rate. Zapier documents that failed calls consume nothing and there is no separate MCP billing. Batch work multiplies: Zapier's own example puts adding five spreadsheet rows at five tool calls, or ten tasks. When the plan's task allowance runs out, tool calls stop until it resets.

Can I restrict which apps the Zapier connector can reach?

Yes, but not for MCP alone. Zapier states that MCP automatically enforces app and action restrictions set at the account level, and that permissions inside the apps themselves also apply. It also states those restrictions cannot currently be set exclusively for MCP, so any limit you configure applies account-wide across every Zapier feature.

Why do Zapier tools disappear from my AI client?

Your client is holding a cached tool list. Zapier's troubleshooting guide names this as the first cause and gives a per-client fix: refresh the connector in ChatGPT, restart Claude Desktop, reload the window in Cursor or VS Code. Zapier's server card declares listChanged as false, so it never pushes an update notification.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Zapier to work.

Connect Zapier once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio