n8n MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| N8N_URL | Yes | The URL of your n8n instance (e.g., https://your-n8n-instance.com or https://your-subdomain.app.n8n.cloud) | |
| N8N_API_KEY | Yes | Your n8n API key (generate from Settings → API in your n8n instance) |
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 with optional filtering |
| get_workflowC | Get detailed information about a specific workflow |
| create_workflowB | Create a new n8n workflow from JSON definition |
| update_workflowB | Update an existing workflow |
| delete_workflowC | Delete a workflow |
| activate_workflowC | Activate a workflow |
| deactivate_workflowB | Deactivate a workflow |
| execute_workflowB | Execute a workflow with optional input data |
| get_executionsB | Get workflow execution history with filtering options |
| get_executionC | Get details of a specific execution |
| delete_executionC | Delete an execution |
| retry_executionB | Retry a failed execution |
| get_tagsB | List all available tags |
| create_tagB | Create a new tag |
| update_tagC | Update a tag |
| delete_tagD | Delete a tag |
| get_credentialsA | List available credentials (names only, no sensitive data) |
| search_workflowsA | Search workflows by name or tags |
| get_workflow_webhooksB | Get webhook URLs for a 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 19 tools
Every tool has a clearly distinct purpose: workflow CRUD, activation, execution, and history; tag CRUD; credential listing; and webhook retrieval. No two tools overlap significantly.
All tool names follow a consistent 'verb_noun' pattern in snake_case, such as 'create_workflow', 'get_executions', and 'update_tag'. No mixed conventions or vague verbs.
With 19 tools, the set covers multiple domains (workflows, executions, tags, credentials, webhooks) and each tool seems necessary. Slightly on the higher end but still well-scoped for the server's purpose.
Workflows, executions, and tags have full CRUD/lifecycle coverage. Credentials are limited to listing names, which is a minor gap but likely intentional for security. No obvious dead ends for typical workflows.