mcpField
A
actionbridge

actionbridge

Local
github.com/CloudCorpRecordsProductivity0Updated 1w ago
Repository

About actionbridge

actionbridge is a generic MCP action runner for the documented Zapier exposed-actions API. It lets MCP clients discover, inspect, validate, execute, and retrieve results for actions exposed by the configured Zapier account, without claiming parity with Zapier's full app catalogue or hosted MCP endpoint.

Key features

  1. 01List and search available actions
  2. 02Inspect action details and inputs
  3. 03Validate action parameters
  4. 04Execute actions
  5. 05Retrieve execution results

Use cases

  1. 01Find an exposed action by name or app
  2. 02Check required inputs before execution
  3. 03Run a Zapier exposed action from an MCP client
  4. 04Retrieve the result of a completed action

MCP support

Exposes a generic runner for the Zapier exposed-actions API as MCP tools. It does not provide Zapier's hosted per-user MCP endpoint or specific app action catalogues.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "cloudcorprecords-actionbridge": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/actionbridge"
      ]
    }
  }
}
Run commandnpx -y @reneturcios/actionbridge

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@reneturcios/actionbridge0.1.0
ocighcr.io/cloudcorprecords/actionbridge:0.1.0

Tools

8

Saved tool list · updated 1w ago

This tool takes no parameters.

Details

From the project README

actionbridge

Zapier exposed actions as MCP tools, talking to the documented Zapier exposed-actions (NLA) API. actionbridge is a clean-room generic action-runner core, under a new name: fresh code, no copied branding.

Special case, stated plainly: Zapier's surface is thousands of per-app actions behind a hosted per-user MCP endpoint; per-app action parity is NOT enumerable and is NOT claimed. actionbridge is a generic runner over whatever actions the key's account has exposed. It does not reproduce Zapier's hosted MCP endpoint, its per-user URL/key embedding, or any specific app's action catalogue.

Tools (generic runner core, 8)

list_actions, search_actions, get_action, execute_action, list_action_apps, describe_action_inputs, validate_action_params, get_execution_result.

Not included, by design: every specific app's action catalogue (not enumerable), Zap/Zaps management, folders, Zap history UI surfaces, app connections admin, and the hosted MCP endpoint itself.

Setup

Create a Zapier API key for the exposed-actions API and set it:

export ZAPIER_API_KEY=...

Optionally override the API base with ZAPIER_API_BASE_URL (default https://nla.zapier.com/api/v1). Without the key, every tool call fails with an error naming the missing variable.

CLI

npx @reneturcios/actionbridge list_actions
npx @reneturcios/actionbridge execute_action '{"action_id":"123","instructions":"Send it"}'
npx @reneturcios/actionbridge mcp        # stdio MCP server

Each tool name is a subcommand taking one JSON object argument.

MCP client config

{
  "mcpServers": {
    "actionbridge": {
      "command": "npx",
      "args": ["-y", "@reneturcios/actionbridge", "mcp"],
      "env": { "ZAPIER_API_KEY": "..." }
    }
  }
}

Docker

docker run -i -e ZAPIER_API_KEY ghcr.io/cloudcorprecords/actionbridge

Development

npm install
npm run build
npm test

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.