Claude can write, plan, and research. But out of the box, it can’t touch the apps where your actual work lives — your CRM, your spreadsheets, your project boards. Zapier MCP changes that in about ten minutes, and it’s the single biggest unlock we’ve set up so far: one connection that puts over 9,000 apps within Claude’s reach.
In this guide, we’ll walk through the exact setup process, show you how to scope permissions so Claude can only do what you allow, and flag the task-quota detail that catches most people off guard.
What Is Zapier MCP?
MCP (Model Context Protocol) is the open standard that lets Claude connect to external tools. Most MCP connectors link Claude to a single app — we’ve covered Gmail, Google Calendar, Notion, and others in our MCP Directory.
Zapier MCP is different: instead of one app, it’s a bridge to Zapier’s entire integration network. That means Claude can search your CRM, add rows to Google Sheets, post to Slack, create Trello cards, or log invoices — through a single connection. You choose exactly which apps and which actions Claude gets access to.
For creators and small businesses, this is the connector that turns Claude from an assistant that talks about work into one that does it.
What You’ll Need
- A Zapier account — the free plan works, no credit card needed for MCP itself
- A Claude plan with remote MCP support (Pro or above) — and if you’re on a Team/organization account, you’ll need to be the organization owner to add a new server
- Ten minutes
Step 1: Create Your Zapier MCP Server
Head to mcp.zapier.com and sign in with your Zapier account. Click + New MCP Server.
You’ll be asked to choose your MCP client — select Claude. Give the server a name you’ll recognize later (something like “Claude Main” works fine).
One thing worth knowing upfront: each AI client needs its own MCP server. If you later want to connect ChatGPT or another tool, you’ll create a separate server for it rather than reusing this one.
Step 2: Add Your First Tools
Inside your new server, click + Add tool. Type the name of an app — say, Google Sheets — and pick it from the list.
Zapier will then show you the available actions for that app: things like “Create Spreadsheet Row,” “Lookup Spreadsheet Row,” or “Update Row.” Here’s our strongest recommendation from testing MCP connectors all summer:
Only enable the actions you actually want Claude to perform. Don’t select everything by default. If you want Claude to draft emails but never send them, enable the draft action and skip the send action. This is the entire security model in one decision — take the extra thirty seconds.
When prompted, connect your app account (Google, Slack, whatever you chose) and click Add tool. Repeat for each app you want Claude to reach.
Step 3: Connect the Server to Claude
In the top menu bar of your MCP server page, open the Connect tab. In the MCP Client dropdown, select Claude.
Zapier displays the exact steps to add the server to Claude.ai — follow them, and when prompted, authenticate with your Zapier account via OAuth. No API keys to copy, no config files to edit.
Step 4: The Claude Desktop Gotcha
If you use Claude Desktop, here’s the detail that trips people up: Claude Desktop syncs its MCP configuration from Claude.ai. You must complete the web setup first — the connection then carries over automatically.
If your Zapier tools don’t appear in Claude Desktop after the web setup, close and reopen the app to force a sync. That fixes it in nearly every case.
Step 5: Test It
Open a new Claude conversation and try something simple tied to a tool you enabled:
- “Add a row to my content tracker sheet with today’s date and the title of my latest post”
- “What’s on my calendar tomorrow?”
- “Draft a Slack message to the team channel summarizing this week’s plan”
Claude will ask for permission the first time it uses a tool. Approve it, and watch it work.
The Pricing Detail Nobody Mentions
Zapier MCP is included on every Zapier plan, including the free one. But there’s a quota mechanic you should know before you build workflows around it: every successful tool call consumes two tasks from your Zapier plan — the same task bucket your Zaps use. Failed calls don’t count.
On the free plan (100 tasks/month at the time of writing), that’s roughly 50 Claude actions per month. Plenty for testing and light use; if Claude becomes your daily operations layer, you’ll want a paid Zapier tier. Check your usage anytime in your Zapier dashboard’s History tab — every action Claude takes is logged there, with the exact values used.
What We’d Use It For
The workflows that make the most sense for creators and small businesses:
- Content tracking: Claude drafts your post, then logs it to your editorial calendar in Sheets or Notion — one conversation, zero tab-switching
- Lead capture: paste an inquiry email and have Claude create the CRM contact and a follow-up task
- Reporting: pull numbers from Sheets, have Claude spot what changed, and write the summary
- Inbox triage: summarize and route messages to the right project board
Zapier MCP vs. Individual MCP Connectors
If you only need Claude to reach Gmail, the dedicated Gmail MCP is simpler and doesn’t touch a task quota. Same logic for Google Calendar. Zapier MCP earns its place when you need apps that don’t have their own connector — CRMs, project tools, invoicing software — or when you want one permission dashboard governing everything Claude can do across your stack.
Our take: run both. Native connectors for the big Google apps, Zapier MCP for everything else.
You Might Also Like
More guides to get Claude working inside your daily tools:
Related Posts
