topmcps
Browse MCPs

MCP Comparison · 2026

Make (Integromat) vs n8n (MCP archived) MCP Server

Comparing Make (Integromat) and n8n (MCP archived) as MCP servers? Make (Integromat) (run make scenarios) is best when triggering existing make scenarios. n8n (MCP archived) (run n8n workflows) is best when triggering existing n8n workflows. Both run as Model Context Protocol servers and can coexist in the same client. Updated 2026.

Make (Integromat)

Make (Integromat)

Trigger Make scenarios and inspect runs from an AI agent.

n8n (MCP archived)

n8n (MCP archived)

Trigger and manage n8n workflows from an AI agent. Community MCP wrapper archived; n8n itself is unaffected.

Side-by-side specs

Pulled from each MCP's verified fact sheet.

 Make (Integromat)n8n (MCP archived)
Primary functionRun Make scenariosRun n8n workflows
MaintainerCommunity (unofficial Make.com MCP)Community
PricingFreemiumOpen source
Setup complexityLow · ~7 minLow · ~8 min
Transportstdiostdio
Auth modelAPI keyAPI key
LicenseMITMIT
LanguageTypeScriptTypeScript
Latest versionlatestlatest
Compatible clientsClaude, Cursor, VS Code, Windsurf, Any MCP-compatible client, Make Cloud (any region)Claude, Cursor, VS Code, Windsurf, Any MCP-compatible client, n8n 1.0+, n8n cloud
Last verified2026-05-312026-05-27

Which one should you pick?

Decision rubric drawn from each MCP's documented strengths.

Choose Make (Integromat)

  • Triggering existing Make scenarios
  • Inspecting failed runs
  • Listing scenarios available to the agent
See full Make (Integromat) write-up →

Choose n8n (MCP archived)

  • Triggering existing n8n workflows
  • Checking execution status from chat
  • Inspecting failed runs
See full n8n (MCP archived) write-up →

Pick something else if…

  • Authoring scenarios (use the Make visual builder)
  • Workflow authoring (use the n8n UI)

Feature breakdown

Key capabilities each server ships out of the box.

Make (Integromat)

  • Make Cloud + EU + US regions
  • API-token auth scoped to one org
  • Scenario enumeration
  • On-demand execution
  • Run-log inspection

n8n (MCP archived)

  • Self-hosted + cloud n8n support
  • API-key auth
  • Workflow enumeration
  • Manual execution trigger
  • Execution status + logs

Install snippets

Open the detail page for ready-to-paste config for every major client.

Install Make (Integromat)

Setup snippets for Claude, Cursor, VS Code, Windsurf →

npx -y make-mcp-server

Install n8n (MCP archived)

Setup snippets for Claude, Cursor, VS Code, Windsurf →

npx -y @leonardsellem/n8n-mcp-server

FAQ

Make (Integromat) vs n8n (MCP archived): which MCP server should I use?

Pick Make (Integromat) when triggering existing make scenarios. Pick n8n (MCP archived) when triggering existing n8n workflows. Make (Integromat) is built for run make scenarios, while n8n (MCP archived) focuses on run n8n workflows.

Can I run both Make (Integromat) and n8n (MCP archived) 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. Make (Integromat)'s last verification: 2026-05-31. n8n (MCP archived)'s last verification: 2026-05-27. We refresh detail-page facts on every catalog rebuild.

More Make (Integromat) comparisons

Make (Integromat)vsZapierMake (Integromat)vsPipedreamMake (Integromat)vsIFTTT (MCP archived)Make (Integromat)vsActivepieces (MCP archived)

Browse all Automation & Workflows MCPs? See the full ranked list →