What it does
actionbridge is an MCP server that lets an MCP client discover and run whatever actions a Zapier account has exposed. Its eight tools cover listing, searching and inspecting actions, listing action apps, describing and validating action inputs, executing an action, and fetching an execution result. It does not provide a catalogue of each app's actions, Zap or folder management, Zap history views, app connection administration, or Zapier's hosted MCP endpoint.
It suits cases where an MCP client needs a single generic runner over the actions exposed through one Zapier key, rather than per-app tools. Each tool is also available as a CLI subcommand that takes one JSON object as its argument.
Setup requires a Zapier API key for the exposed-actions API, set as an environment variable. The API base URL can optionally be overridden through another variable, and the publisher documents MCP client configuration, Docker use and development steps. The project is released under the MIT license.
Limitations and requirements
Requires a Zapier API key for the exposed-actions API; without it, every tool call fails with an error naming the missing variable. Actions available depend on what the key's Zapier account has exposed. Per-app action catalogues are not enumerated or claimed, and the hosted per-user Zapier MCP endpoint is not reproduced. Zap and folder management, Zap history views and app connection administration are not included.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/actionbridge
Zapier exposed actions as MCP tools via a generic action runner.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it