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

Why use it

Key features

17 tools: 8 workflow, 4 execution, 5 tag, 6 credential management
Multi-instance via .config.json (prod / staging / dev), gitignored by default
Single-instance via .env with N8N_HOST + N8N_API_KEY
CRUD + activate/deactivate/execute on workflows
Execution retry and log access for debugging

Live Demo

What it looks like in practice

n8n-workflow-builder-2.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-2": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-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-2": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-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-2": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-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-2": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-n8n-workflow-builder"
      ],
      "_inferred": true
    }
  }
}

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

~/.continue/config.json

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

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

~/.config/zed/settings.json

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

Add to context_servers. Zed hot-reloads on save.

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

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

Use Cases

Real-world ways to use mcp-n8n-workflow-builder

Create an n8n workflow from a prose description

👤 Ops and integrations folks ⏱ ~15 min intermediate

When to use: You want 'when a row is added to Airtable, send a Slack message' without clicking 15 nodes.

Prerequisites

n8n instance running with API enabled — Standard n8n install; get API key from Settings > API
N8N_HOST + N8N_API_KEY env vars (omit /api/v1 suffix) — Set in MCP config

Flow

Describe intent

Create a workflow 'airtable-to-slack': trigger on new row in Airtable base X table Y, post message to Slack channel #updates with the row's Name and Status.✓ Copied

→ Workflow created, URL returned
Verify nodes

get_workflow by id and tell me the node sequence.✓ Copied

→ Node chain matches intent
Activate

Activate the workflow.✓ Copied

→ Status: active

Outcome: A working workflow in minutes instead of tab-hopping in the n8n UI.

Pitfalls

Credentials created in wrong instance — Always include env name in prompts ('on staging instance...') with multi-instance config
Auto-generated node parameters miss some edge-case fields — Do one manual node review after creation; n8n is picky about operation parameters

Combine with: airtable · github

Debug a failed n8n execution

👤 Anyone running n8n in production ⏱ ~15 min intermediate

When to use: A workflow failed at 3 AM and you want to know what happened.

Flow

Find recent failures

list_executions status=error last 24h on prod.✓ Copied

→ Failure list
Inspect one

get_execution for the most recent — which node failed, with what error?✓ Copied

→ Node + stacktrace
Retry or fix

If transient, retry_execution. If code, propose a node change in the workflow JSON.✓ Copied

→ Action taken

Outcome: Root cause + either recovery or a patch proposal.

Combine with: sentry

Bulk-tag workflows and audit credentials

👤 Platform admins ⏱ ~30 min intermediate

When to use: You inherited an n8n instance and need to organize it.

Flow

List and classify workflows

list_workflows — classify each as {marketing, internal, ops, dead}.✓ Copied

→ Classification
Apply tags

Tag each per classification using create_tag + workflow update.✓ Copied

→ Tags applied
Audit credentials

list_credentials — flag any shared across environments or unused for >90 days.✓ Copied

→ Cleanup list

Outcome: A tidier, auditable n8n setup.

Combinations

Pair with other MCPs for X10 leverage

n8n-workflow-builder-2 + airtable

Design and deploy an Airtable→Slack flow

Design an n8n workflow that posts Slack when a new Deal is added to the Airtable CRM; include error handling.✓ Copied

n8n-workflow-builder-2 + sentry

Track n8n errors in Sentry

On workflow execution error, post to Sentry with workflow name and node data.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
list_workflows	filter?: object	Overview	1 API call
get_workflow	id: str	Inspect node graph	1 API call
create_workflow	name, nodes, connections, active?	Build a new workflow	1 API call (write)
update_workflow	id, nodes?, connections?, name?	Edit existing	1 API call (write)
delete_workflow	id	With confirmation	1 API call (destructive)
activate_workflow	id	Go-live	1 API call
deactivate_workflow	id	Pause without delete	1 API call
execute_workflow	id, data?	On-demand trigger	1 API call
list_executions	filter?	Monitoring	1 API call
get_execution	id	Post-mortem	1 API call
retry_execution	id	Transient failure recovery	1 API call
create_credential	name, type, data	Provision auth for nodes	1 API call (write)

Cost & Limits

What this costs to run

API quota: n8n instance's limits (self-hosted is unbounded)
Tokens per call: Workflow JSON can hit 5-20k for complex flows
Monetary: Free (n8n community) or paid (n8n Cloud)
Tip: Ask for summary (nodes + triggers) rather than full JSON dumps unless editing.

Security

Permissions, secrets, blast radius

Credential storage: N8N_API_KEY in env; multi-instance keys in .config.json (gitignored)

Data egress: All to your n8n instance

Never grant: Include N8N_HOST with /api/v1 suffix — cut the suffix or tool calls fail Share API key across dev/prod without tagging

n8n credentials hold secrets (DB passwords, API keys) — audit who has API key access.
The MCP can activate/execute workflows — treat it like admin-level n8n access.

Troubleshooting

Common errors and fixes

401 from n8n

API key invalid or expired; regenerate in Settings > API.

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

404 on create_workflow

N8N_HOST has /api/v1 appended; remove it.

Verify: Check config

Created workflow fails to activate

Node credentials missing. Create credentials first, then reference by id in the workflow.

Verify: get_workflow and look for null credential refs

Alternatives

mcp-n8n-workflow-builder vs others

Alternative	When to use it instead	Tradeoff
Zapier MCP	You're on Zapier instead	Different ecosystem; n8n is self-hostable, Zapier isn't
Native n8n AI nodes	You want AI inside a workflow, not outside	No external chat control

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills