n8n MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| N8N_API_KEY | No | Your n8n API key | |
| N8N_BASE_URL | No | The base URL of your n8n instance | |
| N8N_PASSWORD | No | Your n8n password | |
| N8N_USERNAME | No | Your n8n username |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workflowsC | List all n8n workflows |
| get_workflowA | Get a specific n8n workflow by ID |
| create_workflowD | Create a new n8n workflow |
| update_workflowC | Update an existing n8n workflow |
| delete_workflowC | Delete an n8n workflow |
| activate_workflowC | Activate an n8n workflow |
| deactivate_workflowC | Deactivate an n8n workflow |
| apply_opsA | Apply multiple graph operations atomically to a workflow |
| list_node_typesA | List all available n8n node types |
| get_node_typeC | Get details about a specific n8n node type |
| examplesA | Get examples for a specific n8n node type |
| validate_node_configB | Validate a node configuration against its type definition |
| list_credentialsA | List all n8n credentials |
| resolve_credential_aliasA | Resolve a credential alias to its ID |
| get_credential_schemaB | Get JSON schema for a credential type |
| list_variablesC | List all variables with pagination support |
| create_variableC | Create a new variable (requires unique key) |
| update_variableC | Update an existing variable value |
| delete_variableC | Delete a variable by ID |
| list_workflow_tagsC | List tags for a specific n8n workflow |
| set_workflow_tagsC | Set tags for a specific n8n workflow |
| transfer_workflowC | Transfer an n8n workflow to a different project or owner |
| transfer_credentialC | Transfer an n8n credential to a different project or owner |
| list_executionsC | List n8n workflow executions |
| get_executionB | Get a specific n8n execution by ID |
| delete_executionC | Delete an n8n execution |
| webhook_urlsB | Get webhook URLs for a webhook node in a workflow |
| run_onceC | Execute a workflow manually once and return execution details |
| list_tagsB | List all tags with optional pagination |
| get_tagB | Get a specific tag by ID |
| create_tagC | Create a new tag |
| update_tagC | Update an existing tag |
| delete_tagC | Delete a tag by ID |
| source_control_pullB | Pull changes from source control to sync with remote |
| create_nodeB | Create a new node in an existing n8n workflow |
| update_nodeC | Update an existing node in an n8n workflow |
| connect_nodesC | Connect two nodes in an n8n workflow |
| delete_nodeC | Delete a node from an n8n workflow |
| set_node_positionC | Set the position of a node in an n8n workflow |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 39 tools
Most tools pair one resource with one action (create_workflow, delete_node, list_tags), and resources like workflows, nodes, credentials, variables, executions, and tags are cleanly separated. A few pairs, such as apply_ops versus node-specific editing or examples versus get_node_type, could be confused, but their descriptions make the intended use reasonably clear.
The dominant pattern is snake_case verb_noun: create_workflow, list_workflows, update_node, delete_variable. Minor outliers such as examples, webhook_urls, run_once, and apply_ops break the pattern but remain readable and predictable overall.
39 tools is a very large surface for an agent to scan, even for a broad n8n server. Several operations could be consolidated, such as node position and connection into apply_ops, and the separate CRUD sets for tags and variables add considerable bulk.
Workflows, nodes, tags, variables, and executions have solid CRUD/lifecycle coverage, but credentials lack create/update/delete, and transfer tools reference projects/owners with no discovery tool. Source control is also pull-only, leaving notable dead ends for workflow setup and admin tasks.