n8n Automation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| N8N_API_KEY | Yes | Your n8n API key | |
| N8N_BASE_URL | No | The base URL of your n8n instance | http://localhost:5678 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workflowsA | List all workflows in n8n with filtering by active status, tags, or name. Returns node counts and metadata. |
| get_workflowA | Get full details of a workflow including nodes, connections, and settings. |
| create_workflowA | Create a new n8n workflow with nodes, connections, and settings. Optionally activate immediately. |
| update_workflowA | Update an existing workflow's name, nodes, connections, settings, tags, or active status. |
| delete_workflowA | Permanently delete a workflow by ID. |
| activate_workflowA | Activate a workflow so it runs automatically on triggers. |
| deactivate_workflowA | Deactivate a workflow so it stops running on triggers. |
| duplicate_workflowC | Duplicate an existing workflow. |
| export_workflowA | Export a workflow as a formatted JSON structure for backup or sharing. |
| import_workflowB | Import a workflow directly from a JSON string definition. |
| list_common_nodesA | Get documentation and JSON template snippets for common n8n node types (Webhook, Schedule, HTTP Request, Code, Switch, OpenAI, Slack). |
| list_executionsB | List workflow executions filtered by workflow ID, status (error/success/waiting/running/canceled), and date. |
| get_executionA | Get detailed node-by-node input and output data for a specific execution. |
| delete_executionA | Delete an execution record. |
| run_workflowC | Manually trigger a workflow execution with optional payload data. |
| retry_executionB | Retry a failed execution using the workflow definition. |
| stop_executionA | Stop or cancel a currently running execution. |
| list_tagsA | List all workflow tags. |
| create_tagA | Create a new tag. |
| update_tagA | Rename an existing tag. |
| delete_tagB | Delete a tag permanently. |
| list_credentialsB | List saved credentials. |
| get_credentialA | Get metadata for a credential (secret data is hidden). |
| create_credentialC | Create a new credential instance. |
| update_credentialB | Update an existing credential. |
| delete_credentialC | Delete a credential. |
| list_credential_typesA | List supported credential types in n8n with optional search query. |
| list_variablesA | List n8n environment/instance variables. |
| create_variableA | Create a custom environment variable in n8n. |
| update_variableA | Update an existing variable key or value. |
| delete_variableB | Delete an environment variable. |
| test_connectionA | Health check: Test connection to n8n instance and verify API key and response latency. |
| list_usersA | List registered users in the n8n instance. |
| get_userA | Get details of a specific user by ID. |
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 34 tools
Each tool targets a distinct resource-action pair: workflows, executions, credentials, tags, variables, and users each have their own operations. There is no overlap between tools; for example, 'run_workflow' and 'activate_workflow' are clearly different (manual trigger vs. scheduled).
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_workflows, create_credential, update_tag). Plural nouns are used for list operations, singular for others, and this pattern is uniform across all resource types.
With 34 tools, the server exceeds the 25+ threshold the rubric defines as 'too many'. While each tool serves a legitimate purpose given the broad scope of n8n management, the sheer number may overwhelm an agent and is heavier than the typical well-scoped server.
The surface covers the full lifecycle for workflows (create, read, update, delete, activate, deactivate, duplicate, export, import), executions (list, get, run, retry, stop, delete), credentials (CRUD plus types), tags and variables (full CRUD), and user listing, plus a health check. There are no obvious gaps or dead ends.