n8n MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| N8N_HOST | Yes | The host URL of your n8n instance | |
| N8N_API_KEY | Yes | Your n8n API key |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workflowsB | List all workflows on the n8n server |
| activate_workflowC | Activate a workflow |
| deactivate_workflowC | Deactivate a workflow |
| get_workflowB | Get details of a specific workflow |
| create_workflowB | Create a new workflow |
| search_templatesA | Search for n8n workflow templates to find examples of how to use nodes. |
| get_node_specsB | Get documentation/specs for a specific node type from n8n documentation. |
| create_tagB | Create a new tag |
| list_tagsB | List all available tags |
| add_tags_to_workflowB | Add tags to a workflow |
| index_all_nodesA | explore the n8n node library by category (Core, App, Trigger, etc.) to find the right node for a task. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| All Workflows | A dynamic list of all workflows in the n8n instance |
TDQS
Scored across 11 tools
Each tool targets a distinct operation: workflow CRUD and activation, tag management, node specs, and template search. No overlapping purposes.
All tools follow a consistent verb_noun snake_case pattern (e.g., activate_workflow, list_tags), making the set predictable.
11 tools cover the main aspects of n8n (workflows, tags, nodes, templates) without being excessive or sparse.
Missing update/delete for workflows and tags, and no tool to remove tags from a workflow. These gaps could hinder some automation tasks.