Skip to main content

MCP Tools Expert

HIGHEST PRIORITY SKILL. This skill covers every MCP tool provided by the n8n-mcp server. When in doubt about which tool to use, start here.
Master guide for using n8n-mcp MCP server tools to build workflows.

Tool Categories

Node Discovery

search_nodes, get_node — Find and understand 800+ nodes

Validation

validate_node, validate_workflow — Check configurations before deployment

Workflow Management

n8n_create_workflow, n8n_update_partial_workflow, n8n_deploy_template, n8n_workflow_versions

Templates

search_templates, get_template — Access 2,700+ real workflows

Most Used Tools

Tool Selection Guide

Finding the Right Node

Common pattern: search_nodesget_node (18s average between steps)

Validating a Configuration

Managing Workflows

Critical: nodeType Format Differences

Two different nodeType formats are used by different tools. Using the wrong format causes “Node not found” errors.

Validation Profiles

Choose the right profile for your development stage:

get_node Detail Levels

get_node Operation Modes

Workflow Management — All 17 Operation Types

n8n_update_partial_workflow is the most-used tool in the system (38,287 uses, 99.0% success rate).

Smart Parameters for Connections

Instead of computing sourceIndex manually, use semantic names:

Intent Parameter

Always include intent for better tool responses:

AI Connection Types

All 8 AI connection types are supported via sourceOutput:

Template Usage

Auto-Sanitization System

Auto-sanitization runs on ALL nodes during ANY workflow update. You do not need to manually fix operator structures. What it fixes automatically:
  • Binary operators (equals, contains, greaterThan, etc.) → removes singleValue
  • Unary operators (isEmpty, isNotEmpty, true, false) → adds singleValue: true
  • IF v2.2+ nodes → adds complete conditions.options metadata
  • Switch v3.2+ nodes → adds complete conditions.options for all rules
What it cannot fix:
  • Broken connections (references to non-existent nodes)
  • Branch count mismatches (3 Switch rules but only 2 outputs)
  • Paradoxical corrupt states

Version Control

Tool Availability

No n8n API connection needed:
  • search_nodes, get_node
  • validate_node, validate_workflow
  • search_templates, get_template
  • tools_documentation, ai_agents_guide
  • n8n_health_check

Common Tool Usage Patterns

From real telemetry data:
Workflows are built iteratively, not in one shot. Expect multiple rounds of edit → validate → fix. This is normal and expected behavior.

Complete Workflow Example

Self-Help Tools

Best Practices

Do

  • Use get_node({detail: "standard"}) by default
  • Specify profile: "runtime" explicitly
  • Use smart parameters (branch, case)
  • Include intent in workflow updates
  • Build iteratively (56s avg between edits)
  • Validate after every significant change
  • Use includeExamples: true for real configs

Don't

  • Use detail: "full" unless debugging (wastes tokens)
  • Forget the nodes-base.* prefix with search/validate tools
  • Use the full n8n-nodes-base.* prefix with search/validate tools
  • Skip validation profiles
  • Try to build in one shot
  • Manually fix auto-sanitization issues
  • Forget to activate after building