n8n-workflow-builder MCP — Use Cases, Install & Live Demo

Why use it

Key features

Full workflow CRUD + lifecycle management
Execute workflows manually from the agent
Pull execution history and logs for debugging
Security audit via generate_audit

Live Demo

What it looks like in practice

n8n-workflow-builder.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "n8n-workflow-builder": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-workflow-builder"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "n8n-workflow-builder": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-workflow-builder"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "n8n-workflow-builder": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-workflow-builder"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "n8n-workflow-builder": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-workflow-builder"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "n8n-workflow-builder",
      "command": "npx",
      "args": [
        "-y",
        "n8n-workflow-builder"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "n8n-workflow-builder": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "n8n-workflow-builder"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add n8n-workflow-builder -- npx -y n8n-workflow-builder

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use n8n-workflow-builder

Build an n8n workflow from a natural-language description

👤 No-code PMs, solo founders, internal ops ⏱ ~20 min intermediate

When to use: You want a webhook → Slack → Google Sheet flow without dragging nodes.

Prerequisites

Running n8n instance with API enabled — docker run n8nio/n8n; enable N8N_API in env
API key — n8n Settings → API Keys

Flow

Describe the flow

Create an n8n workflow: when a webhook hits /signup, post the payload to Slack #signups and append a row to sheet 'Signups'.✓ Copied

→ Workflow created with 3 nodes wired
Activate

Activate the workflow and return the production webhook URL.✓ Copied

→ Active + URL
Smoke test

Execute it once with a sample payload, then pull the execution log.✓ Copied

→ Successful run or identifiable failure

Outcome: A running automation in a few prompts instead of a morning in the editor.

Pitfalls

Credentials aren't set on the newly-created nodes — MCP can't create secrets for you — add Slack/Google creds in n8n UI once, refer by name

Combine with: google-sheets

Debug a failing n8n workflow from execution history

👤 Ops engineers maintaining automation ⏱ ~25 min intermediate

When to use: A nightly workflow is failing and you want to triage from chat.

Flow

Pull recent failures

list_executions for workflow 'nightly-export' with status=error in the last 7 days.✓ Copied

→ List with dates and error snippets
Inspect the worst one

get_execution on the most recent failure. Show me the failing node's input and error.✓ Copied

→ Root cause clue
Patch and redeploy

Update the workflow to handle null values in the transform node. Then deactivate+activate to reload.✓ Copied

→ Subsequent runs succeed

Outcome: Outage resolved without opening the editor.

Run a security audit on your n8n workflows

👤 Security + ops teams ⏱ ~15 min intermediate

When to use: Before going to prod, or quarterly, you want a compliance-style report.

Flow

Generate audit

Use generate_audit on my n8n instance. Summarize findings into: credentials, webhook exposure, and node-permission issues.✓ Copied

→ Structured audit report
File the risky items

For each high-severity finding, create an issue in Linear/GitHub with remediation.✓ Copied

→ Issues created

Outcome: Quarterly security hygiene automation.

Combinations

Pair with other MCPs for X10 leverage

n8n-workflow-builder + google-sheets

Webhook-to-sheet automations built and monitored from chat

Create an n8n workflow that appends payloads to my 'Leads' sheet; verify it works end to end.✓ Copied

n8n-workflow-builder + sentry

Sentry alert → n8n workflow → incident response chain

When Sentry sees a spike on project X, trigger my n8n workflow 'incident-page' via execute_workflow.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
list_workflows		Overview	1 API call
get_workflow	id	Inspect nodes	1 API call
create_workflow	name, nodes[], connections	New automation	1 API call
execute_workflow	id, payload?	Manual trigger / test	n8n CPU + downstream
activate_workflow	id	Ship to prod	1 API call
deactivate_workflow	id	Maintenance / rollback	1 API call
update_workflow	id, changes	Patch nodes	1 API call
delete_workflow	id	Retire	1 API call
list_executions	workflow_id?, status?	Triage	1 API call
get_execution	execution_id	Root cause	1 API call
generate_audit		Security review	1 API call

Cost & Limits

What this costs to run

API quota: n8n itself has no API rate limit beyond your own server's capacity
Tokens per call: Workflow JSON can be large — 2-10k tokens per get_workflow on complex flows
Monetary: Free if self-hosted; n8n Cloud billed per exec
Tip: Use list_workflows first, avoid get_workflow on huge flows unless you need node details

Security

Permissions, secrets, blast radius

Credential storage: N8N_API_KEY in env — grants full API access, scope accordingly

Data egress: Only to your N8N_HOST

Troubleshooting

Common errors and fixes

401 Unauthorized

Wrong API key or key lacks permissions — regenerate in n8n UI

Verify: curl -H 'X-N8N-API-KEY: <key>' $N8N_HOST/api/v1/workflows

Workflow created but fails on execute

Nodes missing credentials — attach them in the UI after creation; MCP can't set secrets

execute_workflow hangs

Long-running flow — use activate + webhook trigger instead of sync execute

Alternatives

n8n-workflow-builder vs others

Alternative	When to use it instead	Tradeoff
Direct n8n REST API	You're scripting, not chatting	You write the plumbing
Zapier MCP	You're on Zapier not n8n	Different ecosystem; paid

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills