n8n-mcp-tools-expert

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

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Sebasarmas19/Chatbot-Reminder --skill n8n-mcp-tools-expert-sebasarmas19
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-mcp-tools-expert
Source: https://github.com/Sebasarmas19/Chatbot-Reminder/tree/main/n8n-skills/skills/n8n-mcp-tools-expert
Command: npx skills add https://github.com/Sebasarmas19/Chatbot-Reminder --skill n8n-mcp-tools-expert-sebasarmas19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building n8n workflows through the n8n-mcp MCP server requires choosing among 40+ tools with different nodeType formats, validation profiles, and operation types, and mistakes like wrong prefixes or oversized payloads cause errors and wasted tokens. ## Core Features & Use Cases - Tool Selection Guidance: Maps tasks to the right tools, such as search_nodes for discovery, get_node for configuration details, and validate_node for pre-deployment checks. - Format and Profile Rules: Explains the nodes-base.* versus n8n-nodes-base.* nodeType formats and the minimal, runtime, ai-friendly, and strict validation profiles. - Workflow Management Patterns: Covers n8n_create_workflow, n8n_update_partial_workflow with 17 operation types, smart branch/case parameters, AI connection types, and template deployment. - Use Case: When asked to add a Slack notification to a workflow, follow the documented search → get_node → validate_node → n8n_update_partial_workflow sequence with the correct nodeType format at each step. ## Quick Start Ask the AI to find and configure an n8n node, for example: search for the Slack node, show its standard configuration details, and validate a message-posting config with the runtime profile.

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 find and configure an n8n node with MCP tools?

Call search_nodes with a keyword to get the nodeType, then call get_node with that nodeType at standard detail to see operations and properties. Finish by running validate_node with the runtime profile before using the config in a workflow.

What is the difference between nodes-base.* and n8n-nodes-base.* nodeType formats?

Search and validation tools like get_node and validate_node use the short nodes-base.* prefix, while workflow tools like n8n_create_workflow require the full n8n-nodes-base.* prefix. search_nodes returns both formats as nodeType and workflowNodeType.

Which validation profile should I use for n8n node configs?

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 for production.

When should I use get_node standard versus full detail?

Use standard detail (the default, ~1-2K tokens) for most cases since it returns operations and essential properties. Reserve full detail (~3-8K tokens) for debugging complex configurations, and use docs mode for readable documentation instead.

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

Use smart parameters in n8n_update_partial_workflow addConnection operations: branch "true" or "false" for IF nodes and case numbers for Switch nodes. This avoids manual sourceIndex calculations for multi-output nodes.

Do n8n-mcp workflow tools work without an n8n API connection?

No. Tools like n8n_create_workflow, n8n_update_partial_workflow, and n8n_deploy_template require N8N_API_URL and N8N_API_KEY. Discovery and validation tools such as search_nodes, get_node, and validate_node work without API access.