Zapier MCP Server

The Zapier MCP Server is Zapier's official Model Context Protocol server for AI-powered workflow automation. It connects MCP-capable AI clients — including Claude Code, Cursor, VS Code, Gemini CLI, and OpenAI Codex — to the Zapier automation platform and its more than 9,000 connected apps. The direct product link to the official Zapier MCP documentation is https://docs.zapier.com/mcp/home; the open-source plugin distribution repository is at https://github.com/zapier/zapier-mcp. According to the provider, Zapier MCP gives any MCP-compatible AI client governed access to thousands of apps — no code, no local infrastructure, SOC 2 Type II certified.

What is the Zapier MCP Server?

According to the provider, Zapier MCP is a hosted remote server that implements the Model Context Protocol (MCP) and serves as a bridge between AI agents and the entire Zapier automation platform. When an agent receives a natural language task — such as "Send a Slack message to #team" or "Create a row in Google Sheets" — the MCP client calls the Zapier server, which executes the corresponding action via the configured Zaps. The server runs exclusively as a hosted service and is reachable at https://mcp.zapier.com/api/v1/connect. No local build step, npm package, or own server infrastructure is required.

The repository github.com/zapier/zapier-mcp distributes the Zapier MCP plugin — the part that lives in the AI client. The plugin adds guided onboarding, a first demo, and role-tailored skills on top of the base server connection. Different clients integrate the plugin in different ways: Claude Code and OpenAI Codex via zapier/marketplace, Cursor via a direct deeplink badge, and Gemini CLI via gemini extensions install.

Prerequisites

Using the Zapier MCP Server requires an active Zapier account and at least one pre-configured Zap or AI Action in Zapier. Access to the MCP server itself requires no own infrastructure according to the provider; an MCP-capable AI client is the only local prerequisite. Depending on the app or action triggered, specific credentials for third-party services (for example a Google account or Slack workspace) need to be stored within Zapier. Authentication against the MCP server uses OAuth or a Zapier API key that the connected client sends with each request. Usage limits depend on the Zapier subscription; current pricing is available at zapier.com/pricing.

Features: Trigger Zaps and connect 9,000+ apps

The core toolset of the Zapier MCP Server allows, according to the provider, triggering Zaps and AI Actions from the AI client, retrieving data from connected apps, and returning structured results. Supported apps include, per the provider, more than 9,000 services — among them Gmail, Slack, Google Sheets, Notion, HubSpot, Salesforce, Linear, Asana, Trello, Jira, GitHub, Airtable, Dropbox, Mailchimp, Typeform, Calendly, Zoom, and hundreds more. The tools that actually appear depend on the Zaps and AI Actions configured and enabled in the Zapier account: only enabled actions are visible to the MCP client.

Typical use cases include sending emails or messages automatically based on AI output, creating CRM records, writing spreadsheet rows, triggering webhook-based workflows, and retrieving structured data sets from connected systems. According to the provider, no programming knowledge is required to configure Zaps; the setup is done entirely through the Zapier interface.

The plugin from the repository adds guided onboarding: it runs a brief demo, explains available actions, and tailors recommendations to the user's role (for example sales, marketing, or engineering). VS Code connects directly to the hosted server via HTTP without the plugin; other clients integrate it through their respective marketplace.

Setup

Connecting to the Zapier MCP Server requires only a server URL, per the provider. For VS Code, that URL is https://mcp.zapier.com/api/v1/connect (type: http), added via the VS Code badge in the repository or manually in .vscode/mcp.json. For Claude Code, claude mcp add --transport http zapier https://mcp.zapier.com/api/v1/connect is sufficient. Cursor uses the deeplink badge in the repository or a manual JSON configuration at ~/.cursor/mcp.json. Gemini CLI connects via gemini extensions install https://github.com/zapier/zapier-mcp followed by /mcp auth zapier. OpenAI Codex and GitHub Copilot CLI use zapier/marketplace.

After the first connection, an OAuth flow opens for Zapier authentication according to the provider. Those who prefer not to use OAuth can alternatively generate an API key in the Zapier dashboard. Afterwards, the desired AI Actions should be enabled and configured as Zaps in the Zapier account so that the MCP server exposes them as tools.

Security and data access

According to the provider, the Zapier MCP Server processes tool calls and forwards them to the configured Zapier actions. The authentication of the connected user determines which Zaps and actions are visible and executable; actions that have not been enabled are not reachable by the MCP client. According to the provider, Zapier is SOC 2 Type II certified. Because Zaps can trigger actions in third-party apps — sending emails, writing CRM records, creating files — access should be limited to only the actions actually needed. Prompt injection via external data sources is a general risk for MCP servers with write access to third-party systems; agent-driven write actions should be tested before production use and limited to the minimum required scope.

FAQ

Is the Zapier MCP Server free? The server itself and the plugin repository are MIT licensed and open source. Usage depends on the Zapier subscription; current plan and usage information is available at zapier.com/pricing. Costs arise from Zapier Tasks, the selected plan, and the chosen AI client — not from the MCP Server itself.

Do I need to install anything locally? No. The Zapier MCP Server runs exclusively as a hosted remote service. Only the server URL in the AI client is needed to connect. The plugin repository does not include a local server mode; those who want to integrate the plugin do so through their client's marketplace.

How many apps are available? According to the provider, Zapier MCP connects more than 9,000 apps. Which of those appear as tools in the AI client depends on the AI Actions configured and enabled in the Zapier account.

Active Zapier account with at least one configured Zap or AI Action, and an MCP-capable AI client such as Claude Code, Cursor, or VS Code.

For Claude Code: claude mcp add --transport http zapier https://mcp.zapier.com/api/v1/connect. VS Code: add server URL https://mcp.zapier.com/api/v1/connect (type: http) to .vscode/mcp.json. Cursor: use the deeplink badge in the repository or a manual JSON configuration.

claude mcp add --transport http zapier https://mcp.zapier.com/api/v1/connect

OAuth flow through Zapier login (recommended) or Zapier API key for non-interactive environments.

Access to Zaps and AI Actions is scoped to the authenticated Zapier account; only enabled actions are visible to the MCP client.

The server receives tool calls and triggers the configured Zapier actions. Data flows through the Zapier platform to the connected apps.

Zaps can trigger write actions in third-party apps (emails, CRM records, files). Prompt injection via external data sources is a general MCP risk when write access is involved.