Skip to main content
mcpFirst-partyLow risk Safety Privacy
Zapier logo

Zapier MCP Server for Claude

Connect to nearly 8,000 apps through Zapier's automation platform

by Zapier·added 2025-09-18·
HarnessClaude CodeClaude Desktop

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://help.zapier.com/hc/en-us/articles/36265392843917, https://github.com/JSONbored/awesome-claude/blob/main/content/mcp/zapier-mcp-server.mdx
Brand
Zapier
Brand domain
zapier.com
Brand asset source
brandfetch
Package URL
/downloads/mcp/zapier-mcp-server.mcpb
Package SHA256
e43a859d567995a464e662a9b3726830434085c31bea4240635bf4ec61d66abd
Safety notes
Restrict the generated Zapier MCP URL and enabled actions because automations can write across many connected apps.
Privacy notes
Connected app data, workflow payloads, account metadata, and action inputs or outputs may be sent through model context.
Author
Zapier
Claim status
unclaimed
Last verified
2025-09-18

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as first-party.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    Package marked verified.

    Done
  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

1 minute

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

10 to clear

Platforms

2 listed

Difficulty

11/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

10 prerequisites to line up before setup. Have accounts and credentials ready first.

0/10 ready
Account & credentials3Network & hosting2General51 minute

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 1 risk area.

1 area
  • SafetyGeneralRestrict the generated Zapier MCP URL and enabled actions because automations can write across many connected apps.
  • PrivacyGeneralConnected app data, workflow payloads, account metadata, and action inputs or outputs may be sent through model context.

Safety notes

  • Restrict the generated Zapier MCP URL and enabled actions because automations can write across many connected apps.

Privacy notes

  • Connected app data, workflow payloads, account metadata, and action inputs or outputs may be sent through model context.

Prerequisites

  • Zapier account (free or paid plan)
  • Personal authentication token (generated at mcp.zapier.com)
  • Network access to mcp.zapier.com (HTTPS required, HTTP transport)
  • Understanding of Zapier Zaps/workflows (automation concepts)
  • Zapier Dashboard access (for token management and Zap configuration)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Understanding of Zapier API rate limits (1000 req/min, 10000 req/hour, 100000 req/day)
  • Understanding of task limits (daily/monthly quotas, plan-specific limits)
  • Understanding of Zap throttling (burst thresholds, delay steps)
  • Optional: Zapier plan upgrade (for higher task limits and features)

Schema details

Install type
package
Reading time
1 min
Difficulty score
11
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
e43a859d567995a464e662a9b3726830434085c31bea4240635bf4ec61d66abd
Collection metadata
Estimated setup
1 minute
Difficulty
beginner
Full copyable content
{
  "zapier": {
    "url": "https://mcp.zapier.com/YOUR_GENERATED_URL",
    "transport": "http"
  }
}

About this resource

Content

Access thousands of app integrations through Zapier's no-code automation platform. Trigger Zaps programmatically, access data from connected apps, read and write cross-application data, monitor Zap execution status, execute custom actions across apps, manage Zap configurations, view Zap History, and process webhooks—all through natural language commands. Supports personal authentication tokens, Zap-level permission controls, task usage monitoring, and comprehensive workflow automation across nearly 8,000 apps.

Features

  • Trigger Zaps (workflows) programmatically (on-demand execution)
  • Access data from connected apps (cross-app data retrieval)
  • Read and write cross-application data (data synchronization)
  • Monitor Zap execution status (real-time task tracking)
  • Execute custom actions across apps (multi-step automation)
  • Manage Zap configurations and connections (workflow management)
  • View Zap History and task details (monitoring and debugging)
  • Process webhooks and events (real-time event handling)
  • Advanced Zapier workflow automation and integration management with Zap execution, trigger configuration, and multi-app data transformation
  • Batch operations support for efficient bulk Zap operations, workflow management, and integration processing with automatic rate limit handling and retry logic
  • Real-time workflow synchronization capabilities with webhook integration support for monitoring Zapier events and triggering automated workflows

Use Cases

  • Trigger multi-step workflows across apps (end-to-end automation)
  • Connect disparate systems without code (no-code integration)
  • Automate repetitive tasks (task automation)
  • Sync data between applications (data synchronization)
  • Process webhooks and events (event-driven automation)
  • Monitor Zap performance and task execution (operational monitoring)
  • Manage integrations across thousands of apps (unified automation)
  • Debug and troubleshoot failed Zaps (error resolution)
  • Build automated integration workflows that sync external systems with Zapier for real-time data processing and business process automation

Installation

Claude Code

  1. Run: claude mcp add --transport http zapier YOUR_GENERATED_URL
  2. Verify installation: claude mcp list
  3. Test connection: claude mcp status zapier
  4. Authenticate with your Zapier account (personal token)
  5. Grant required permissions (Zap access, task execution)

Claude Desktop

  1. Visit mcp.zapier.com
  2. Sign in to your Zapier account
  3. Generate your personal MCP endpoint
  4. Copy the provided URL and add to Claude Desktop configuration
  5. Authenticate with your Zapier account (personal token)
  6. Grant required permissions (Zap access, task execution)
  7. Verify connection in Claude Desktop

Requirements

  • Zapier account (free or paid plan)
  • Personal authentication token (generated at mcp.zapier.com)
  • Network access to mcp.zapier.com (HTTPS required, HTTP transport)
  • Understanding of Zapier Zaps/workflows (automation concepts)
  • Zapier Dashboard access (for token management and Zap configuration)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Understanding of Zapier API rate limits (1000 req/min, 10000 req/hour, 100000 req/day)
  • Understanding of task limits (daily/monthly quotas, plan-specific limits)
  • Understanding of Zap throttling (burst thresholds, delay steps)
  • Optional: Zapier plan upgrade (for higher task limits and features)

Configuration

{
  "zapier": {
    "url": "https://mcp.zapier.com/YOUR_GENERATED_URL",
    "transport": "http"
  }
}

Examples

Trigger the new customer onboarding Zap

Common usage pattern for this MCP server

Ask Claude: "Trigger the new customer onboarding Zap"

Send Slack notification when deal closes

Common usage pattern for this MCP server

Ask Claude: "Send Slack notification when deal closes"

Add form submission to Google Sheets

Common usage pattern for this MCP server

Ask Claude: "Add form submission to Google Sheets"

Create Trello card from email

Common usage pattern for this MCP server

Ask Claude: "Create Trello card from email"

Trigger Zap

Trigger a Zapier Zap with input data

// Trigger Zapier Zap
const result = await zapier.zaps.trigger({
  zap_id: "zap-id",
  data: {
    field: "value",
  },
});

Security

  • Personal authentication tokens required for secure API access
  • Zap-level permission controls (granular access management)
  • Monitor task usage limits (Dashboard > Usage tracking)
  • Test Zaps before enabling (sandbox testing)
  • API token security (store tokens securely, never commit to git)
  • Zapier API keys and access tokens must be securely stored and never exposed in client-side code or public repositories - use environment variables and secure credential management
  • Zapier OAuth access tokens should be used for third-party integrations to ensure proper access control, token lifecycle management, and automatic token refresh
  • Zapier Zap, task, and account IDs may expose integration architecture and business process information - ensure Zapier resource identifiers are kept private and not shared in public configurations
  • Rate limiting and API quota management are critical for Zapier MCP servers - implement proper rate limit handling, retry logic, and quota monitoring to prevent service disruption
  • Zapier webhook configurations and payloads may contain sensitive workflow data and business information - ensure webhook endpoints are properly secured with authentication and HTTPS encryption

Troubleshooting

Task limit exceeded or Zap throttled without clear error

Check Dashboard > Usage for daily/monthly task quotas (plan-specific limits). Each action counts as one task. Zaps throttled if exceeding plan limits or burst thresholds. Add Delay after Queue step to manage rate (spread out task execution). Upgrade plan for higher limits (Free: 100 tasks/month, Starter: 750 tasks/month, Professional: 2000 tasks/month, Team: 50000 tasks/month, Company: custom). Monitor task usage in Dashboard > Usage. Use Zap History to identify high-frequency Zaps. Implement delays between steps using Delay action. Consider batching tasks to reduce task count.

API rate limit errors from connected apps

Check app-specific API usage limits in Zap History (inspect failed tasks, error codes). Zapier API rate limits: 1000 requests/minute, 10000/hour, 100000/day. Check response headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. Batch tasks where possible (combine operations). Implement delays between steps using Delay action (spread out API calls). Upgrade app plan if hitting external service limits (third-party app rate limits). Use webhooks instead of polling triggers (reduce API calls). Monitor Zap History for rate limit errors (429 status codes). Wait for rate limit reset before retrying.

Zap fails with authentication or connection errors

Use Zap History to inspect failed tasks and error codes (detailed error messages). Reauthenticate accounts if credentials expired (Dashboard > My Apps > Reconnect). Check app connection status in My Apps (verify connections are active). Verify OAuth redirect URLs correct (check app settings, redirect URI configuration). Test connection with sample trigger (use Test trigger button in Zap editor). Check personal authentication token not expired (regenerate at mcp.zapier.com if needed). Verify token has required permissions (Zap-level permission controls). Review error messages in Zap History for specific authentication issues (OAuth errors, token expiration, scope issues).

Data formatting or missing field errors in multi-step Zaps

Check payloads in Zap History for missing/malformed data (inspect Data tab for each step). Use Formatter to transform data between steps (format dates, numbers, text). Verify required fields mapped correctly (check field mappings in Zap editor). Test each step individually (use Test step button). Enable detailed logging for debugging (Zap History > Task Details). Use Lookup Tables for data transformation (reference data mapping). Check data types match expected format (string vs number, date format). Review Zap History Data tab step-by-step to identify where data is lost or transformed incorrectly. Use Code by Zapier for complex transformations if Formatter insufficient.

Zapier MCP server authentication errors with API keys

Verify API key is valid and not expired. Check API key permissions match required operations. Ensure API key format is correct (Bearer token in Authorization header). For OAuth integrations, verify token refresh logic is working correctly.

Zapier rate limit errors when processing multiple Zap requests

Implement exponential backoff retry logic with jitter. Use Zapier API rate limit headers to monitor usage. Reduce concurrent requests. Cache frequently accessed Zap data. Zapier allows 1,000 requests per hour per API key.

Zapier Zap or task access denied errors

Verify API key has access to the Zap or task. Check Zap permissions and account membership. Ensure API key has required permissions for target operations.

Zapier MCP server connection timeouts or network errors

Check network connectivity and firewall settings. Verify Zapier API endpoints are accessible. Increase request timeout values. Implement connection pooling and retry mechanisms with exponential backoff.

Source citations

Add this badge to your README

Show that Zapier MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/zapier-mcp-server.svg)](https://heyclau.de/entry/mcp/zapier-mcp-server)

How it compares

Zapier MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Source provenance).

Field

Connect to nearly 8,000 apps through Zapier's automation platform

Open dossier

Browse, summarize, and generate Canva designs directly from Claude

Open dossier

Interact with Asana workspaces to manage projects and tasks

Open dossier

Task management and project tracking with ClickUp integration

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage verifiedPackage verifiedPackage verifiedPackage verified
Source provenanceDiffersSource-backedNo submission linkNo submission linkNo submission link
Submitter
Install riskLow riskLow riskLow riskLow risk
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
BrandZapier logoZapierCanva logoCanvaAsana logoAsanaClickUp logoClickUp
Categorymcpmcpmcpmcp
Sourcefirst-partyfirst-partyfirst-partyfirst-party
AuthorZapierCanvaAsanahauptsacheNet
Added2025-09-182025-09-182025-09-182025-09-18
Platforms
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesRestrict the generated Zapier MCP URL and enabled actions because automations can write across many connected apps.Limit access to the intended Canva team or projects and review generated or modified designs before publishing or sharing them.Use a least-privilege Asana token and test task or project writes in a non-critical workspace before connecting production workflows.Scope the ClickUp API key to the intended team and review task, status, or project mutations before using it on active workspaces.
Privacy notesConnected app data, workflow payloads, account metadata, and action inputs or outputs may be sent through model context.Design contents, uploaded media, brand assets, templates, and Canva account metadata may be sent to the MCP client and model.Asana task text, project metadata, comments, assignees, due dates, and workspace details may be sent through model context.Tasks, comments, custom fields, assignees, due dates, and workspace metadata may be exposed through tool calls.
Prerequisites
  • Zapier account (free or paid plan)
  • Personal authentication token (generated at mcp.zapier.com)
  • Network access to mcp.zapier.com (HTTPS required, HTTP transport)
  • Understanding of Zapier Zaps/workflows (automation concepts)
  • Canva account (Canva Pro subscription recommended for full API access and team features)
  • OAuth 2.0 authentication configured via Canva Developer Console (https://www.canva.dev/)
  • HTTP transport support in MCP client (required for Canva MCP server)
  • Internet connection for accessing Canva API (https://api.canva.com endpoints)
  • OAuth 2.0 authentication (required for MCP server via SSE transport)
  • Asana account with access to at least one workspace
  • Workspace membership with Member role or higher (Guest role insufficient for task creation)
  • Internet connection for accessing Asana API (https://app.asana.com)
  • ClickUp account with workspace access
  • ClickUp Personal API Token from https://app.clickup.com/settings/apps
  • ClickUp Team ID (found in ClickUp workspace settings)
  • Node.js and npm/npx available for running the @hauptsache.net/clickup-mcp package
Install
claude mcp add --transport http zapier YOUR_GENERATED_URL && claude mcp list
claude mcp list && claude mcp status canva
claude mcp list && claude mcp status asana
claude mcp add clickup --env CLICKUP_API_KEY=YOUR_KEY --env CLICKUP_TEAM_ID=YOUR_TEAM_ID -- npx -y @hauptsache.net/clickup-mcp && claude mcp list
Config
Manual-only setup:
{
  "zapier": {
    "url": "https://mcp.zapier.com/YOUR_GENERATED_URL",
    "transport": "http"
  }
}
{
  "mcpServers": {
    "canva": {
      "url": "https://mcp.canva.com/mcp",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "asana": {
      "url": "https://mcp.asana.com/sse",
      "type": "sse"
    }
  }
}
{
  "mcpServers": {
    "clickup": {
      "env": {
        "CLICKUP_API_KEY": "${CLICKUP_API_KEY}",
        "CLICKUP_TEAM_ID": "${CLICKUP_TEAM_ID}"
      },
      "args": [
        "-y",
        "@hauptsache.net/clickup-mcp"
      ],
      "command": "npx",
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.