Open-source n8n MCP alternatives
The n8n MCP server publishes its source, so you can read exactly how it inspects nodes and deploys workflows before you trust it with a write. Every option below is open source too, which lets you audit the code, pin a version, and patch behaviour rather than wait on a vendor.
The list runs from flow-based engines that mirror n8n's model to code-first task runners and broad integration layers. All of them ship a repo you can clone and read end to end.
The 8 best open-source alternatives
Activepieces is open source down to its automation pieces, and its official server turns those pieces and flows into agent tools through a per-project remote endpoint. The closest match to n8n if reading the code matters.
Set up Activepieces →Flow-shaped and open source, the Node-RED community server reads, builds, and updates flows, manages nodes, and inspects runtime state through the Admin API, so you can confirm what it touches before granting access.
Set up Node-RED →For durable code workflows, the open-source Temporal server starts, signals, and queries workflows and manages batch operations and schedules in a durable-execution cluster. The repo is there to vet how it drives your cluster.
Set up Temporal →- ComposioOfficial
Open source and broad, Composio connects an agent to 500+ apps through one OAuth-authenticated endpoint. You can read how it manages connections and executes tools before pointing it at production accounts.
Set up Composio → - InngestOfficial
Inngest's Dev Server MCP is open source and event-driven: send events, invoke functions, monitor runs, and search the docs against a local dev server, with source you can audit alongside your own functions.
Set up Inngest → - PipedreamOfficial
Open source and broad, the Pipedream server connects an agent to 2,800+ apps and 10,000+ prebuilt actions with managed OAuth. Reading the repo clarifies how those per-app endpoints are wired.
Set up Pipedream → - Trigger.devOfficial
Code-first and open source, the Trigger.dev server scaffolds projects, triggers and debugs background tasks, deploys to any environment, and runs TRQL queries, all from a repo you can inspect.
Set up Trigger.dev → - WindmillOfficial
Windmill's official server is open source and turns scripts and flows into agent tools: run scripts, manage flows, resources, variables, jobs, and schedules, and expose your own scripts. A code-and-flow hybrid you can read top to bottom.
Set up Windmill →
How to choose
Among the open-source options, Activepieces and Node-RED stay closest to n8n's visual flow model, while Windmill blends scripts and flows. Temporal, Inngest, and Trigger.dev lean code-first for durable or event-driven work. Composio and Pipedream are the wide integration layers. Whichever you pick, the win of open source here is the same: read the repo before you wire it into accounts with write access.
FAQ
- Is the n8n MCP server open source?
- Yes. The community n8n server publishes its code, so you can audit how it reads node definitions and deploys workflows, and pin or patch the version you run. Every alternative on this page is open source as well.
- Which open-source alternative is most like n8n?
- Activepieces, because it is open-source and flow-based and its server exposes pieces and flows to an agent. Node-RED is the other close match if your automations are wired as Node-RED flows rather than n8n nodes.