技能 n8n-mcp-tools-expert
📦

n8n-mcp-tools-expert

安全

Build n8n Workflows with MCP Tools

This skill provides expert guidance for using n8n-mcp MCP server tools to discover nodes, validate configurations, and manage workflows efficiently.

支援: Claude Codex Code(CC)
🥉 74 青銅
1

下載技能 ZIP

2

在 Claude 中上傳

前往 設定 → 功能 → 技能 → 上傳技能

3

開啟並開始使用

測試它

正在使用「n8n-mcp-tools-expert」。 Search for Slack-related nodes

預期結果:

Found nodes:
- nodes-base.slack (Slack node)
- nodes-base.slackTrigger (Slack Trigger)

Use get_node with nodes-base.slack to see operations like 'send', 'reaction', 'uploadFile', etc.

正在使用「n8n-mcp-tools-expert」。 Validate a webhook node configuration

預期結果:

Validation result: valid=true

The configuration is correct. You can use this node in your workflow.

正在使用「n8n-mcp-tools-expert」。 Create a simple webhook workflow

預期結果:

Workflow created with ID: abc123
Nodes: Webhook → Respond to Webhook

Use n8n_validate_workflow to verify, then activate with activateWorkflow operation.

安全審計

安全
v1 • 2/25/2026

Static analysis flagged 170 potential issues including external_commands (96), network (1), and env_access (1). After evaluating the actual content, all findings are FALSE POSITIVES. The backtick characters detected are markdown code formatting for tool names, not shell execution. The URL is a legitimate source reference. The API key reference is documentation about required configuration. This is a documentation file with example code snippets, not executable malicious code.

1
已掃描檔案
655
分析行數
3
發現項
1
審計總數
低風險問題 (3)
Static Scanner False Positives - Markdown Code Formatting
The static analyzer detected 96 instances of 'external_commands' (Ruby/shell backtick execution) at various lines in SKILL.md. These are FALSE POSITIVES. The backtick characters are markdown code formatting for tool names (e.g., `search_nodes`, `get_node`), not shell execution. This is a documentation file containing example code snippets.
Static Scanner False Positives - Documentation URL
The static analyzer detected a 'Hardcoded URL' at SKILL.md:4. This is a FALSE POSITIVE. The URL 'https://github.com/czlonkowski/n8n-skills/...' is a legitimate source reference documenting where the skill originates from.
Static Scanner False Positives - Configuration Documentation
The static analyzer detected 'env_access' (Generic API/secret keys) at SKILL.md:511. This is a FALSE POSITIVE. The line documents that N8N_API_URL and N8N_API_KEY environment variables are needed for certain tools - this is configuration documentation, not exposed secrets.
審計者: claude

品質評分

38
架構
100
可維護性
87
內容
50
社群
99
安全
96
規範符合性

你能建構什麼

Find and configure n8n nodes

Search for nodes by keyword, get detailed configuration options, and validate settings before building workflows.

Build workflows iteratively

Create workflows step-by-step using n8n_update_partial_workflow with intelligent error handling and validation.

Deploy from template library

Search 2700+ pre-built workflows, get details, and deploy directly to your n8n instance with auto-fix capabilities.

試試這些提示

Find a node for specific task
I need to [describe your task, e.g., send messages to Slack]. Use the n8n-mcp-tools skill to search for appropriate n8n nodes and show me how to configure the main settings.
Validate node configuration
Help me validate my n8n node configuration. I'm setting up a [node name] node with these settings: [describe config]. Use validate_node with the runtime profile to check for errors.
Create a new workflow
I want to create an n8n workflow that [describe workflow purpose]. Use n8n-mcp-tools to create the workflow with appropriate nodes and show me the structure.
Find and deploy a template
Search the n8n template library for workflows related to [describe use case, e.g., webhook processing]. Show me the top results and how to deploy one to my n8n instance.

最佳實務

  • Use get_node with detail: 'standard' (default) for most use cases - it covers 95% of needs while keeping token usage low
  • Specify validation profile explicitly - 'runtime' profile is recommended for pre-deployment checks
  • Use smart parameters like 'branch' and 'case' for IF and Switch nodes instead of manual sourceIndex calculations

避免

  • Using detail: 'full' by default - this returns 3-8K tokens and should only be used for debugging complex configurations
  • Forgetting the nodeType prefix - use 'nodes-base.*' for search/validate tools and 'n8n-nodes-base.*' for workflow tools
  • Trying to build entire workflows in one shot - use iterative updates with validation between each change

常見問題

What is the difference between nodes-base and n8n-nodes-base prefixes?
Use 'nodes-base.slack' for search, get_node, and validate_node tools. Use 'n8n-nodes-base.slack' for workflow creation and update tools. Using the wrong prefix will cause 'Node not found' errors.
Do I need an n8n API key to use this skill?
No. Node discovery, validation, and template search tools work without API access. Only workflow management tools (create, update, deploy) require N8N_API_URL and N8N_API_KEY.
How do I choose the right validation profile?
Use 'minimal' for quick checks, 'runtime' for pre-deployment (recommended), 'ai-friendly' for AI-generated configs, and 'strict' for production validation.
What is auto-sanitization in n8n workflow updates?
When you update a workflow, n8n automatically fixes certain issues like binary operator structures and missing IF/Switch metadata. It cannot fix broken connections or paradoxical states.
Can I use this skill to edit existing workflows?
Yes, use n8n_update_partial_workflow with operations like addNode, addConnection, or removeNode. The skill supports 17 different operation types.
How do smart parameters work for node connections?
Instead of manually calculating sourceIndex (0, 1, 2...), use semantic parameters like 'branch: true/false' for IF nodes or 'case: 0, 1, 2...' for Switch nodes.

開發者詳情

檔案結構

📄 SKILL.md