Open-source Pipedream MCP alternatives
Pipedream's MCP server publishes its source, so you can read how its connector layer reaches 2,800+ apps before pointing an agent at it. The servers here also ship their code, which matters when you want to vet exactly which integrations and actions an agent can fire and pin a version you trust.
These are the open-source automation servers people compare against Pipedream. They split between connector catalogs and workflow engines you can read and run yourself. The note on each says which side it lands on.
The 8 best open-source alternatives
Activepieces is the closest open-source match: its server turns open-source automation pieces and flows into agent tools through a per-project remote endpoint, with the connector code there to audit.
Set up Activepieces →n8n's open-source server gives an agent complete knowledge of 800+ nodes so it can design, validate, and deploy workflows. You can read the repo and run the engine yourself for full control over what executes.
Set up n8n →Node-RED's open-source server reads, builds, and updates flows, manages nodes, triggers inject nodes, and inspects runtime state via the Admin API. A flow engine whose source and runtime you operate.
Set up Node-RED →Temporal is open source and about durable execution: its server manages workflows, signals, queries, batch operations, and schedules in a cluster. Audit the code, then run reliable long-running work yourself.
Set up Temporal →- ComposioOfficial
Composio is the nearest open-source connector aggregator: a universal server reaching 500+ apps through one OAuth endpoint. A smaller catalog than Pipedream's, with code you can read.
Set up Composio → - InngestOfficial
Event-driven and open source, the Inngest Dev Server MCP sends events, invokes functions, monitors runs, and searches docs against a local dev server. Workflows you can develop and inspect locally.
Set up Inngest → - Trigger.devOfficial
Trigger.dev is open source and developer-first: its server scaffolds projects, triggers and debugs background tasks, deploys to any environment, and runs TRQL queries. A background-jobs platform you can self-host.
Set up Trigger.dev → - WindmillOfficial
Scripts, flows, resources, variables, jobs, and schedules all run through the open-source Windmill server, which also exposes your own scripts as agent tools. A script-and-flow platform whose code and runtime you control.
Set up Windmill →
How to choose
All of these publish their code. For the connector-catalog approach, Composio and Activepieces are the open-source matches, with smaller catalogs than Pipedream's. For workflow engines you run yourself, n8n, Node-RED, and Windmill fit, while Temporal, Inngest, and Trigger.dev focus on durable execution, events, and background jobs. Read the repo before granting an agent action-firing access.
FAQ
- Is the Pipedream MCP server open source?
- Yes. Pipedream publishes the server's source, so you can read how its connector layer reaches 2,800+ apps before connecting an agent. Every alternative on this page also ships its code publicly.
- Why pick an open-source automation MCP server?
- You can read exactly which integrations and actions the server can fire, pin or patch the version you run, and keep credentials on infrastructure you control. The trade-off is operating the platform yourself rather than leaning on Pipedream's hosted connectors and managed OAuth.