MCP HubMCP Hub
返回技能列表

n8n-mcp-tools-expert

davila7
更新于 Today
181 次查看
18,478
1,685
18,478
在 GitHub 上查看
mcpautomationdesign

关于

This Claude Skill provides expert guidance for using n8n-mcp MCP tools to build and manage n8n workflows. It helps developers search for nodes, validate configurations, access templates, and manage workflows with tool selection guidance and parameter formats. Use it when working with n8n-mcp's 40+ tools across categories like node discovery, workflow management, and template libraries.

快速安装

Claude Code

推荐
插件命令推荐
/plugin add https://github.com/davila7/claude-code-templates
Git 克隆备选方式
git clone https://github.com/davila7/claude-code-templates.git ~/.claude/skills/n8n-mcp-tools-expert

在 Claude Code 中复制并粘贴此命令以安装该技能

技能文档

n8n MCP Tools Expert

Master guide for using n8n-mcp MCP server tools to build workflows.


Tool Categories

n8n-mcp provides 40+ tools organized into categories:

  1. Node DiscoverySEARCH_GUIDE.md
  2. Configuration ValidationVALIDATION_GUIDE.md
  3. Workflow ManagementWORKFLOW_GUIDE.md
  4. Template Library - Search and access 2,653 real workflows
  5. Documentation - Get tool and node documentation

Quick Reference

Most Used Tools (by success rate)

ToolUse WhenSuccess RateSpeed
search_nodesFinding nodes by keyword99.9%<20ms
get_node_essentialsUnderstanding node operations91.7%<10ms
validate_node_operationChecking configurationsVaries<100ms
n8n_create_workflowCreating workflows96.8%100-500ms
n8n_update_partial_workflowEditing workflows (MOST USED!)99.0%50-200ms
validate_workflowChecking complete workflow95.5%100-500ms

Tool Selection Guide

Finding the Right Node

Workflow:

1. search_nodes({query: "keyword"})
2. get_node_essentials({nodeType: "nodes-base.name"})
3. [Optional] get_node_documentation({nodeType: "nodes-base.name"})

Example:

// Step 1: Search
search_nodes({query: "slack"})
// Returns: nodes-base.slack

// Step 2: Get details (18s avg between steps)
get_node_essentials({nodeType: "nodes-base.slack"})
// Returns: operations, properties, examples

Common pattern: search → essentials (18s average)

Validating Configuration

Workflow:

1. validate_node_minimal({nodeType, config: {}}) - Check required fields
2. validate_node_operation({nodeType, config, profile: "runtime"}) - Full validation
3. [Repeat] Fix errors, validate again

Common pattern: validate → fix → validate (23s thinking, 58s fixing per cycle)

Managing Workflows

Workflow:

1. n8n_create_workflow({name, nodes, connections})
2. n8n_validate_workflow({id})
3. n8n_update_partial_workflow({id, operations: [...]})
4. n8n_validate_workflow({id}) again

Common pattern: iterative updates (56s average between edits)


Critical: nodeType Formats

Two different formats for different tools!

Format 1: Search/Validate Tools

// Use SHORT prefix
"nodes-base.slack"
"nodes-base.httpRequest"
"nodes-base.webhook"
"nodes-langchain.agent"

Tools that use this:

  • search_nodes (returns this format)
  • get_node_essentials
  • get_node_info
  • validate_node_minimal
  • validate_node_operation
  • get_property_dependencies

Format 2: Workflow Tools

// Use FULL prefix
"n8n-nodes-base.slack"
"n8n-nodes-base.httpRequest"
"n8n-nodes-base.webhook"
"@n8n/n8n-nodes-langchain.agent"

Tools that use this:

  • n8n_create_workflow
  • n8n_update_partial_workflow
  • list_node_templates

Conversion

// search_nodes returns BOTH formats
{
  "nodeType": "nodes-base.slack",          // For search/validate tools
  "workflowNodeType": "n8n-nodes-base.slack"  // For workflow tools
}

Common Mistakes

❌ Mistake 1: Wrong nodeType Format

Problem: "Node not found" error

❌ get_node_essentials({nodeType: "slack"})  // Missing prefix
❌ get_node_essentials({nodeType: "n8n-nodes-base.slack"})  // Wrong prefix

✅ get_node_essentials({nodeType: "nodes-base.slack"})  // Correct!

❌ Mistake 2: Using get_node_info Instead of get_node_essentials

Problem: 20% failure rate, slow response, huge payload

❌ get_node_info({nodeType: "nodes-base.slack"})
// Returns: 100KB+ data, 20% chance of failure

✅ get_node_essentials({nodeType: "nodes-base.slack"})
// Returns: 5KB focused data, 91.7% success, <10ms

When to use get_node_info:

  • Debugging complex configuration issues
  • Need complete property schema
  • Exploring advanced features

Better alternatives:

  1. get_node_essentials - for operations list
  2. get_node_documentation - for readable docs
  3. search_node_properties - for specific property

❌ Mistake 3: Not Using Validation Profiles

Problem: Too many false positives OR missing real errors

Profiles:

  • minimal - Only required fields (fast, permissive)
  • runtime - Values + types (recommended for pre-deployment)
  • ai-friendly - Reduce false positives (for AI configuration)
  • strict - Maximum validation (for production)
❌ validate_node_operation({nodeType, config})  // Uses default

✅ validate_node_operation({nodeType, config, profile: "runtime"})  // Explicit

❌ Mistake 4: Ignoring Auto-Sanitization

What happens: ALL nodes sanitized on ANY workflow update

Auto-fixes:

  • Binary operators (equals, contains) → removes singleValue
  • Unary operators (isEmpty, isNotEmpty) → adds singleValue: true
  • IF/Switch nodes → adds missing metadata

Cannot fix:

  • Broken connections
  • Branch count mismatches
  • Paradoxical corrupt states
// After ANY update, auto-sanitization runs on ALL nodes
n8n_update_partial_workflow({id, operations: [...]})
// → Automatically fixes operator structures

❌ Mistake 5: Not Using Smart Parameters

Problem: Complex sourceIndex calculations for multi-output nodes

Old way (manual):

// IF node connection
{
  type: "addConnection",
  source: "IF",
  target: "Handler",
  sourceIndex: 0  // Which output? Hard to remember!
}

New way (smart parameters):

// IF node - semantic branch names
{
  type: "addConnection",
  source: "IF",
  target: "True Handler",
  branch: "true"  // Clear and readable!
}

{
  type: "addConnection",
  source: "IF",
  target: "False Handler",
  branch: "false"
}

// Switch node - semantic case numbers
{
  type: "addConnection",
  source: "Switch",
  target: "Handler A",
  case: 0
}

Tool Usage Patterns

Pattern 1: Node Discovery (Most Common)

Common workflow: 18s average between steps

// Step 1: Search (fast!)
const results = await search_nodes({
  query: "slack",
  mode: "OR",  // Default: any word matches
  limit: 20
});
// → Returns: nodes-base.slack, nodes-base.slackTrigger

// Step 2: Get details (~18s later, user reviewing results)
const details = await get_node_essentials({
  nodeType: "nodes-base.slack",
  includeExamples: true  // Get real template configs
});
// → Returns: operations, properties, metadata

Pattern 2: Validation Loop

Typical cycle: 23s thinking, 58s fixing

// Step 1: Validate
const result = await validate_node_operation({
  nodeType: "nodes-base.slack",
  config: {
    resource: "channel",
    operation: "create"
  },
  profile: "runtime"
});

// Step 2: Check errors (~23s thinking)
if (!result.valid) {
  console.log(result.errors);  // "Missing required field: name"
}

// Step 3: Fix config (~58s fixing)
config.name = "general";

// Step 4: Validate again
await validate_node_operation({...});  // Repeat until clean

Pattern 3: Workflow Editing

Most used update tool: 99.0% success rate, 56s average between edits

// Iterative workflow building (NOT one-shot!)
// Edit 1
await n8n_update_partial_workflow({
  id: "workflow-id",
  operations: [{type: "addNode", node: {...}}]
});

// ~56s later...

// Edit 2
await n8n_update_partial_workflow({
  id: "workflow-id",
  operations: [{type: "addConnection", source: "...", target: "..."}]
});

// ~56s later...

// Edit 3 (validation)
await n8n_validate_workflow({id: "workflow-id"});

Detailed Guides

Node Discovery Tools

See SEARCH_GUIDE.md for:

  • search_nodes (99.9% success)
  • get_node_essentials vs get_node_info
  • list_nodes by category
  • search_node_properties for specific fields

Validation Tools

See VALIDATION_GUIDE.md for:

  • Validation profiles explained
  • validate_node_minimal vs validate_node_operation
  • validate_workflow complete structure
  • Auto-sanitization system
  • Handling validation errors

Workflow Management

See WORKFLOW_GUIDE.md for:

  • n8n_create_workflow
  • n8n_update_partial_workflow (15 operation types!)
  • Smart parameters (branch, case)
  • AI connection types (8 types)
  • cleanStaleConnections recovery

Template Usage

Search Templates

// Search by keyword
search_templates({
  query: "webhook slack",
  limit: 20
});
// → Returns: 1,085 templates with metadata

// Get template details
get_template({
  templateId: 2947,  // Weather to Slack
  mode: "structure"  // or "full" for complete JSON
});

Template Metadata

Templates include:

  • Complexity (simple, medium, complex)
  • Setup time estimate
  • Required services
  • Categories and use cases
  • View counts (popularity)

Self-Help Tools

Get Tool Documentation

// List all tools
tools_documentation()

// Specific tool details
tools_documentation({
  topic: "search_nodes",
  depth: "full"
})

Health Check

// Verify MCP server connectivity
n8n_health_check()
// → Returns: status, features, API availability, version

Database Statistics

get_database_statistics()
// → Returns: 537 nodes, 270 AI tools, 2,653 templates

Tool Availability

Always Available (no n8n API needed):

  • search_nodes, list_nodes, get_node_essentials ✅
  • validate_node_minimal, validate_node_operation ✅
  • validate_workflow, get_property_dependencies ✅
  • search_templates, get_template, list_tasks ✅
  • tools_documentation, get_database_statistics ✅

Requires n8n API (N8N_API_URL + N8N_API_KEY):

  • n8n_create_workflow ⚠️
  • n8n_update_partial_workflow ⚠️
  • n8n_validate_workflow (by ID) ⚠️
  • n8n_list_workflows, n8n_get_workflow ⚠️
  • n8n_trigger_webhook_workflow ⚠️

If API tools unavailable, use templates and validation-only workflows.


Performance Characteristics

ToolResponse TimePayload SizeReliability
search_nodes<20msSmall99.9%
list_nodes<20msSmall99.6%
get_node_essentials<10ms~5KB91.7%
get_node_infoVaries100KB+80% ⚠️
validate_node_minimal<100msSmall97.4%
validate_node_operation<100msMediumVaries
validate_workflow100-500msMedium95.5%
n8n_create_workflow100-500msMedium96.8%
n8n_update_partial_workflow50-200msSmall99.0%

Best Practices

✅ Do

  • Use get_node_essentials over get_node_info (91.7% vs 80%)
  • Specify validation profile explicitly
  • Use smart parameters (branch, case) for clarity
  • Follow search → essentials → validate workflow
  • Iterate workflows (avg 56s between edits)
  • Validate after every significant change
  • Use includeExamples: true for real configs

❌ Don't

  • Use get_node_info unless necessary (20% failure rate!)
  • Forget nodeType prefix (nodes-base.*)
  • Skip validation profiles (use "runtime")
  • Try to build workflows in one shot (iterate!)
  • Ignore auto-sanitization behavior
  • Use full prefix (n8n-nodes-base.*) with search tools

Summary

Most Important:

  1. Use get_node_essentials, not get_node_info (5KB vs 100KB, 91.7% vs 80%)
  2. nodeType formats differ: nodes-base.* (search) vs n8n-nodes-base.* (workflows)
  3. Specify validation profiles (runtime recommended)
  4. Use smart parameters (branch="true", case=0)
  5. Auto-sanitization runs on ALL nodes during updates
  6. Workflows are built iteratively (56s avg between edits)

Common Workflow:

  1. search_nodes → find node
  2. get_node_essentials → understand config
  3. validate_node_operation → check config
  4. n8n_create_workflow → build
  5. n8n_validate_workflow → verify
  6. n8n_update_partial_workflow → iterate

For details, see:


Related Skills:

  • n8n Expression Syntax - Write expressions in workflow fields
  • n8n Workflow Patterns - Architectural patterns from templates
  • n8n Validation Expert - Interpret validation errors
  • n8n Node Configuration - Operation-specific requirements

GitHub 仓库

davila7/claude-code-templates
路径: cli-tool/components/skills/workflow-automation/n8n/n8n-mcp-tools-expert
anthropicanthropic-claudeclaudeclaude-code

相关推荐技能

content-collections

Content Collections 是一个 TypeScript 优先的构建工具,可将本地 Markdown/MDX 文件转换为类型安全的数据集合。它专为构建博客、文档站和内容密集型 Vite+React 应用而设计,提供基于 Zod 的自动模式验证。该工具涵盖从 Vite 插件配置、MDX 编译到生产环境部署的完整工作流。

查看技能

creating-opencode-plugins

该Skill为开发者创建OpenCode插件提供指导,涵盖命令、文件、LSP等25+种事件类型。它详细说明了插件结构、事件API规范及JavaScript/TypeScript实现模式,帮助开发者构建事件驱动的模块。适用于需要拦截操作、扩展功能或自定义AI助手行为的插件开发场景。

查看技能

sglang

SGLang是一个专为LLM设计的高性能推理框架,特别适用于需要结构化输出的场景。它通过RadixAttention前缀缓存技术,在处理JSON、正则表达式、工具调用等具有重复前缀的复杂工作流时,能实现极速生成。如果你正在构建智能体或多轮对话系统,并追求远超vLLM的推理性能,SGLang是理想选择。

查看技能

langchain

LangChain是一个用于构建LLM应用程序的框架,支持智能体、链和RAG应用开发。它提供多模型提供商支持、500+工具集成、记忆管理和向量检索等核心功能。开发者可用它快速构建聊天机器人、问答系统和自主代理,适用于从原型验证到生产部署的全流程。

查看技能