/ Verzeichnis / Playground / n8n-workflow-builder
← Alle Server ↗ GitHub
● Community makafeli ⚡ Sofort

n8n-workflow-builder

von makafeli · makafeli/n8n-workflow-builder

Build and run n8n workflows from natural language — 15 tools for create/activate/execute plus audit reports, connected to your self-hosted or cloud n8n.

n8n-workflow-builder (makafeli) is an MCP that talks to any n8n instance via its REST API. 15 tools cover the full workflow lifecycle: list, create with nodes, activate, execute, update, delete, plus execution history and security audits.

▶ Demo ansehen 📦 Installieren 💡 Anwendungsfälle

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

n8n-workflow-builder.replay ▶ bereit
0/0

Installieren

Wählen Sie Ihren 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
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "n8n-workflow-builder": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-workflow-builder"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "n8n-workflow-builder": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-workflow-builder"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "n8n-workflow-builder": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-workflow-builder"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "n8n-workflow-builder",
      "command": "npx",
      "args": [
        "-y",
        "n8n-workflow-builder"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json
{
  "context_servers": {
    "n8n-workflow-builder": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "n8n-workflow-builder"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: n8n-workflow-builder

Build an n8n workflow from a natural-language description

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

Wann einsetzen: You want a webhook → Slack → Google Sheet flow without dragging nodes.

Voraussetzungen
  • Running n8n instance with API enabled — docker run n8nio/n8n; enable N8N_API in env
  • API key — n8n Settings → API Keys
Ablauf
  1. 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'.✓ Kopiert
    → Workflow created with 3 nodes wired
  2. Activate
    Activate the workflow and return the production webhook URL.✓ Kopiert
    → Active + URL
  3. Smoke test
    Execute it once with a sample payload, then pull the execution log.✓ Kopiert
    → Successful run or identifiable failure

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

Fallstricke
  • 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
Kombinieren mit: google-sheets

Debug a failing n8n workflow from execution history

👤 Ops engineers maintaining automation ⏱ ~25 min intermediate

Wann einsetzen: A nightly workflow is failing and you want to triage from chat.

Ablauf
  1. Pull recent failures
    list_executions for workflow 'nightly-export' with status=error in the last 7 days.✓ Kopiert
    → List with dates and error snippets
  2. Inspect the worst one
    get_execution on the most recent failure. Show me the failing node's input and error.✓ Kopiert
    → Root cause clue
  3. Patch and redeploy
    Update the workflow to handle null values in the transform node. Then deactivate+activate to reload.✓ Kopiert
    → Subsequent runs succeed

Ergebnis: Outage resolved without opening the editor.

Run a security audit on your n8n workflows

👤 Security + ops teams ⏱ ~15 min intermediate

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

Ablauf
  1. Generate audit
    Use generate_audit on my n8n instance. Summarize findings into: credentials, webhook exposure, and node-permission issues.✓ Kopiert
    → Structured audit report
  2. File the risky items
    For each high-severity finding, create an issue in Linear/GitHub with remediation.✓ Kopiert
    → Issues created

Ergebnis: Quarterly security hygiene automation.

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

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.✓ Kopiert
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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
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

Kosten & Limits

Was der Betrieb kostet

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

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: N8N_API_KEY in env — grants full API access, scope accordingly
Datenabfluss: Only to your N8N_HOST

Fehlerbehebung

Häufige Fehler und Lösungen

401 Unauthorized

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

Prüfen: 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

Alternativen

n8n-workflow-builder vs. andere

AlternativeWann stattdessenKompromiss
Direct n8n REST APIYou're scripting, not chattingYou write the plumbing
Zapier MCPYou're on Zapier not n8nDifferent ecosystem; paid

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen