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

왜 쓰나요

핵심 기능

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

라이브 데모

실제 사용 모습

n8n-workflow-builder-2.replay ▶ 준비됨

0/0

설치

클라이언트 선택

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

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

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

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

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

VS Code → Cline → MCP Servers → Edit

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

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

~/.codeium/windsurf/mcp_config.json

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

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

~/.continue/config.json

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

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

~/.config/zed/settings.json

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

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

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

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

사용 사례

실전 활용법: mcp-n8n-workflow-builder

Create an n8n workflow from a prose description

👤 Ops and integrations folks ⏱ ~15 min intermediate

언제 쓸까: You want 'when a row is added to Airtable, send a Slack message' without clicking 15 nodes.

사전 조건

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

흐름

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

→ Workflow created, URL returned
Verify nodes

get_workflow by id and tell me the node sequence.✓ 복사됨

→ Node chain matches intent
Activate

Activate the workflow.✓ 복사됨

→ Status: active

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

함정

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

함께 쓰기: airtable · github

Debug a failed n8n execution

👤 Anyone running n8n in production ⏱ ~15 min intermediate

언제 쓸까: A workflow failed at 3 AM and you want to know what happened.

흐름

Find recent failures

list_executions status=error last 24h on prod.✓ 복사됨

→ Failure list
Inspect one

get_execution for the most recent — which node failed, with what error?✓ 복사됨

→ Node + stacktrace
Retry or fix

If transient, retry_execution. If code, propose a node change in the workflow JSON.✓ 복사됨

→ Action taken

결과: Root cause + either recovery or a patch proposal.

함께 쓰기: sentry

Bulk-tag workflows and audit credentials

👤 Platform admins ⏱ ~30 min intermediate

언제 쓸까: You inherited an n8n instance and need to organize it.

흐름

List and classify workflows

list_workflows — classify each as {marketing, internal, ops, dead}.✓ 복사됨

→ Classification
Apply tags

Tag each per classification using create_tag + workflow update.✓ 복사됨

→ Tags applied
Audit credentials

list_credentials — flag any shared across environments or unused for >90 days.✓ 복사됨

→ Cleanup list

결과: A tidier, auditable n8n setup.

조합

다른 MCP와 조합해 10배 효율

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

n8n-workflow-builder-2 + sentry

Track n8n errors in Sentry

On workflow execution error, post to Sentry with workflow name and node data.✓ 복사됨

도구

이 MCP가 노출하는 것

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

비용 및 제한

운영 비용

API 쿼터: n8n instance's limits (self-hosted is unbounded)
호출당 토큰: Workflow JSON can hit 5-20k for complex flows
금액: Free (n8n community) or paid (n8n Cloud)
팁: Ask for summary (nodes + triggers) rather than full JSON dumps unless editing.

보안

권한, 시크릿, 파급범위

자격 증명 저장: N8N_API_KEY in env; multi-instance keys in .config.json (gitignored)

데이터 외부 송신: All to your n8n instance

절대 부여 금지: 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.

문제 해결

자주 발생하는 오류와 해결

401 from n8n

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

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

404 on create_workflow

N8N_HOST has /api/v1 appended; remove it.

확인: Check config

Created workflow fails to activate

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

확인: get_workflow and look for null credential refs

대안

mcp-n8n-workflow-builder 다른 것과 비교

대안	언제 쓰나	단점/장점
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

mcp-n8n-workflow-builder