Zapier MCP

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-09-07. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

https://mcp.zapier.com/api/v1/connect ; https://mcp.zapier.com/login?redirectTo=%2Fmcp (redirect correction 2026-08-28: the bare address previously recorded here, mcp.zapier.com, 307s to /mcp and then to this signed-in console URL, which returns 200. It is an auth wall, not documentation; the public documentation for the same server is https://zapier.com/mcp) ; repo https://github.com/zapier/zapier-mcp

• https://mcp.zapier.com/api/v1/connect
• https://mcp.zapier.com/login?redirectTo=%2Fmcp
• https://zapier.com/mcp
• https://github.com/zapier/zapier-mcp

A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.

Recorded by the harvest: every tool is one of the customer's own connected Zaps

• auto_provision_mcp
  Automatically provisions tools from your existing Zapier connections.
  evidence: in the vendor docs · calling it reads · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server
• create_zapier_skill
  Creates new reusable workflows.
  evidence: in the vendor docs · calling it reads · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server
• delete_zapier_skill
  Removes skills.
  evidence: in the vendor docs · calling it reads · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server
• disable_zapier_action
  Removes an action you no longer need.
  evidence: in the vendor docs · calling it reads · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server
• discover_zapier_actions
  Searches for apps and actions available to add.
  evidence: in the vendor docs · calling it writes · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server
• enable_zapier_action
  Enables a specific action as a callable tool.
  evidence: in the vendor docs · calling it reads · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server
• execute_zapier_read_action
  Runs search and lookup operations.
  evidence: in the vendor docs · calling it reads · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server
• execute_zapier_write_action
  Runs create, send, or update operations.
  evidence: in the vendor docs · calling it writes · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server
• get_configuration_url
  Returns the URL to your Zapier MCP configuration page.
  evidence: in the vendor docs · calling it reads · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server
• get_zapier_skill
  Retrieves a specific skill by name.
  evidence: in the vendor docs · calling it reads · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server
• inspect_zapier_actions
  Lists your enabled actions with what you need to run them.
  evidence: in the vendor docs · calling it reads · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server
• list_zapier_skills
  Lists saved workflow instructions.
  evidence: in the vendor docs · calling it reads · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server
• send_feedback
  Sends feedback to Zapier.
  evidence: in the vendor docs · calling it reads · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server
• update_zapier_skill
  Modifies existing skills.
  evidence: in the vendor docs · calling it reads · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server
• write_code_action
  Generates custom code when built-in actions do not fit. Exposed on some servers only.
  evidence: in the vendor docs · calling it reads · read off zapier, an aggregator wrapping the vendor's API rather than the vendor's own server

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.

Install, as the source shows it:

npx zapier

quoted from https://zapier.com/sdk on 2026-09-27, via npx

npm install -g zapier-platform-cli

quoted from https://www.npmjs.com/package/zapier-platform-cli on 2026-09-27, via npm

npm install -g @zapier/zapier-sdk-cli

quoted from https://www.npmjs.com/package/@zapier/zapier-sdk-cli on 2026-09-27, via npm

Login or key hint seen on the page:

handles auth

Packages seen, with the version on 2026-09-27:

• npm: zapier-platform-cli 19.1.0
• npm: @zapier/zapier-sdk-cli 0.84.4

Where it was documented:

• https://zapier.com/sdk (the page that documented the CLI)

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. Harvest date 2026-09-27.

api_gate, verbatim from the file:

free (bundled into existing Zapier plans; each MCP tool call consumes 2 tasks from the account's standard task quota - no separate SKU)

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:

• https://github.com/zapier/zapier-mcp

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:

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.

• Proxy tool calls to SaaS apps

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.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

• https://zapier.com/mcp
• https://mcp.zapier.com/login?redirectTo=%2Fmcp
• https://github.com/zapier/zapier-mcp
• https://mcp.zapier.com/api/v1/connect

4 source URLs. Raw sources field, verbatim:

https://zapier.com/mcp, https://mcp.zapier.com/login?redirectTo=%2Fmcp, https://github.com/zapier/zapier-mcp, https://mcp.zapier.com/api/v1/connect

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.