io.github.CloudCorpRecords/actionbridge
Zapier exposed actions as MCP tools via a generic action runner.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@reneturcios/actionbridgeclaude mcp add actionbridge -- npx -y @reneturcios/actionbridge@0.1.0 mcp
{
"mcpServers": {
"actionbridge": {
"command": "npx",
"args": [
"-y",
"@reneturcios/actionbridge@0.1.0",
"mcp"
]
}
}
}
ghcr.io/cloudcorprecords/actionbridge:0.1.0claude mcp add actionbridge -- docker run -i --rm ghcr.io/cloudcorprecords/actionbridge:0.1.0 mcp
{
"mcpServers": {
"actionbridge": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/cloudcorprecords/actionbridge:0.1.0",
"mcp"
]
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
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
Frequently asked questions
What is io.github.CloudCorpRecords/actionbridge?
Zapier exposed actions as MCP tools via a generic action runner.
How do I install io.github.CloudCorpRecords/actionbridge?
It runs on your machine. In Claude Code: claude mcp add actionbridge -- npx -y @reneturcios/actionbridge@0.1.0 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.CloudCorpRecords/actionbridge need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.CloudCorpRecords/actionbridge open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.CloudCorpRecords/actionbridge?
It is published by CloudCorpRecords. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.