MCP Comparison · 2026
n8n (MCP archived) vs n8n MCP Server
Comparing n8n (MCP archived) and n8n as MCP servers? n8n (MCP archived) (run n8n workflows) is best when triggering existing n8n workflows. n8n (build n8n workflows) is best when authoring n8n workflows with correct node config. Both run as Model Context Protocol servers and can coexist in the same client. Updated 2026.
Side-by-side specs
Pulled from each MCP's verified fact sheet.
| n8n (MCP archived) | n8n | |
|---|---|---|
| Primary function | Run n8n workflows | Build n8n workflows |
| Maintainer | Community | czlonkowski (community) |
| Pricing | Open source | Open source |
| Setup complexity | Low · ~8 min | Low · ~3 min |
| Transport | stdio | stdio, Streamable HTTP |
| Auth model | API key | None |
| License | MIT | MIT |
| Language | TypeScript | TypeScript |
| Latest version | latest | latest |
| Compatible clients | Claude, Cursor, VS Code, Windsurf, Any MCP-compatible client, n8n 1.0+, n8n cloud | Claude, Cursor, VS Code, Windsurf, Any MCP-compatible client, n8n instances |
| Last verified | 2026-06-11 | 2026-07-16 |
Which one should you pick?
Decision rubric drawn from each MCP's documented strengths.
Choose n8n (MCP archived)
- Triggering existing n8n workflows
- Checking execution status from chat
- Inspecting failed runs
Choose n8n
- Authoring n8n workflows with correct node config
- Validating a workflow before import
- Looking up node properties and operations
Pick something else if…
- Workflow authoring (use the n8n UI)
- Hosted no-code automation (use Zapier/Make)
Feature breakdown
Key capabilities each server ships out of the box.
n8n (MCP archived)
- Self-hosted + cloud n8n support
- API-key auth
- Workflow enumeration
- Manual execution trigger
- Execution status + logs
n8n
- Docs + schemas for 2,000+ n8n nodes
- Workflow validation (incl. AI-agent nodes)
- Optional workflow management via n8n API
- Docs tools work with zero auth
- npx + Docker, MIT
Install snippets
Open the detail page for ready-to-paste config for every major client.
FAQ
n8n (MCP archived) vs n8n: which MCP server should I use?
Pick n8n (MCP archived) when triggering existing n8n workflows. Pick n8n when authoring n8n workflows with correct node config. n8n (MCP archived) is built for run n8n workflows, while n8n focuses on build n8n workflows.
Can I run both n8n (MCP archived) and n8n together?
Yes. MCP clients run each server as a separate process and surface every server's tools simultaneously, so you can install both and let your agent decide which to call. Be deliberate with auth scopes when stacking servers.
How fresh is this comparison?
Updated for 2026. n8n (MCP archived)'s last verification: 2026-06-11. n8n's last verification: 2026-07-16. We refresh detail-page facts on every catalog rebuild.
More n8n (MCP archived) comparisons
Browse all Automation & Workflows MCPs? See the full ranked list →