Zapier
Vendor domain: zapier.com · vendor page id zapier-com
A live handshake means the URL answered an MCP initialize as a server on the probe date. It is liveness and nothing more: nobody has run its tools. A tool being catalogued means a server names it, by answering tools/list, in its own source, or in the vendor's documentation. None of them has been called. A tool count of 0 means not measured, never zero tools.
Zapier
A cloud automation platform connecting thousands of apps via trigger-action workflows (Zaps), plus a separate agent product.
Zapier MCP
Zapier's own MCP endpoint, letting Claude, ChatGPT, Cursor, and other MCP clients trigger the same 9,000+ app actions Zapier already exposes to its classic trigger-action Zaps.
2 of 2 free to start, a solo operator gets API access without talking to anyone.
The gate is the api_gate field on each product entry, established by hand on the last_checked date shown above. It records whether a solo operator can get API access without a contract. Money is not tracked.
3 distinct job labels, the union across 2 products, tagged 2026-08-25. A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.
- https://zapier.com/mcp (Zapier, docs page, probed 2026-09-04)
- https://mcp.zapier.com/login?redirectTo=%2Fmcp (Zapier MCP, docs page, probed 2026-09-04)
An endpoint is where an agent connects. A docs page is where a person reads about connecting. Both are published because both are what the probe found; an agent needs the first.
Zapier zapier-platform official CLI
npx zapierquoted from https://zapier.com/sdk on 2026-09-27, via npx
Login or key hint: handles auth
2 more install commands, harvested 2026-09-27, all on the tool page.
A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it.
github.com/zapier tied to the vendor by rule 2, account website https://zapier.com has the vendor's domain, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| zapier-platform | CLI | The toolkit for you to build an integration on Zapier | 551 | 2026-09-08 | |
| kubechecks | infrastructure | Check your Kubernetes changes before they hit the cluster | 612 | 2026-09-02 | v3.4.0 |
| connectors | CLI | Connect your agent to the apps you already use - with or without Zapier. | 164 | 2026-08-25 | |
| agent-skills | other | Agent skills for working with Zapier, maintained by Zapier teams. Indexed by skills.sh. | 17 | 2026-08-25 | |
| marketplace | CLI | Install Zapier in your coding agent via the Claude Code, Codex, and Copilot CLI marketplaces. | 13 | 2026-08-11 |
Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.
A job tag is a vendor claim: it means the vendor says the product does this, and it is not a test result. A listed tool has not been run: the catalogue says what an agent could try, not what works. 1 of 1,252 directory entries are bench tested, meaning somebody personally ran the tool on a stated date, and 0 of this vendor's 2 products are among them. There is no verdict here on whether this vendor is better than another.
Vendor pages group the directory's canonical product entries by vendor_domain. The vendor name is the product display name that matches the domain when several products share it; nothing on this page is typed by hand. Data baked 2026-09-27 by build_directory.py (phase 1).