by Zapier
Updated October 20, 2026
MCP100 verdict
Not currently recommended. First-party evidence supports Shortlist admission; this is not a Recommended-tier security certification.
MCP100 Assessment
Editorial verdict
Reviewed October 19, 2026
Task Fit
Mapped
Specialized workflows
Trust
Status warning
First-party documentation establishes Zapier MCP, its dynamic secure URL model, and cross-app action scope. Exact tool inventory is user-configured, and runtime context footprint remains unmeasured.
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals unavailable
No independently comparable adoption metric is currently stored.
Evidence scope
443 shared-repository stars · not MCP-specific
No MCP-specific package metric is stored
Repository identity: zapier/zapier-mcp
Stars observed October 20, 2026 · Downloads observed October 20, 2026
Official Zapier repository distributes plugins/configuration for the hosted Zapier MCP server; it does not contain the hosted server implementation. Stars are distribution evidence, not hosted-server implementation adoption.
Zapier MCP is hosted and does not expose an exact public server package for download measurement.
Publisher activity observed October 20, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed October 19, 2026
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
Complete client-specific setup, verification and removal are not documented in this reviewed source.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-10-20
Type-appropriate, source-backed setup for this mcp server profile.
Loading optional publisher installation details…
No complete evidence-backed client setup steps are currently stored. Optional publisher documentation may provide additional context below.
Capability
Zapier MCP is a first-party MCP for let an ai client execute selected zapier actions across connected apps. Authentication/setup: Unique secure Zapier MCP URL plus Zapier-managed connected-app credentials. Each user/server has a generated secure URL and a user-selected action set, so there is no universal endpoint or fixed tool count. Actions can create broad external side effects across connected services and should be narrowly scoped and confirmed.
Zapier MCP tool inventory is intentionally dynamic: users choose which Zapier actions to expose, so a universal tool count would be misleading.
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
Reviewed access
Related reviewed MCPs
Codebase knowledge graph for AI agents — 159 languages, sub-ms queries, 99% fewer tokens.
Choose this instead if
Choose Codebase Memory MCP instead if repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages.
Recommended after reviewed 2026-09-25 admission dossier: all_current_selected_gates_pass.
Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Choose this instead if
Choose Terraform MCP instead if connect compatible AI clients to HashiCorp's documented MCP capabilities.
Recommended after reviewed Batch 1 correction: exact 61-tool contract closes the prior formal Recommended gap.
Connect agents to Azure resources and more than forty Azure services.
Choose this instead if
Choose Azure MCP Server instead if discovering and inspecting resources across supported Azure services.
Connect agents to Azure resources and more than forty Azure services.
Zapier is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
From the publisher README
Original client setup and configuration retained from the publisher documentation.
Publisher-documented clients
These names appear in the publisher's installation documentation. MCP100-verified configurations are shown separately above when available.
Connecting Zapier MCP to your AI client only takes a server URL — see docs.zapier.com/mcp/clients for step-by-step instructions for every supported client.
A few clients also install the plugin distributed from this repo, which layers guided onboarding, a first-use demo, and role-tailored skills on top of that base connection:
zapier/marketplace or anthropics/claude-plugins-officialcursor/mcp-serverszapier/marketplaceanthropics/knowledge-work-pluginsgemini extensions install https://github.com/zapier/zapier-mcp, then /mcp auth zapier — see gemini-extension.jsonVS Code connects directly to the hosted MCP server rather than through a plugin — use the badge above, or add https://mcp.zapier.com/api/v1/connect (type: http) manually.
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
Zapier MCP gives any MCP-compatible AI client governed access to 9,000+ apps — send messages, pull data, trigger workflows, all in plain English. No code, no infrastructure, SOC 2 Type II certified. ⚡
This repo distributes the Zapier MCP plugin — the part that lives in your AI client. Install it from your client's marketplace and your assistant arrives knowing how to use Zapier well, with guided onboarding, a quick demo, and skills tailored to your role.
plugins/zapier/: the plugin that onboards you to Zapier MCP and supercharges your experienceZapier MCP is also listed on: