n8n-workflow-builder MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

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

Démo en direct

Aperçu en pratique

n8n-workflow-builder.replay ▶ prêt

0/0

Installer

Choisissez votre 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
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

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

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

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

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

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

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

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

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

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : n8n-workflow-builder

Build an n8n workflow from a natural-language description

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

Quand l'utiliser : You want a webhook → Slack → Google Sheet flow without dragging nodes.

Prérequis

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

Déroulement

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'.✓ Copié

→ Workflow created with 3 nodes wired
Activate

Activate the workflow and return the production webhook URL.✓ Copié

→ Active + URL
Smoke test

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

→ Successful run or identifiable failure

Résultat : A running automation in a few prompts instead of a morning in the editor.

Pièges

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

Combiner avec : google-sheets

Debug a failing n8n workflow from execution history

👤 Ops engineers maintaining automation ⏱ ~25 min intermediate

Quand l'utiliser : A nightly workflow is failing and you want to triage from chat.

Déroulement

Pull recent failures

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

→ 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.✓ Copié

→ Root cause clue
Patch and redeploy

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

→ Subsequent runs succeed

Résultat : Outage resolved without opening the editor.

Run a security audit on your n8n workflows

👤 Security + ops teams ⏱ ~15 min intermediate

Quand l'utiliser : Before going to prod, or quarterly, you want a compliance-style report.

Déroulement

Generate audit

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

→ Structured audit report
File the risky items

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

→ Issues created

Résultat : Quarterly security hygiene automation.

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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.✓ Copié

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.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler	Coût
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

Coût et limites

Coût d'exécution

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

Sécurité

Permissions, secrets, portée

Stockage des identifiants : N8N_API_KEY in env — grants full API access, scope accordingly

Sortie de données : Only to your N8N_HOST

Dépannage

Erreurs courantes et correctifs

401 Unauthorized

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

Vérifier : 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 autres

Alternative	Quand l'utiliser	Compromis
Direct n8n REST API	You're scripting, not chatting	You write the plumbing
Zapier MCP	You're on Zapier not n8n	Different ecosystem; paid

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills