zapier / zapier-mcp

The four are zapier-onboard (introduces the plugin, walks through authentication, and routes you based on what's already set up), zapier-demo (the smallest possible win — pick one app, enable one read action, watch it run), zapier-explore (interviews you about your role and suggests specific use cases to enable next, the natural step after zapier-demo), and zapier-status (a health-check dashboard, an audit for waste and duplicates, or step-by-step diagnosis). All four are mcp_service in our dependency check, meaning none of them does anything until the Zapier MCP server is already added at mcp.zapier.com.

This is Zapier's own repository — official in our records — and the plugin ships through four separate marketplaces: Anthropic's Claude Code and Claude Cowork catalogs, Kiro's Powers catalog, and Cursor's MCP server registry. It's for someone who has just installed, or is about to install, the Zapier MCP plugin in one of those clients and wants the guided walk-through rather than reading Zapier's docs cold.

READ THE FULL ANALYSIS＋

The catalog of 9,000+ app actions lives outside this repository. Nothing here documents what a specific action looks like once you enable it — that's served live by mcp.zapier.com itself, scoped to whichever apps and actions you turn on. A reader hoping this page is a directory of Zapier automations will find four meta-skills about setting one up, and nothing about the automations themselves.