Browse / Alternatives / n8n
n8n alternatives for AI agents
2 alternatives to n8n. 2 have an interface an agent can drive. 1 is open source.
| Listing | License | Agent interface | Reach | Effort | Last activity |
|---|---|---|---|---|---|
| EDDI | Apache-2.0 | MCP server, from the builder | 8 of 10 jobs | Config only | Nov 3, 2026 |
| Heym | MIT with Commons Clause | MCP server, from the builder | 8 of 10 jobs | Config only | Nov 3, 2026 |
EDDI
Config-driven server that runs AI agents from versioned JSON, driven by MCP, REST or A2A.
Open source · EDDI Solutions managed plans
- I want agents defined in versioned config that my coding agent can create and deploy over MCP instead of writing framework code
- I need agents that stop for human approval and keep an audit trail in a self-hosted deployment
- I want several agents to debate a question and hand back a synthesized answer
- I want my agents to call agents on other platforms over A2A and to answer those platforms too
- Create knowledge bases and ingest documents for RAG
- Manage the secrets vault, import agents and sync instances
- Infrastructure-grade: a Java 25 server plus MongoDB or PostgreSQL, with optional Keycloak and NATS for authentication and clustering
- The shipped default has OIDC off, so no endpoint needs a token, A2A JSON-RPC included; the compose files bind to 127.0.0.1, so turn authentication on before exposing it
- A2A agents are opt-in: set a2aEnabled per agent. eddi.a2a.enabled is on by default but only switches the endpoints
- The root Agent Card describes only the first A2A-enabled agent; other agents use /a2a/agents/{agentId}/.well-known/agent-card.json
- A2A ListTasks, SubscribeToTask, push notifications and the extended card are refused, and clustered deployments need a shared IA2ATaskStore
- Set EDDI_VAULT_MASTER_KEY or secret references such as ${vault:name} fail; store provider keys there, not in agent JSON
- Most creating MCP tools are not idempotent: after a transport error, check with a list tool before retrying or you get a duplicate
Heym
Self-hosted runtime for agentic workflows, driven by MCP, with its agent also served over A2A.
Heym Core: Free · Heym Work: €99 per month · Enterprise
- I want to build agent workflows on my own servers without paying per execution
- I want my coding agent to build, test and run workflows for me through one MCP tool
- I want a person to approve what an agent does before the run continues
- I want another agent to send tasks to my self-hosted workflow platform over A2A
- Enter credentials
- Turn on MCP and A2A, and set team access
- The Commons Clause forbids selling a product or service whose value comes substantially from Heym, and it names hosting and consulting fees. An agency that charges to host or support Heym needs a commercial license
- A2A is off by default and rides on the Heym Agent: turn on the agent, pick a credential and model, then tick Enable A2A. Until then the card address returns 404
- A2A 1.0 only: 0.3 method names such as message/send are refused, push notifications are not offered, and file parts are refused
- Named servers serve their card at /api/a2a/servers/{server_id}/agent-card.json, not the well-known path
- heym_chat is one plain-language tool, so an MCP client's reach runs through a model on your own credential
- Test runs from heym_chat are real runs and their side effects happen
- An agent cannot enter a credential; a person has to save it on a Heym page
Questions
Is there an open source alternative to n8n?
Yes. 1 of the 2 listings here is open source: EDDI (Apache-2.0).
Which n8n alternatives have an MCP server?
EDDI and Heym have MCP servers from their builders.
Which n8n alternative can an agent do the most with?
EDDI: 8 of 10 recorded jobs reachable. Heym: 8 of 10 recorded jobs reachable. Jobs differ by listing, so read each list before you choose.
Listings come from reading each repo and its docs. Reach counts the jobs an agent can do through the stated interface, and each listing page shows the evidence. Order follows fit. For agents: Markdown · JSON