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

왜 쓰나요

핵심 기능

Full-text search across 500+ n8n nodes with schemas
Workflow JSON validator — catches bad configs before deploy
Template library + fetchable JSON for starting points
Optional: manage workflows on a real n8n instance (create, update, trigger, audit)

라이브 데모

실제 사용 모습

n8n-mcp.replay ▶ 준비됨

0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-mcp"
      ]
    }
  }
}

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

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

{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-mcp"
      ]
    }
  }
}

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

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-mcp"
      ]
    }
  }
}

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

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-mcp"
      ]
    }
  }
}

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

~/.continue/config.json

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

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

~/.config/zed/settings.json

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

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

claude mcp add n8n-mcp -- npx -y n8n-mcp

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

사용 사례

실전 활용법: n8n-mcp

Build an n8n workflow from a plain-English description

👤 Ops engineers, indie hackers using n8n ⏱ ~20 min intermediate

언제 쓸까: You know what you want ('every new Typeform goes to Notion + Slack') but don't want to click through the n8n UI for 20 minutes.

사전 조건

n8n instance (cloud or self-hosted) — Any working n8n; needed only for deploy step, not for design
N8N_API_URL + N8N_API_KEY — n8n Settings → n8n API → create API key

흐름

Search nodes for each step

I want: Typeform webhook → parse → create Notion page → post to Slack. Search for the exact node types I need.✓ 복사됨

→ Node names + required credentials identified
Generate the workflow JSON

Generate a complete workflow with those 4 nodes wired in order. Use a template as a base if one matches.✓ 복사됨

→ Valid n8n workflow JSON
Validate and deploy

Validate the JSON with validate_workflow. Fix any errors. Then deploy to my n8n as a draft (not active).✓ 복사됨

→ Workflow appears in n8n UI in draft state

결과: A working n8n workflow, 10x faster than manual clicking, with validation catching misconfigs before you hit Run.

함정

Credentials have to be set up in n8n first — JSON references them by ID — Create credential entries in n8n UI before deploy; pass the credential IDs to the agent
Agent deploys as active and immediately fires on historical data — Always deploy inactive; activate manually after testing in n8n UI

Audit your n8n instance for broken or dangerous workflows

👤 Ops leads inheriting an n8n instance ⏱ ~30 min intermediate

언제 쓸까: You took over an n8n instance with 50 workflows, no docs. You need to know what's there and what's risky.

흐름

List all workflows

List every workflow with name, active status, last execution time, and node count.✓ 복사됨

→ Full inventory
Flag risky patterns

Find workflows with: no error handling, webhook triggers with no auth, HTTP Request nodes to random URLs, or shell command nodes.✓ 복사됨

→ Risk list with rationale
Check failure rates

For each active workflow, get last 20 executions. Compute failure rate. Flag anything >20%.✓ 복사됨

→ Broken workflow list

결과: A risk + health inventory — know what to fix, freeze, or delete.

함정

Disabling a workflow that other workflows depend on (via Execute Workflow node) — Before disabling, search other workflows for references to the target by ID

Start from a template and customize it

👤 New n8n users ⏱ ~15 min beginner

언제 쓸까: Someone has likely built something close to what you need — use that as a starting point.

흐름

Search templates

Find templates that do: 'sync a CSV to a database with deduplication'.✓ 복사됨

→ 3-5 candidate templates ranked by relevance
Fetch and adapt

Get the JSON for the top match. Adapt nodes to use my actual database (Postgres at host X) and my CSV source (S3 bucket Y).✓ 복사됨

→ Customized workflow JSON
Validate and deploy

Validate, then deploy as draft to my n8n.✓ 복사됨

→ Draft workflow in n8n

결과: A working workflow in 10 minutes by standing on someone else's shoulders.

함정

Templates use deprecated node versions — Check validate_workflow output for version warnings; swap in current nodes

조합

다른 MCP와 조합해 10배 효율

n8n-mcp + notion

Scaffold an n8n workflow that writes to a specific Notion database — look up the DB schema first

Look up my Notion 'Leads' database schema. Then build an n8n workflow that takes webhook input and creates matching entries.✓ 복사됨

n8n-mcp + linear

Auto-create Linear tickets for n8n workflow failures

Audit my n8n for workflows failing >20% of runs. For each, create a Linear bug.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
tools_documentation	tool_name?	Discover available tools	free
search_nodes	query, limit?	Find which n8n nodes match a need	free
get_node	node_type, mode?	Deep-dive on a specific node before wiring it	free
validate_node	node JSON	Check a single node config	free
validate_workflow	workflow JSON	Always — before any deploy	free
search_templates	query/keywords/nodes	Find prior art before building from scratch	free
get_template	template_id	Fetch a chosen template	free
create_workflow / update_workflow / delete_workflow	requires N8N_API_URL/KEY	Deploy or mutate on the real instance	1 n8n API call
trigger_workflow / get_executions	workflow_id, data?	Test a deployed workflow	1 n8n API call
audit_instance		Periodic instance review	multiple API calls

비용 및 제한

운영 비용

API 쿼터: Search/validate tools: unlimited (local data). Management tools: limited by your n8n instance's capacity.
호출당 토큰: Node schemas can be large (2-5k tokens); use get_node with mode='minimal' when you just need types
금액: Free MCP; n8n has a cloud tier ($20+/mo) or self-host for free
팁: Design fully with search/validate first (free). Only call create/update once you're sure — each deploy costs a quota slot on n8n cloud

보안

권한, 시크릿, 파급범위

자격 증명 저장: N8N_API_KEY in env var — treat like an admin token since it can create workflows

데이터 외부 송신: n8n-mcp MCP itself runs locally. Management tools call your N8N_API_URL.

문제 해결

자주 발생하는 오류와 해결

Management tools not appearing

N8N_API_URL or N8N_API_KEY not set. Management tools only register when both env vars are present at startup.

확인: echo $N8N_API_URL && echo $N8N_API_KEY | cut -c1-6

validate_workflow passes but n8n rejects at deploy

Likely a credential reference issue. Credentials are validated against names in your n8n instance — verify the credential names match exactly.

Workflow deploys but fails on first run with 'Node type not found'

You're using a node from a community package not installed on the n8n instance. Install it in n8n first or swap to a core node.

Template JSON uses deprecated node versions

After fetching, pass through validate_workflow — it flags deprecated versions. Upgrade nodes before deploy.

대안

n8n-mcp 다른 것과 비교

대안	언제 쓰나	단점/장점
Zapier MCP	Your team is on Zapier not n8n	Hosted only; less control but more polished integrations
Make (Integromat) MCP	Your team is on Make	Hosted; scenario model differs from n8n's graph model
Raw n8n REST API	You want code-level control from a custom script	No node catalog or validation — you're on your own for correctness

n8n-mcp