n8n MCP Server
Servidor MCP n8n
Un servidor MCP que proporciona acceso a flujos de trabajo, ejecuciones, credenciales y más de n8n mediante el Protocolo de Contexto de Modelo. Esto permite que los Modelos de Lenguaje Grandes (LLM) interactúen con instancias de n8n de forma segura y estandarizada.
Instalación
Obtenga su clave API n8n
Inicie sesión en su instancia n8n
Haga clic en su icono de usuario en la parte inferior izquierda.
Ir a Configuración
Seleccionar API
Haga clic en "Crear clave API"
Copia tu clave API (no podrás volver a verla)
Instalar el servidor MCP
Opción 1: Instalar desde npm (recomendado)
npm install -g @illuminaresolutions/n8n-mcp-serverOpción 2: Instalar desde la fuente
Clonar el repositorio:
git clone https://github.com/illuminaresolutions/n8n-mcp-server.git cd n8n-mcp-serverInstalar dependencias y compilar:
npm install npm run buildInicie el servidor en segundo plano:
nohup npm start > n8n-mcp.log 2>&1 &Para detener el servidor:
pkill -f "node build/index.js"
Nota: Al instalar desde npm, el servidor estará disponible como n8n-mcp-server en su RUTA.
Related MCP server: MCP Server for n8n Integration
Configuración
Escritorio de Claude
Abra la configuración de Claude Desktop:
~/Library/Application Support/Claude/claude_desktop_config.jsonAgregue la configuración n8n:
{ "mcpServers": { "n8n": { "command": "n8n-mcp-server", "env": { "N8N_HOST": "https://your-n8n-instance.com", "N8N_API_KEY": "your-api-key-here" } } } }
Cline (Código VS)
Instalar el servidor (siga los pasos de instalación anteriores)
Abrir VS Code
Abra la extensión Cline desde la barra lateral izquierda
Haga clic en el icono 'Servidores MCP' en la parte superior del panel
Desplácese hasta la parte inferior y haga clic en "Configurar servidores MCP".
Agregue al archivo de configuración abierto:
{ "mcpServers": { "n8n": { "command": "n8n-mcp-server", "env": { "N8N_HOST": "https://your-n8n-instance.com", "N8N_API_KEY": "your-api-key-here" } } } }Guardar el archivo
Asegúrese de que el interruptor MCP esté habilitado (verde) y que el indicador de estado esté verde
Comience a usar comandos MCP en Cline
Sabio
¡Próximamente! El servidor MCP n8n estará disponible a través de:
Mercado de Smithery.ai
Importar desde Claude Desktop
Por ahora, utilice Claude Desktop o Cline.
Validación
Después de la configuración:
Reinicia tu solicitud de LLM
Pregunta: "Enumerar mis flujos de trabajo n8n"
Deberías ver tus flujos de trabajo enumerados
Si recibe un error:
Comprueba que tu instancia n8n se esté ejecutando
Verifique que su clave API tenga los permisos correctos
Asegúrese de que N8N_HOST no tenga ninguna barra diagonal final
Características
Características principales
Enumerar y gestionar flujos de trabajo
Ver detalles del flujo de trabajo
Ejecutar flujos de trabajo
Administrar credenciales
Manejar etiquetas y ejecuciones
Generar auditorías de seguridad
Administrar etiquetas de flujo de trabajo
Funciones empresariales
Estas funciones requieren una licencia n8n Enterprise:
Gestión de proyectos
Gestión de variables
Gestión avanzada de usuarios
Solución de problemas
Problemas comunes
"Cliente no inicializado"
Compruebe que N8N_HOST y N8N_API_KEY estén configurados correctamente
Asegúrese de que la instancia n8n sea accesible
Verificar los permisos de la clave API
"Se requiere licencia"
Estás intentando utilizar una función de Enterprise
Actualice a n8n Enterprise o utilice solo las funciones principales
Problemas de conexión
Verificar que la instancia n8n se esté ejecutando
Comprobar el protocolo URL (http/https)
Eliminar la barra diagonal final de N8N_HOST
Mejores prácticas de seguridad
Gestión de claves API
Utilice los permisos mínimos necesarios
Gire las llaves regularmente
Nunca envíe claves al control de versiones
Acceso a instancias
Utilice HTTPS para producción
Habilitar la autenticación n8n
Mantén n8n actualizado
Apoyo
Licencia
Available Tools
33 toolsactivate-workflowC
Activate a workflow by ID. This will enable the workflow to run. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.
Inputs: clientId (required), id (required).
create-credentialB
Create a credential that can be used by nodes of the specified type. The credential type name can be found in the n8n UI when creating credentials (e.g., 'cloudflareApi', 'githubApi', 'slackOAuth2Api'). Use get-credential-schema first to see what fields are required for the credential type you want to create.
Inputs: clientId (required), name (required), type (required), data (required).
create-projectA
Create a new project in n8n. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.
Inputs: clientId (required), name (required).
create-tagC
Create a new tag in your instance.
Inputs: clientId (required), name (required).
create-usersC
Create one or more users in your instance.
Inputs: clientId (required), users (required).
create-variableA
Create a new variable in n8n. NOTE: Requires n8n Enterprise license with variable management features enabled. Variables can be used across workflows to store and share data. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.
Inputs: clientId (required), key (required), value (required).
create-workflowB
Create a new workflow in n8n. Use to set up a new workflow with optional nodes and connections. IMPORTANT: 1) Arguments must be provided as compact, single-line JSON without whitespace or newlines. 2) Must provide full workflow structure including nodes and connections arrays, even if empty. The 'active' property should not be included as it is read-only.
Inputs: clientId (required), name (required), nodes, connections.
deactivate-workflowC
Deactivate a workflow by ID. This will prevent the workflow from running. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.
Inputs: clientId (required), id (required).
delete-credentialB
Delete a credential by ID. You must be the owner of the credentials.
Inputs: clientId (required), id (required).
delete-executionC
Delete a specific execution by ID.
Inputs: clientId (required), id (required).
delete-projectA
Delete a project by ID. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.
Inputs: clientId (required), projectId (required).
delete-tagC
Delete a tag by ID.
Inputs: clientId (required), id (required).
delete-userC
Delete a user from your instance.
Inputs: clientId (required), idOrEmail (required).
delete-variableA
Delete a variable by ID. NOTE: Requires n8n Enterprise license with variable management features enabled. Use after list-variables to get the ID of the variable to delete. This action cannot be undone. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.
Inputs: clientId (required), id (required).
delete-workflowA
Delete a workflow by ID. This action cannot be undone. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.
Inputs: clientId (required), id (required).
generate-auditC
Generate a security audit for your n8n instance.
Inputs: clientId (required), daysAbandonedWorkflow, categories.
get-credential-schemaA
Show credential data schema for a specific credential type. The credential type name can be found in the n8n UI when creating credentials (e.g., 'cloudflareApi', 'githubApi', 'slackOAuth2Api'). This will show you what fields are required for creating credentials of this type.
Inputs: clientId (required), credentialTypeName (required).
get-executionC
Retrieve a specific execution by ID.
Inputs: clientId (required), id (required), includeData.
get-tagC
Retrieve a specific tag by ID.
Inputs: clientId (required), id (required).
get-userC
Get user by ID or email address.
Inputs: clientId (required), idOrEmail (required).
get-workflowB
Retrieve a workflow by ID. Use after list-workflows to get detailed information about a specific workflow. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.
Inputs: clientId (required), id (required).
get-workflow-tagsC
Get tags associated with a workflow.
Inputs: clientId (required), workflowId (required).
init-n8nA
Initialize connection to n8n instance. Use this tool whenever an n8n URL and API key are shared to establish the connection. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.
Inputs: url (required), apiKey (required).
list-executionsC
Retrieve all executions from your instance with optional filtering.
Inputs: clientId (required), includeData, status, workflowId, +1 more.
list-projectsA
List all projects from n8n. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.
Inputs: clientId (required).
list-tagsC
Retrieve all tags from your instance.
Inputs: clientId (required), limit.
list-usersB
Retrieve all users from your instance. Only available for the instance owner.
Inputs: clientId (required).
list-variablesA
List all variables from n8n. NOTE: Requires n8n Enterprise license with variable management features enabled. Use after init-n8n to see available variables. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.
Inputs: clientId (required).
list-workflowsB
List all workflows from n8n. Use after init-n8n to see available workflows. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.
Inputs: clientId (required).
update-projectB
Update a project's name. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.
Inputs: clientId (required), projectId (required), name (required).
update-tagC
Update a tag's name.
Inputs: clientId (required), id (required), name (required).
update-workflowC
Update an existing workflow in n8n. Use after get-workflow to modify a workflow's properties, nodes, or connections. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.
Inputs: clientId (required), id (required), workflow (required).
update-workflow-tagsC
Update tags associated with a workflow.
Inputs: clientId (required), workflowId (required), tagIds (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 33 tools
Most tools have distinct purposes targeting specific resources like workflows, credentials, projects, tags, users, variables, and executions. However, some tools like 'create-users' and 'delete-user' (singular vs plural) could cause minor confusion, and 'get-workflow-tags' vs 'update-workflow-tags' are closely related but still distinguishable.
Tool names follow a highly consistent verb-noun pattern with hyphens (e.g., create-workflow, list-executions, delete-credential). All tools adhere to this convention, making them predictable and easy to parse, with no mixing of styles like camelCase or snake_case.
With 33 tools, the count is borderline high for an MCP server, as it may feel heavy and overwhelming for agents. While n8n is a complex automation platform, the tool set could potentially be streamlined or grouped to reduce cognitive load, though it does cover a broad domain.
The tool set provides comprehensive CRUD/lifecycle coverage for all key n8n resources: workflows (activate, deactivate, create, get, update, delete, list), credentials (create, delete, get-schema), projects (create, delete, list, update), tags (create, delete, get, list, update), users (create, delete, get, list), variables (create, delete, list), and executions (delete, get, list). There are no obvious gaps, and tools like init-n8n and generate-audit add useful functionality.
Maintenance
Related MCP Connectors
Open-source Zapier/n8n alternative as an MCP server: agents build, run and debug your workflows.
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Related MCP Servers
- AlicenseCqualityDmaintenanceA Model Context Protocol (MCP) server for programmatically creating and managing n8n workflows.118MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol server that enables AI agents to interact with n8n workflows and automation tools through a standardized interface, allowing execution of workflows and access to n8n functions.-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that generates production-ready n8n workflows from natural language prompts. Transform simple descriptions into fully validated, deployable automation workflows using AI-powered code generation.1-
- AlicenseBqualityCmaintenanceA Model Context Protocol server that enables AI assistants to interact with N8N workflows, executions, and automation capabilities.12MIT