Open-source Zapier MCP alternatives
Zapier's MCP server is closed and run by Zapier. You authenticate to a per-account hosted endpoint and cannot read the engine that runs your actions. If you would rather use a server whose source you can audit, fork, or pin, every option below publishes its code.
That matters for automation specifically, because the engine can reach a lot of apps and run a lot of actions on your behalf. Reading the repo before you connect tells you what the agent can actually trigger.
The 8 best open-source alternatives
Open source through and through, Activepieces' official server turns its automation pieces and flows into agent tools over a per-project remote endpoint, with the engine's source there to read.
Set up Activepieces →The community n8n server is open source and gives an agent complete knowledge of n8n's 800+ nodes to design, validate, and deploy workflows. You can audit both the server and the engine it drives.
Set up n8n →Flow-based and inspectable, the open-source Node-RED server reads, builds, and updates flows, manages nodes, triggers inject nodes, and inspects runtime state via the Admin API, an engine for event and device wiring.
Set up Node-RED →For durable execution with an auditable connector, the Temporal server manages workflows, signals, queries, batch operations, and schedules in a cluster. The open source lets you confirm exactly what it can trigger.
Set up Temporal →- ComposioOfficial
Composio's universal server is open source and connects an agent to 500+ apps like Gmail, Slack, GitHub, and Notion through one OAuth endpoint, the closest open connector hub to Zapier's reach.
Set up Composio → - InngestOfficial
For code-defined workflows you can read end to end, the open-source Inngest Dev Server MCP sends events, invokes functions, monitors runs, and searches docs against a local Inngest dev server.
Set up Inngest → - PipedreamOfficial
Pipedream's official server is open source and reaches 2,800+ apps and 10,000+ prebuilt actions with managed OAuth and per-app endpoints, a broad hub whose code you can vet before connecting.
Set up Pipedream → - Trigger.devOfficial
Aimed at developers defining background jobs in code, the open-source Trigger.dev server scaffolds projects, triggers and debugs background tasks, deploys to any environment, and runs TRQL queries.
Set up Trigger.dev →
How to choose
Every server here publishes its source, so pick by automation style. Composio and Pipedream are open connector hubs closest to Zapier's breadth; Activepieces, n8n, and Node-RED are self-hostable engines you can read; Temporal, Inngest, and Trigger.dev target code-defined and durable workflows. Whatever you choose, read the repo before granting an agent the ability to run actions across your apps.
FAQ
- Is the Zapier MCP server open source?
- No. Zapier runs the server itself and does not publish its source, so you connect to a per-account hosted endpoint you cannot audit or modify. Every alternative on this page ships its code publicly.
- Why choose an open-source automation MCP server?
- You can read which apps and actions the engine can reach, pin or patch the version you run, and self-host it on infrastructure you control. That review matters because an automation engine can trigger many actions across your accounts on the agent's behalf.