n8n-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_MODE | No | Mode for MCP communication | stdio |
| LOG_LEVEL | No | Logging level for the server | error |
| N8N_API_KEY | No | API key for n8n authentication | |
| N8N_API_URL | No | URL of the n8n instance API | |
| DISABLE_CONSOLE_OUTPUT | No | Disable console output | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
n8n-mcp provides n8n node documentation, validation and workflow management tools. tools_documentation() gives the overview. Choose nodes native first, taking the first option that does the job:
The service's own node (Slack, Google Sheets, Postgres, ...). Use HTTP Request only when no node covers the operation.
A native node for the job: Edit Fields (Set), Filter, IF, Switch, Merge, Aggregate, Summarize, Remove Duplicates, Sort, Limit, Split Out, Date & Time, Compare Datasets.
A short expression in that node's field; see tools_documentation({topic: "expression_helpers"}).
A Code node, only for: loops or recursion that per-item execution and Loop Over Items cannot express, state across runs, parsing no node handles, external libraries, heavy all-items work on queue-mode workers, or one short Code node that replaces four or more glue nodes. An expression with a function body or several statements counts as code: use a Code node for it, not a long expression. When a Code node is the right choice, start its notes with "Why Code:" and the reason; validate_workflow then does not suggest a native node for it. Call get_node with detail "standard" before configuring a node: its options list many settings that make a Code node unnecessary.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| 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_nodeB | 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. |
| n8n_create_workflowA | Create workflow. Requires: name, nodes[], connections{}. Created inactive. Returns workflow with ID. |
| n8n_get_workflowA | Get workflow by ID with different detail levels. n8n has a draft/publish model: the workflow body holds the draft (latest edits); use mode='active' to see the published graph that is actually running. Modes: 'full' (draft + metadata), 'details' (full + execution stats), 'active' (published graph only), 'structure' (nodes/connections topology), 'filtered' (full config of only the nodes named in nodeNames - use to read one heavy node without the whole workflow), 'minimal' (id/name/active/tags). |
| n8n_update_full_workflowA | Full workflow update. Requires complete nodes[] and connections{}. For incremental use n8n_update_partial_workflow. |
| n8n_update_partial_workflowA | Update workflow incrementally with diff operations. Types: addNode, removeNode, updateNode, patchNodeField, moveNode, enable/disableNode, addConnection, removeConnection, rewireConnection, cleanStaleConnections, replaceConnections, updateSettings, updateName, setNodeGroups, add/removeTag, activate/deactivateWorkflow, transferWorkflow, moveToFolder. patchNodeField requires fieldPath (dot path, e.g. "parameters.jsCode") and patches: [{find, replace}]. setNodeGroups replaces all canvas groups: [{name, nodeNames|nodeIds}] (or [] to ungroup). moveToFolder moves the workflow into a folder (n8n 2.32+): {parentFolderId: folder ID or null for project root}. See tools_documentation("n8n_update_partial_workflow", "full") for details. |
| n8n_delete_workflowA | Permanently delete a workflow. This action cannot be undone. |
| n8n_list_workflowsA | List workflows (minimal metadata only). Returns id/name/active/dates/tags. Check hasMore/nextCursor for pagination. |
| n8n_validate_workflowB | Validate workflow by ID. Checks nodes, connections, expressions. Returns errors/warnings/suggestions. |
| n8n_autofix_workflowA | Automatically fix common workflow validation errors. Preview fixes or apply them. Fixes expression format, typeVersion, error output config, webhook paths, connection structure issues (numeric keys, invalid types, ID-to-name, duplicates, out-of-bounds indices). |
| n8n_test_workflowA | Run a workflow. method=auto (default) triggers it over HTTP through its webhook/form/chat trigger. Workflows without such a trigger need n8n's MCP server: method=prepare lists the nodes that need pinned data, method=pinned runs the workflow with that data, method=direct starts a run with optional inputs. The official methods need N8N_MCP_ACCESS_TOKEN and the workflow's "Available in MCP" setting (exposeToMcp: true enables it after you confirm with the user). |
| n8n_executionsA | Manage workflow executions: get details, list, or delete. Use action='get' with id for execution details, action='list' (the default) for listing executions, action='delete' to remove execution record. |
| n8n_evaluationsA | Run and read evaluation test runs for a workflow. Reading requires n8n >= 2.30, run/cancel require n8n >= 2.32, and the API key must be created on the matching release to carry the testRun scopes; run/cancel also need the key owner to hold workflow:execute on the workflow. Actions: list_runs=list runs for a workflow, get_run=single run with aggregated metrics, list_cases=per-case results (paginate - cases can be large), run=trigger a run on a workflow with an evaluation trigger, cancel=stop a running run. |
| n8n_health_checkA | Check n8n instance health and API connectivity. Use mode='diagnostic' for detailed troubleshooting with env vars and tool status. |
| n8n_workflow_versionsA | Manage workflow version history, rollback, comparison, and cleanup. Six modes:
Two sources:
|
| n8n_deploy_templateA | Deploy a workflow template from n8n.io directly to your n8n instance. Deploys first, then auto-fixes common issues (expression format, typeVersions). Returns workflow ID, required credentials, and fixes applied. |
| n8n_manage_datatableA | Manage n8n data tables, rows and columns. Actions: createTable, listTables, getTable, updateTable, deleteTable, getRows, insertRows, updateRows, upsertRows, deleteRows, addColumn, deleteColumn, renameColumn. The column actions run through n8n's own MCP server (N8N_MCP_ACCESS_TOKEN, n8n 2.34+) because the public API cannot change a table's columns after creation; everything else uses the public API. |
| n8n_manage_foldersA | Manage workflow folders (n8n 2.19+; folders need a registered Community instance or higher). Actions: create, list, get, rename, move, delete. projectId defaults to 'personal' (the calling user's personal project). Place workflows into folders via n8n_create_workflow's parentFolderId or the moveToFolder operation of n8n_update_partial_workflow (both n8n 2.32+). Note: n8n's API cannot report which folder a workflow is in - folder contents are visible only as counts. |
| n8n_manage_credentialsA | Manage n8n credentials. Actions: list, get, create, update, delete, getSchema. Use getSchema to discover required fields before creating. For list, page beyond 100 results with cursor (from the previous response's nextCursor). NOTE: list/get need an n8n deployment whose public API permits credential reads — older n8n versions, restricted API keys, or instance settings can reject them, returning NOT_SUPPORTED (create, delete, getSchema — and update where the API version supports it — still work). SECURITY: credential data values are never logged. |
| n8n_audit_instanceA | Security audit of n8n instance. Combines n8n's built-in audit API (credentials, database, nodes, instance, filesystem risks) with deep workflow scanning (hardcoded secrets via 50+ regex patterns, unauthenticated webhooks, error handling gaps, data retention risks). Returns actionable markdown report with remediation steps using n8n_manage_credentials and n8n_update_partial_workflow. |
| n8n_manage_agentsA | Manage n8n Agents (persisted assistants with a model, instructions, tools, skills, tasks, memory and channels) through n8n's instance-level MCP server. Requires N8N_MCP_ACCESS_TOKEN (MCP API key from n8n Settings → Instance-level MCP) and n8n >= 2.34 with the agents module. Actions: reference, search, get, create, mutate, validate, call, publish, unpublish, revert, versions, delete, discover_assets, verify_mcp_server, update_integration. Start with action=reference (config shape and mutate operations), then discover_assets → create → mutate (one resource at a time, always with the latest configHash) → validate. projectId for create, discover_assets and verify_mcp_server defaults to your personal project. publish only when the user explicitly asks. call runs the agent with real credentials and tools and may return approvals[] that need a human decision — never approve on the user's behalf. This is not the AI Agent workflow node; use get_node for that. |
| n8n_explore_node_resourcesA | Resolve the real options behind a node's dynamic dropdown (loadOptions) or resource-locator search (listSearch) using one of the instance's credentials — Slack channels, Google Sheets tabs, model lists — so workflow configs use existing IDs instead of invented ones. Requires N8N_MCP_ACCESS_TOKEN. Find methodName/methodType in get_node output (dynamicOptions on a property) and the credentialId with n8n_manage_credentials list. |
| n8n_list_catalogA | List instance-level catalog entries: projects (with the personal project marked, needed as projectId for agents and data tables) or tags. Reads the Public API first; when team projects are not licensed there, falls back to n8n's MCP server if N8N_MCP_ACCESS_TOKEN is set. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Operation Result | Visual summary of workflow operations (create, update, delete, test) |
| Validation Summary | Visual summary of node and workflow validation results |
| Workflow List | Workflow snapshots with activation state and returned-page scope |
| Execution Results | Execution list, detail and deletion results |
| Connection Check | Connection evidence from health checks and diagnostics |
TDQS
Scored across 28 tools
Most tools target distinct resources and actions, but validate_workflow and n8n_validate_workflow appear to serve the same purpose, creating ambiguity. There is also a minor potential confusion between n8n_test_workflow and n8n_executions, though descriptions differentiate them. The overall overlap is limited but significant enough to warrant a middle score.
Naming is inconsistent: some tools have the 'n8n_' prefix (e.g., n8n_create_workflow) while others do not (e.g., validate_workflow, search_nodes). Even within the prefixed tools, patterns vary (e.g., n8n_workflow_versions is a noun phrase, while n8n_manage_credentials uses verb_noun). This mixed convention makes it harder to predict tool names and reduces consistency.
With 28 tools, the set is at the upper edge of what is typical for a comprehensive MCP server. The broad scope of n8n automation (workflows, nodes, templates, credentials, agents, data tables, executions, evaluations) justifies a large surface, but the count is slightly heavy and could benefit from consolidation (e.g., merging the duplicate validation tools).
The tool set provides extensive lifecycle coverage for the n8n domain: workflow CRUD, validation, testing, execution monitoring, evaluations, template deployment, credential management, node exploration, and instance auditing. There are minor gaps (e.g., no direct workflow import/export), but overall the surface is quite complete for the stated purpose.