mcp-n8n-workflow-builder

Provides an MCP server that lets an AI agent (e.g., Claude Desktop/Cursor IDE) create, manage, and monitor n8n workflows via natural language, including multi-instance routing across multiple n8n environments.

Evaluated Mar 30, 2026 (21d ago)

Homepage ↗ Repo ↗ Automation mcp n8n workflow-automation ai-automation cursor-ide claude-desktop natural-language multi-instance developer-tools

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Uses n8n API keys per environment and claims to avoid logging secrets and to encrypt credentials via n8n API. Scope granularity and transport enforcement are not fully demonstrated; strong assurances (audits, CVE status, verified TLS enforcement) are not provided in the supplied content.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want an agent-driven workflow builder inside an IDE via MCP, especially when you need to manage multiple n8n environments.

Avoid When

You cannot securely manage n8n API keys/configuration or you require strict guarantees about error semantics/idempotency for destructive operations.

Use Cases

• Generate n8n workflows from natural language requirements
• Manage workflow lifecycle (create/update/activate/deactivate/delete) across dev/staging/prod
• Trigger and debug executions (list/get/retry)
• Organize workflows with tags
• Manage n8n credential types/schemas and perform credential create/update/delete flows

Not For

• Replacing n8n’s native UI for users who require only manual, no-agent changes
• Implementations needing a first-class public REST API/SDK for end-customer integration (this is primarily an MCP tool for IDE/agents)
• High-assurance production security programs that require formal audits/verification beyond README claims

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: n8n_api_key

OAuth: No Scopes: No

Authentication is done via per-environment n8n API keys provided in .config.json or .env. No OAuth flow is described; scope granularity is not documented.

Pricing

Free tier: No

Requires CC: No

No pricing information provided; appears distributed via npm under MIT license.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Destructive operations (delete) require extra caution; no formal guardrails are described besides user guidance.
⚠ n8n base URL formatting matters (avoid adding /api/v1 suffix).
⚠ Activation may fail if a trigger node is missing or incompatible with the described n8n version.
⚠ Multi-instance routing depends on correct environment configuration; misrouting could affect the wrong n8n instance.

Alternatives

Use n8n’s built-in workflow editor plus export/import for migration Call n8n REST API directly (e.g., via your own scripts) Use an MCP server you build on top of n8n APIs with custom tooling and stricter controls Low-code automation platforms if n8n-specific workflow generation is not required

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-n8n-workflow-builder.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

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