Overview
What n8n-MCP does
n8n-MCP is a community server designed to help agents build and maintain n8n workflows with current node schemas and template knowledge. Its core tools can search nodes, inspect versioned properties, validate configurations, and retrieve templates without connecting to an n8n instance. Adding N8N_API_URL and an API key unlocks management tools for workflows, executions, data tables, credentials, health checks, and audits. It can run locally over stdio, as a protected HTTP service, or through the publisher's hosted offering.
Best for
- Designing valid n8n workflow JSON with node and property guidance
- Finding reusable n8n templates before assembling workflows from scratch
- Managing an n8n instance through an agent with explicitly controlled permissions
Not ideal for
- Users looking for an MCP server maintained by the n8n company itself
- Production access without a read-only policy, disabled destructive tools, and scoped API credentials
Capabilities
What an agent can do
- 01
Search core, verified, and community nodes and inspect their properties and versions
- 02
Validate node configurations and complete workflow structures
- 03
Search and retrieve workflow templates by keyword, task, node, or metadata
- 04
Create, update, validate, test, and version workflows through an n8n API connection
- 05
Inspect executions, health, and security posture, with optional data-table and credential management
Representative tools and operations
tools_documentationsearch_nodesget_nodevalidate_nodevalidate_workflowsearch_templatesget_templaten8n_create_workflown8n_get_workflown8n_update_partial_workflown8n_list_workflowsn8n_test_workflown8n_executionsn8n_audit_instancen8n_health_check
Installation
Connect n8n-MCP
Use the publisher’s current instructions as the source of truth. The examples below were checked on .
Any stdio MCP clientUse node knowledge and validation without instance management
npx n8n-mcp{
"mcpServers": {
"n8n-mcp": {
"command": "npx",
"args": ["n8n-mcp"],
"env": {
"MCP_MODE": "stdio",
"LOG_LEVEL": "error",
"DISABLE_CONSOLE_OUTPUT": "true"
}
}
}
}CodexEnable n8n instance management
npx n8n-mcp[mcp_servers.n8n-mcp]
command = "npx"
args = ["n8n-mcp"]
env = { MCP_MODE = "stdio", LOG_LEVEL = "error", DISABLE_CONSOLE_OUTPUT = "true", N8N_API_URL = "https://your-n8n-instance.com", N8N_API_KEY = "your-api-key" }Trust and access
Authentication and security notes
Authentication: Core documentation tools need no n8n credentials. Management tools require N8N_API_URL and N8N_API_KEY. Remote HTTP mode additionally requires an AUTH_TOKEN Bearer token.
Review before connecting
- Use a read-only n8n API key where possible and combine it with the documented disabled-tool and disabled-operation controls.
- Credential and data-table tools expose sensitive material even on read operations; remove them entirely when they are not required.
- Production HTTP mode should use HTTPS, a strong AUTH_TOKEN or token file, rate limiting, and strict network exposure.
- The project is community-maintained and is not an official n8n product.
Known limitations
- Management capabilities are unavailable until valid n8n API credentials are configured.
- The node and template catalog can lag the latest n8n release until the packaged database is refreshed.
- Launching the npm package concurrently from several clients can require separate npm cache directories.
- Several management tools can make destructive or externally visible changes when fully enabled.
Evidence
Sources used for this guide
Facts were checked against primary publisher material. Descriptions and guidance are original Graphify summaries.
FAQ
Questions about n8n-MCP
Can n8n-MCP help build workflows without an n8n API key?
Yes. Node search, documentation, templates, and offline validation work without an instance connection; management tools do not.
Is n8n-MCP an official n8n server?
No. It is a community-maintained project by czlonkowski, so teams should review its release and security practices independently.
