n8n-mcp-tools-expert

Guides selection and usage of n8n-mcp MCP tools for node discovery, validation, and workflow management.

2|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/mdc159/cbass --skill n8n-mcp-tools-expert-mdc159
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-mcp-tools-expert
Source: https://github.com/mdc159/cbass/tree/main/.claude/skills/n8n-mcp-tools-expert-v1.0.0
Command: npx skills add https://github.com/mdc159/cbass --skill n8n-mcp-tools-expert-mdc159

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building n8n workflows through the n8n-mcp MCP server fails frequently due to wrong tool selection, incorrect nodeType prefix formats, oversized payloads from get_node_info, and missing validation profiles, causing errors and wasted iterations. ## Core Features & Use Cases - Tool Selection Guidance: Maps 40+ MCP tools to tasks across node discovery, configuration validation, workflow management, templates, and documentation, with success rates and performance characteristics. - Format and Parameter Rules: Explains the critical nodeType format difference (nodes-base.* for search/validate tools vs n8n-nodes-base.* for workflow tools), validation profiles (minimal/runtime/ai-friendly/strict), and smart parameters (branch, case) for multi-output nodes. - Use Case: When building a Webhook-to-Slack workflow, follow the documented pattern: search_nodes to find the node, get_node_essentials for configuration details, validate_node_operation with the runtime profile, then create and iteratively update the workflow with n8n_update_partial_workflow. ## Quick Start Ask the assistant to search for an n8n node by keyword and show its essential configuration using the n8n-mcp tools.

Frequently Asked Questions about n8n-mcp-tools-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search for n8n nodes using MCP tools?

Use search_nodes with a keyword query, optional mode (OR, AND, FUZZY), and limit. It returns matching nodes with both nodeType formats, then call get_node_essentials on the result to get operations and configuration details.

What is the difference between get_node_essentials and get_node_info?

get_node_essentials returns about 5KB of focused configuration data with a 91.7% success rate in under 10ms, while get_node_info returns 100KB+ full schemas with a 20% failure rate. Use get_node_essentials for most cases and reserve get_node_info for debugging complex configurations.

Why does n8n-mcp return node not found errors?

The error usually comes from wrong nodeType prefix formats. Search and validation tools require the short prefix like nodes-base.slack, while workflow creation tools require the full prefix like n8n-nodes-base.slack. search_nodes returns both formats for conversion.

Which validation profile should I use for n8n node configurations?

Use the runtime profile for pre-deployment validation since it balances value and type checking. Use minimal for quick required-field checks, ai-friendly to reduce false positives on AI-generated configs, and strict only for production-grade validation.

Can n8n-mcp tools create workflows without the n8n API?

Discovery, validation, template, and documentation tools work without API access, but n8n_create_workflow, n8n_update_partial_workflow, and n8n_validate_workflow require N8N_API_URL and N8N_API_KEY. Workflow activation must always be done manually in the n8n UI.

How do I connect IF or Switch node outputs in n8n workflows?

Use smart parameters in n8n_update_partial_workflow instead of manual sourceIndex values. For IF nodes pass branch: "true" or branch: "false", and for Switch nodes pass case: 0, case: 1, and so on in the addConnection operation.