mcp-n8n-builder

An MCP server that provides tools for programmatic creation, retrieval, updating, and deletion of n8n workflows, plus workflow activation/deactivation and listing/getting execution details. It validates node types against the target n8n instance and supports configurable output verbosity to reduce token usage.

Evaluated Mar 30, 2026 (22d ago)

Repo ↗ Automation mcp n8n workflow-automation ai-tools api-integration automation

⚙ 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

The README indicates use of N8N_HOST and N8N_API_KEY, but does not specify whether HTTPS-only is enforced, how errors log sensitive data (if at all), or whether scopes/least-privilege are supported. Dependency list is minimal in the manifest and does not provide vulnerability posture.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want an MCP-compatible agent to manage n8n workflows programmatically and you can supply N8N_HOST/N8N_API_KEY securely.

Avoid When

You need strong, documented retry/idempotency semantics for destructive operations, or you cannot control the token/response size when fetching large workflows.

Use Cases

• Letting AI agents build and modify n8n workflows via MCP tools
• Validating node types before creating/updating workflows to prevent n8n errors
• Automating workflow lifecycle management (CRUD + activate/deactivate)
• Inspecting workflow execution history and retrieving execution details

Not For

• Direct user-driven workflow editing UIs
• Environments where model/agent cannot safely hold and use n8n credentials
• Highly regulated deployments requiring documented compliance guarantees from this package

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: n8n API key via N8N_API_KEY environment variable (passed through to REST API calls)

OAuth: No Scopes: No

Auth is described as N8N_API_KEY; no finer-grained scope/granularity is documented in the provided README.

Pricing

Free tier: No

Requires CC: No

No pricing information provided; as an npm package, cost would depend on your n8n usage and any LLM/agent token costs.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Token usage can be high for large n8n workflow JSON; use OUTPUT_VERBOSITY=concise and consider per-tool verbosity overrides.
⚠ update_workflow requires the entire workflow structure (not a patch); agents must supply complete, validated payloads.
⚠ delete_workflow is permanent and cannot be undone—agents should be careful with confirmation/guardrails outside this package.

Alternatives

Use n8n REST API directly from your own backend/service (no MCP layer) Create a custom MCP server wrapper around n8n’s REST API Use official/community n8n automation SDKs (if available for your use case) rather than MCP

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-n8n-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.