Zapier MCP Server: Connect 8,000 Apps to Claude

Zapier is the automation glue that connects 8,000+ apps in workflows called Zaps. The Zapier MCP server brings those workflows into Claude — so instead of logging into Zapier to manually trigger a Zap or check a workflow, you can say "run my new-lead notification Zap" directly in Claude and watch it execute.

What is Zapier?

Zapier is a no-code automation platform that connects over 8,000 apps through workflows called Zaps. Each Zap follows an if-this-then-that logic: a trigger event in one app causes one or more actions in another. For example, a new row in Google Sheets triggers an email via Gmail, which creates a task in Asana. Millions of businesses use Zapier to eliminate manual data entry, synchronize tools, and build workflows without writing code. It is the connective tissue of the modern business software stack.

What the Zapier MCP Server Does

The Zapier MCP server exposes your Zapier account's capabilities as tools that Claude can invoke during a conversation. Once installed, Claude can:

• Trigger Zaps — run any active Zap by name or ID, passing input data if the Zap requires it.
• List active Zaps — retrieve all your enabled workflows with their status and app connections.
• Search workflows — find Zaps by keyword, app name, or trigger type across your account.
• Check Zap run history — see recent runs, success/failure status, and error messages for any Zap.
• Expose Zapier actions as Claude tools — any Zapier action you configure becomes a callable tool in Claude's context.

Claude decides which Zapier tool to invoke based on your natural-language request, constructs the correct parameters, and formats the results in a readable way. For a deeper look at how Claude maps requests to tools, see our MCP resources vs tools vs prompts guide.

Prerequisites

Before installing the Zapier MCP server, make sure you have the following:

• Zapier account — free or paid; your plan determines which Zaps and premium apps are available.
• Zapier API key — go to zapier.com/l/mcp to generate your MCP-specific API key. This is separate from general Zapier API keys.
• Node.js 18 or higher — check with node --version in your terminal. Download from nodejs.org if needed.
• Claude Desktop — the MCP server connects via Claude Desktop's MCP integration.

How to Install the Zapier MCP Server

1. Get your Zapier API key. Visit zapier.com/l/mcp and follow the prompts to generate an MCP API key for your account. Copy the key — you will need it in the next step.
2. Open your Claude Desktop config file. This file is called claude_desktop_config.json. On macOS it lives at ~/Library/Application Support/Claude/claude_desktop_config.json; on Windows it is at %APPDATA%\Claude\claude_desktop_config.json. See our full claude_desktop_config.json guide for details on where to find and edit this file.
3. Add the Zapier server block. Paste the configuration shown below into the mcpServers object, replacing the placeholder with your actual API key.
4. Save the file and restart Claude Desktop. The Zapier server will appear in Claude's tool list within a few seconds of launch, and your Zaps will be ready to trigger.

The Config JSON

Add this block to your claude_desktop_config.json. The npx command pulls the latest server version automatically — no manual installation required.

{
  "mcpServers": {
    "zapier": {
      "command": "npx",
      "args": ["-y", "@zapier/mcp-server"],
      "env": {
        "ZAPIER_MCP_API_KEY": "your_zapier_api_key_here"
      }
    }
  }
}

If you are new to editing this file, our claude_desktop_config.json guide walks through every step. For guidance on keeping your API key secure, see our MCP security and trust levels article.

Real Use Cases

Once the server is connected, these are the kinds of requests Claude can handle immediately:

1. "Run my new customer welcome Zap." Claude identifies the matching Zap by name, triggers it, and confirms the run was queued — no Zapier dashboard login required.
2. "What Zaps ran in the last hour?" Claude queries your Zap run history, lists every workflow that executed in the past 60 minutes, and flags any that failed with the associated error message.
3. "Trigger my Slack notification Zap with this message: 'Deployment complete — v2.4.1 is live.'" Claude passes the message as input to the Zap, which fires the Slack notification without you touching Zapier or Slack directly.
4. "List all my active Zaps." Claude returns a formatted list of every enabled Zap in your account, including the trigger app, action app, and current on/off status.
5. "Which Zaps involve Google Sheets?" Claude searches your workflows for any Zap that uses Google Sheets as either a trigger or action, helping you audit your data pipeline at a glance.

Pros

• 8,000+ app coverage — if Zapier supports the app, Claude can interact with it through a Zap, covering virtually every SaaS tool in existence.
• No-code automation — you design workflows in Zapier's visual editor and Claude handles triggering them; no API knowledge needed.
• Zapier maintains integrations — when apps update their APIs, Zapier updates the connectors, so your MCP workflows stay functional without manual maintenance.
• Composable with other servers — combine the Zapier MCP server with a Stripe MCP server or HubSpot MCP server for multi-system automation in a single conversation.

Cons / Limitations

• Requires paid Zapier plan for premium Zaps — multi-step Zaps and integrations with premium apps like Salesforce require a paid Zapier subscription; free accounts are limited to single-step workflows.
• Limited customization — because the MCP server is Zapier's own product, its capabilities are bounded by what Zapier chooses to expose; you cannot extend it with custom logic the way you can with self-hosted servers.
• Rate limits apply — Zapier enforces task limits based on your plan. High-frequency triggering from Claude counts against your monthly task quota, so monitor usage if you automate frequently.