n8n-workflow-builder MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

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

라이브 데모

실제 사용 모습

n8n-workflow-builder.replay ▶ 준비됨

0/0

설치

클라이언트 선택

~/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
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

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

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

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

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

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

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

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

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

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

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

context_servers에 추가. 저장 시 Zed가 핫 리로드.

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

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: n8n-workflow-builder

Build an n8n workflow from a natural-language description

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

언제 쓸까: You want a webhook → Slack → Google Sheet flow without dragging nodes.

사전 조건

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

흐름

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'.✓ 복사됨

→ Workflow created with 3 nodes wired
Activate

Activate the workflow and return the production webhook URL.✓ 복사됨

→ Active + URL
Smoke test

Execute it once with a sample payload, then pull the execution log.✓ 복사됨

→ Successful run or identifiable failure

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

함정

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

함께 쓰기: google-sheets

Debug a failing n8n workflow from execution history

👤 Ops engineers maintaining automation ⏱ ~25 min intermediate

언제 쓸까: A nightly workflow is failing and you want to triage from chat.

흐름

Pull recent failures

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

→ 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.✓ 복사됨

→ Root cause clue
Patch and redeploy

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

→ Subsequent runs succeed

결과: Outage resolved without opening the editor.

Run a security audit on your n8n workflows

👤 Security + ops teams ⏱ ~15 min intermediate

언제 쓸까: Before going to prod, or quarterly, you want a compliance-style report.

흐름

Generate audit

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

→ Structured audit report
File the risky items

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

→ Issues created

결과: Quarterly security hygiene automation.

조합

다른 MCP와 조합해 10배 효율

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.✓ 복사됨

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.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
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

비용 및 제한

운영 비용

API 쿼터: n8n itself has no API rate limit beyond your own server's capacity
호출당 토큰: Workflow JSON can be large — 2-10k tokens per get_workflow on complex flows
금액: Free if self-hosted; n8n Cloud billed per exec
팁: Use list_workflows first, avoid get_workflow on huge flows unless you need node details

보안

권한, 시크릿, 파급범위

자격 증명 저장: N8N_API_KEY in env — grants full API access, scope accordingly

데이터 외부 송신: Only to your N8N_HOST

문제 해결

자주 발생하는 오류와 해결

401 Unauthorized

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

확인: 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

대안

n8n-workflow-builder 다른 것과 비교

대안	언제 쓰나	단점/장점
Direct n8n REST API	You're scripting, not chatting	You write the plumbing
Zapier MCP	You're on Zapier not n8n	Different ecosystem; paid

n8n-workflow-builder