n8n2mcp — n8n to MCP Bridge

n8n2mcp bridge server enabling AI agents to trigger and interact with n8n workflows via MCP — exposing n8n workflow webhooks as MCP tools, allowing agents to invoke complex automation pipelines, data transformations, and integrations built in n8n from within their tool-calling context.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Developer Tools n8n workflow-automation mcp-server bridge no-code integration
⚙ Agent Friendliness
70
/ 100
Can an agent use this?
🔒 Security
75
/ 100
Is it safe for agents?
⚡ Reliability
66
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
68
Documentation
70
Error Messages
68
Auth Simplicity
75
Rate Limits
72

🔒 Security

TLS Enforcement
85
Auth Strength
75
Scope Granularity
70
Dep. Hygiene
70
Secret Handling
75

n8n API key access. HTTPS. Community MCP. Scope workflow permissions.

⚡ Reliability

Uptime/SLA
70
Version Stability
65
Breaking Changes
65
Error Recovery
65
AF Security Reliability

Best When

A team already uses n8n for workflow automation and wants AI agents to invoke those workflows — bridging the rich n8n ecosystem into MCP tool calls without rebuilding integrations.

Avoid When

You don't have n8n or only need simple API calls — use dedicated MCP servers for individual services.

Use Cases

  • • Triggering n8n automation workflows from AI agents
  • • Calling complex multi-step integrations via simple MCP tool calls from orchestration agents
  • • Bridging AI agents with n8n's 400+ integration nodes from connectivity agents
  • • Running data transformation pipelines from data processing agents
  • • Automating business processes defined in n8n from enterprise agents
  • • Connecting AI agents to legacy systems via n8n adapters

Not For

  • • Teams without n8n self-hosted or cloud instance
  • • Simple single-API integrations (use dedicated MCP servers instead)
  • • Real-time streaming data (n8n webhooks are request/response)

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes ↗
SDK
No
Webhooks
Yes
OpenAPI Spec ↗

Authentication

Methods: api_key
OAuth: No Scopes: No

n8n API key required to access workflow definitions. Webhook URLs may have their own authentication. n8n instance URL must be configured.

Pricing

Model: freemium
Free tier: Yes
Requires CC: No

n8n is free to self-host. n8n Cloud has free tier. Community MCP bridge is free. Self-hosting costs apply.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • ⚠ n8n instance must be running and accessible from MCP server
  • ⚠ Workflow names/IDs must be configured in MCP — no auto-discovery in all implementations
  • ⚠ n8n workflow errors may not surface cleanly as MCP errors
  • ⚠ Community bridge — functionality depends on n8n API version
  • ⚠ Webhook-based workflows have latency from n8n processing overhead
  • ⚠ n8n self-hosted requires maintenance and updates

Alternatives

zapier-mcp make-mcp temporal-mcp

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for n8n2mcp — n8n to MCP Bridge.

$99
API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-06.

5220
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
♥
Community Powered