IonBin
All pages
Search

n8n

Workflow automation
DataOps Automation hub MCPAPI/CLIFile import

Independent review. Unpaid; no partnership with n8n. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.

Workflow automation with a no-license-fee self-hosted Community Edition and paid Cloud plans. The MCP Server Trigger exposes connected tools and workflows to MCP clients. Self-hosting still requires infrastructure, maintenance and compliance with n8n's license.

The Ion perspective

The five-point review

Judgment, not a score. Documentation checked 2026-10-18.

Value
Workflow automation with a no-license-fee self-hosted Community Edition and paid Cloud plans. The MCP Server Trigger exposes connected tools and workflows to MCP clients. Self-hosting still requires infrastructure, maintenance and compliance with n8n's license.
Differentiation
Documented fit: Technical teams wanting control; Agent workflows with custom steps. Uniqueness is not established.
Replaceability and switching
Compare Make, Zapier. Not drop-in replacements. Export completeness and migration effort remain unverified.
Ease and technical aptitude
Consider the fit limits: Teams that want zero setup. Setup effort has not been scored.
Interoperability and portability
See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.

Connections: MCP connections · APIs · Portability and vendor lock-in.

Best for
  • Technical teams wanting control
  • Agent workflows with custom steps
Not for
  • Teams that want zero setup

Top use cases

  • Expose n8n workflows as tools to MCP clients with the MCP Server Trigger node source ↗
  • Self-host n8n with Docker on your own infrastructure source ↗
  • Import and export workflows as JSON files source ↗

In depth

Plans

Displayed EUR prices with annual billing: Cloud Starter €20/month for 2,500 executions, Pro €50/month for 10,000, and self-hosted Business €667/month for 40,000. Enterprise is quoted. Community has no license fee, but hosting and external model/service usage can cost extra. source ↗

Self-hosting and licensing

Community is covered by the Sustainable Use License for permitted internal business, personal and noncommercial use; it is not an unrestricted hosting-resale license. Keep the instance updated and review the terms before embedding or reselling a service. source ↗

Workflow portability

JSON imports move workflow definitions. Exported files can contain credential names and IDs, and HTTP nodes can contain authentication headers. Inspect and remove sensitive values before sharing; reconnect and test the required credentials in the destination. source ↗

How to use it with AI

How n8n connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.

PlatformMCP / connectorAPI (agent-written code)BrowserUpload / export
Claude (incl. Claude Code) Not documented n8n has an official MCP server and Claude (incl. Claude Code) supports MCP, but n8n's docs don't name this pairing. Auth setup may differ. n8n MCP docs ↗Claude (incl. Claude Code) MCP docs ↗ Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands n8n publishes an API, but this pairing still needs network, authentication and execution-scope checks. n8n API ↗Claude (incl. Claude Code) docs ↗ Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). n8n is a web app; the pairing itself is not documented. Claude (incl. Claude Code) browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. n8n's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. n8n file docs ↗Claude (incl. Claude Code) file docs ↗
OpenAI Codex Not documented n8n has an official MCP server and OpenAI Codex supports MCP, but n8n's docs don't name this pairing. Auth setup may differ. n8n MCP docs ↗OpenAI Codex MCP docs ↗ Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces n8n publishes an API, but this pairing still needs network, authentication and execution-scope checks. n8n API ↗OpenAI Codex docs ↗ Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. n8n is a web app; the pairing itself is not documented. OpenAI Codex browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. n8n's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. n8n file docs ↗OpenAI Codex file docs ↗
Google Antigravity Not documented n8n has an official MCP server and Google Antigravity supports MCP, but n8n's docs don't name this pairing. Auth setup may differ. n8n MCP docs ↗Google Antigravity MCP docs ↗ Not documented Google Antigravity: Agents edit code and run tasks n8n publishes an API, but this pairing still needs network, authentication and execution-scope checks. n8n API ↗Google Antigravity docs ↗ Inferred The /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. n8n is a web app; the pairing itself is not documented. Google Antigravity browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. n8n's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. n8n file docs ↗Google Antigravity file docs ↗

Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.

Agent compatibility

Automation hub MCPAPI/CLIFile import
LevelStatusDetail / source
Native connector / MCPYes Official docs ↗ — supports SSE and Streamable HTTP, not stdio; expose workflows using attached workflow-tool nodes.
API / CLIYes Official docs ↗ — available on paid Cloud plans and all self-hosted editions; excluded from the Cloud free trial.
Browser / manualNo Browser access is recorded alongside a documented programmatic route.
File upload / importYes Official docs ↗ — import/export workflow JSON; review credentials and headers before sharing.

Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.

Appears in these proposed stacks

Connection capabilities to compare

An official MCP server is documented for this tool. These platforms separately document MCP client support: ChatGPT, Claude, Cursor, Gemini (Google), Google Antigravity, Grok, Grok Bot, Lindy, LM Studio, Mistral Vibe, OpenAI Codex. This inventory does not establish compatible transport, authentication or actions for a pairing. Check the connection matrix and linked sources.

Workflows using this tool

Explained in the wiki

Review

No long-form review yet. Verdict is based on research, not hands-on testing.

Alternatives

Make

Workflow automation

Visual builder for multi-step automation scenarios across apps, billed in credits. A hosted MCP server lets AI clients such as Claude and ChatGPT run scenarios, and scenarios can be exported and imported as JSON blueprints.

Automation hub MCPAPI/CLIFile import
Ops

Zapier

Workflow automation

App-to-app automation across what Zapier says are 9,000+ apps, with Zaps, Tables and Forms. Zapier MCP lets AI assistants take actions (Zapier cites 40,000+); each successful MCP call uses two tasks from your plan.

Automation hub MCPAPI/CLIFile import
Ops