n8n-mcp
by mirza-javed
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| N8N_API_KEY | No | API key for your n8n instance. Required for n8n management tools. | |
| N8N_API_URL | No | The URL of your n8n instance API. Required for n8n management tools. | |
| DISABLED_TOOLS | No | Comma-separated list of tool names to disable (e.g., 'n8n_create_workflow,n8n_delete_workflow'). | |
| DISABLED_TOOL_OPERATIONS | No | Semicolon-separated list of tool:operation pairs to disable (e.g., 'n8n_workflow_versions:delete,rollback;n8n_executions:delete'). |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tools_documentationA | Get documentation for n8n MCP tools. Call without parameters for quick start guide. Use topic parameter to get documentation for specific tools. Use depth='full' for comprehensive documentation. |
| search_nodesA | Search n8n nodes by keyword with optional real-world examples. Pass query as string. Example: query="webhook" or query="database". Returns max 20 results. Use includeExamples=true to get top 2 template configs per node. |
| get_nodeA | Get node info with progressive detail levels and multiple modes. Detail: minimal (~200 tokens), standard (~1-2K, default), full (~3-8K). Modes: info (default), docs (markdown documentation), search_properties (find properties), versions/compare/breaking/migrations (version info). Use format='docs' for readable documentation, mode='search_properties' with propertyQuery for finding specific fields. |
| validate_nodeA | Validate n8n node configuration. Use mode='full' for comprehensive validation with errors/warnings/suggestions, mode='minimal' for quick required fields check. Example: nodeType="nodes-base.slack", config={resource:"channel",operation:"create"} |
| get_templateA | Get template by ID. Use mode to control response size: nodes_only (minimal), structure (nodes+connections), full (complete workflow). |
| search_templatesA | Search templates with multiple modes. Use searchMode='keyword' for text search, 'by_nodes' to find templates using specific nodes, 'by_task' for curated task-based templates, 'by_metadata' for filtering by complexity/setup time/services, 'patterns' for lightweight workflow pattern summaries mined from 2700+ templates. |
| validate_workflowA | Full workflow validation: structure, connections, expressions, AI tools. Returns errors/warnings/fixes. Essential before deploy. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| N8n Agents — CHAT AGENT PATTERNS | Chat agent patterns: shell + core + sub-agents |
| N8n Agents — EXAMPLES | Examples |
| N8n Agents — HUMAN REVIEW | Human review for agent tools |
| N8n Agents — MEMORY | Agent memory |
| N8n Agents — RAG | RAG (retrieval augmented generation) |
| N8n Agents — README | n8n Agents Skill |
| n8n-agents | Design n8n AI agents the right way. Use when building or editing any @n8n/n8n-nodes-langchain.* AI node — an AI Agent, LLM chain, Text Classifier, or Information Extractor — and whenever the user mentions AI agents, LLM with tools, tool calling, $fromAI, system prompts, agent memory, sessionId, structured/JSON output, output parser, RAG, vector store, a chat assistant/bot, or human-in-the-loop review. Covers Agent-vs-chain-vs-classifier choice, the model/memory/tools/outputParser slots, tool names/descriptions as prompt, structured output with autoFix, memory, RAG, human review, and chat topologies. |
| N8n Agents — STRUCTURED OUTPUT | Structured output |
| N8n Agents — SUBWORKFLOW AS TOOL | Sub-workflow as agent tool |
| N8n Agents — SYSTEM PROMPT | System prompts |
| N8n Agents — TOOLS | Agent tools |
| N8n Binary And Data — AGENT TOOL BINARY | Agent Tools and Binary |
| N8n Binary And Data — BINARY BASICS | Binary Basics |
| N8n Binary And Data — CDN REQUIREMENT | The CDN / URL Requirement for Chat Surfaces |
| N8n Binary And Data — MERGE FOR CONTEXT | Merge for Keeping Binary in Context |
| N8n Binary And Data — README | n8n Binary and Data Skill |
| n8n-binary-and-data | Handle files and binary data in n8n correctly. Use when working with files, images, PDFs, attachments, uploads or downloads, base64, vision/multimodal input, or when an AI agent needs a file as tool input or output — and whenever the user mentions $binary, binaryPropertyName, "read the PDF", "attach the file", "send the image", Merge losing binary, or a CDN for chat images. Covers the $binary vs $json split, reading/writing binary, keeping binary alive across transforms with Merge, the agent-tool binary boundary, and the CDN/URL requirement for chat surfaces. |
| N8n Code Javascript — BUILTIN FUNCTIONS | Built-in Functions - JavaScript Code Node |
| N8n Code Javascript — COMMON PATTERNS | Common Patterns - JavaScript Code Node |
| N8n Code Javascript — DATA ACCESS | Data Access Patterns - JavaScript Code Node |
| N8n Code Javascript — ERROR PATTERNS | Error Patterns - JavaScript Code Node |
| N8n Code Javascript — README | n8n Code JavaScript |
| n8n-code-javascript | Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with this.helpers / the $helpers global, working with dates using DateTime, troubleshooting Code node errors, choosing between Code node modes, or doing any custom data transformation in n8n. Always use this skill when a workflow needs a Code node — whether for data aggregation, filtering, API calls, format conversion, batch processing logic, or any custom JavaScript. Covers SplitInBatches loop patterns, cross-iteration data, pairedItem, and real-world production patterns. Also use when asked why a Code node or workflow is slow, which execution mode is faster, or how to cut per-item overhead on large datasets. EXCEPTION — for the AI-agent-callable Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode, a tool attached to an AI Agent), use the n8n-code-tool skill instead; it has a different runtime contract. |
| N8n Code Python — COMMON PATTERNS | Common Patterns - Python Code Node |
| N8n Code Python — DATA ACCESS | Data Access Patterns - Python Code Node |
| N8n Code Python — ERROR PATTERNS | Error Patterns - Python Code Node |
| N8n Code Python — README | n8n Code Python Skill |
| n8n-code-python | Write Python code in n8n Code nodes. Use when writing Python in n8n, using _input/_json/_node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes. Use this skill when the user specifically requests Python for an n8n Code node. Note — JavaScript is recommended for 95% of use cases — only use Python when the user explicitly prefers it or the task requires Python-specific standard library capabilities (regex, hashlib, statistics). EXCEPTION — for Python in the AI-agent-callable Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode), use the n8n-code-tool skill instead (input is _query, return must be a string). |
| N8n Code Python — STANDARD LIBRARY | Standard Library Reference - Python Code Node |
| N8n Code Tool — ERROR PATTERNS | Code Tool Error Patterns |
| N8n Code Tool — INPUT SCHEMA | Input Schema for Code Tool (Structured Mode) |
| N8n Code Tool — README | n8n Code Tool Skill |
| n8n-code-tool | Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the `query` input, returning a string result, defining an input schema for structured arguments (specifyInputSchema, jsonSchemaExample, DynamicStructuredTool), or troubleshooting errors like "Wrong output type returned", "No execution data available", "The response property should be a string, but it is an object", "Cannot assign to read only property 'name'", or an AI agent that refuses to call the tool. Covers the critical differences between Code node and Code Tool: return format (string vs `[{json:{...}}]`), unavailability of `$fromAI`/`$input`/`$helpers` in the Code Tool sandbox, naming rules for AI invocation, and when to use `toolWorkflow`/HTTP Request Tool instead. |
| N8n Error Handling — API WORKFLOWS | API Workflows |
| N8n Error Handling — ERROR WORKFLOWS | Workflow-Level Error Workflows |
| N8n Error Handling — NODE ERROR OUTPUTS | Per-Node Error Outputs |
| N8n Error Handling — README | n8n Error Handling Skill |
| N8n Error Handling — RESPONSE SHAPES | Response Shapes |
| n8n-error-handling | Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error branches/outputs, retries, retryOnFail, Respond to Webhook status codes, 4xx/5xx, Error Trigger, or "my workflow fails silently". Covers per-node error outputs and wiring, retry/self-healing, error-trigger workflows, and 4xx/5xx response shapes. |
| N8n Expression Syntax — COMMON MISTAKES | Common n8n Expression Mistakes |
| N8n Expression Syntax — EXAMPLES | n8n Expression Examples |
| N8n Expression Syntax — README | n8n Expression Syntax |
| n8n-expression-syntax | Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, mapping data between nodes, or referencing webhook data in workflows. Use this skill whenever configuring node fields that reference data from previous nodes — expressions are how n8n passes data between nodes, and getting the syntax wrong is the most common source of workflow errors. Also use when asked whether a complex expression hurts performance. |
| N8n Mcp Tools Expert — OPERATIONS GUIDE | Templates, Data Tables & Self-Help Tools Guide |
| N8n Mcp Tools Expert — README | n8n MCP Tools Expert |
| N8n Mcp Tools Expert — SEARCH GUIDE | Node Discovery Tools Guide |
| n8n-mcp-tools-expert | Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, managing credentials, auditing instance security, or using any n8n-mcp tool. Provides tool selection guidance, parameter formats, and common patterns. IMPORTANT — Always consult this skill before calling any n8n-mcp tool — it prevents common mistakes like wrong nodeType formats, incorrect parameter structures, and inefficient tool usage. If the user mentions n8n, workflows, nodes, or automation and you have n8n MCP tools available, use this skill first. |
| N8n Mcp Tools Expert — VALIDATION GUIDE | Configuration Validation Tools Guide |
| N8n Mcp Tools Expert — WORKFLOW GUIDE | Workflow Management Tools Guide |
| N8n Multi Instance — README | n8n Multi-Instance Skill |
| n8n-multi-instance | Use when an n8n-mcp account targets more than one n8n instance — i.e. the `n8n_instances` tool is available, the user mentions multiple n8n instances or environments (prod vs staging, several teams or clients), a workflow / datatable / credential / execution call returns an unexpected NOT_FOUND or reads data you don't recognize, or a credential create/update/delete is refused with an `INSTANCE_AMBIGUOUS` error. Covers choosing and switching which instance this MCP session targets, verifying the target before high-stakes work — credential writes above all — and recovering from misroutes and ambiguous-write fail-closes. Always consult this skill before operating on a specific instance, before any credential create/update/delete on a multi-instance account, or when a call hits the wrong/empty data or an `INSTANCE_AMBIGUOUS` error. |
| N8n Node Configuration — DEPENDENCIES | Property Dependencies Guide |
| N8n Node Configuration — NODE FAMILY GOTCHAS | Node Family Gotchas |
| N8n Node Configuration — OPERATION PATTERNS | Operation Patterns Guide |
| N8n Node Configuration — README | n8n Node Configuration |
| n8n-node-configuration | Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning common configuration patterns by node type. Always use this skill when setting up node parameters — it explains which fields are required for each operation, how displayOptions control field visibility, and when to use patchNodeField for surgical edits vs full node updates. |
| N8n Self Hosting — DAY2 | Day-2: update, back up, restore |
| N8n Self Hosting — QUEUE MODE | Queue mode |
| N8n Self Hosting — README | n8n Self-Hosting Skill |
| N8n Self Hosting — SECURITY | Secrets & hardening |
| N8n Self Hosting — SINGLE MODE | Single / regular mode |
| n8n-self-hosting | Deploy a production self-hosted n8n end-to-end to a fresh Linux VM over SSH, using Docker Compose behind a Caddy reverse proxy with automatic HTTPS. Use whenever the user wants to self-host, install, set up, provision, or deploy n8n on their own server/VPS/box (Hetzner, DigitalOcean, AWS EC2, bare metal, etc.) — in either single/regular mode or queue mode with workers — or to update, back up, restore, or harden such an instance. This is for SELF-HOSTED n8n (Docker), not n8n Cloud and not building workflows. The skill makes the agent ask single-vs-queue first, collect the domain/SSH/timezone inputs, generate fresh secrets on the box, and bring the stack up with TLS. Trigger on "deploy n8n", "self-host n8n", "install n8n on my server", "n8n docker compose", "n8n queue mode / workers / scaling", "n8n reverse proxy / SSL", or "back up / update my n8n". |
| N8n Subworkflows — NAMING AND DISCOVERY | Naming and discovery |
| N8n Subworkflows — README | n8n Sub-workflows Skill |
| n8n-subworkflows | Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over ~10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs, waitForSubWorkflow, mode each vs all, or exposing a workflow as an agent tool. Covers typed sub-workflow inputs, all-vs-each execution, verb-first naming for discovery, stateless vs stateful design, and splitting by input shape. |
| N8n Subworkflows — SUBWORKFLOW PATTERNS | Sub-workflow patterns |
| N8n Validation Expert — ERROR CATALOG | Error Catalog |
| N8n Validation Expert — FALSE POSITIVES | False Positives Guide |
| N8n Validation Expert — README | n8n Validation Expert |
| N8n Validation Expert — REVIEW CHECKLIST | Workflow Review Checklist |
| n8n-validation-expert | Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities. Consult this skill whenever a validate_node or validate_workflow call returns errors or warnings — it knows which warnings are false positives and which errors need real fixes. |
| N8n Workflow Patterns — README | n8n Workflow Patterns |
| n8n-workflow-patterns | Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, batch processing, or scheduled tasks. Always consult this skill when the user asks to create, build, or design an n8n workflow, automate a process, or connect services — even if they don't explicitly mention 'patterns'. Covers webhook, API, database, AI, batch processing, and scheduled automation architectures. Also use when optimizing a slow workflow or speeding up large-item-count processing (node count, batchSize, all-items vs per-item). |
| N8n Workflow Patterns — Ai Agent Workflow | AI Agent Workflow Pattern |
| N8n Workflow Patterns — Database Operations | Database Operations Pattern |
| N8n Workflow Patterns — Http Api Integration | HTTP API Integration Pattern |
| N8n Workflow Patterns — Scheduled Tasks | Scheduled Tasks Pattern |
| N8n Workflow Patterns — Webhook Processing | Webhook Processing Pattern |
| Using N8n Mcp Skills — README | Using n8n-mcp Skills (Router) |
| using-n8n-mcp-skills | Use when building, editing, validating, testing, or debugging an n8n workflow through the n8n-mcp MCP server — designing a flow, configuring a node, writing an expression or Code node, wiring credentials, or fixing one that misbehaves. The entry-point skill for the n8n-mcp-skills pack: it routes you to the right specialist skill, gives working knowledge of every n8n-mcp tool from turn one, and states the rules that keep workflows from breaking in production. Always consult it first on any n8n, workflow, node, or automation task — even a quick one-off, and even when the user names no skill — because n8n's surface drifts between versions and the specialist skills prevent silent failures. |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mirza-javed/n8n-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server