n8n 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 | Yes | The base URL of 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 | Get all workflows with their status and metadata |
| get_workflowB | Get detailed information about a specific workflow |
| activate_workflowB | Activate a workflow to start automatic execution |
| deactivate_workflowA | Deactivate a workflow to stop automatic execution |
| execute_workflowC | Manually trigger a workflow execution |
| list_executionsC | Get recent workflow executions with optional filtering |
| get_executionB | Get detailed information about a specific execution |
| stop_executionC | Stop a currently running execution |
| get_instance_infoB | Get n8n instance information and health status |
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 9 tools
Each tool targets a distinct resource and action: workflow management (list/get/activate/deactivate/execute), execution management (list/get/stop), and instance info. No two tools overlap in purpose, and descriptions clearly delineate manual execution from activation and stopping a specific execution from deactivating a workflow.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_workflows, get_workflow, activate_workflow). The single get_instance_info slightly extends to verb_noun_noun but remains fully predictable and readable.
Nine tools is well-scoped for an n8n management server, covering key workflow and execution lifecycle operations without redundancy. Each tool earns its place and the set is neither thin nor heavy.
The surface covers listing, retrieving, activating, deactivating, and executing workflows, plus execution monitoring and instance health. However, it lacks create, update, and delete operations for workflows, which are fundamental for a workflow automation platform and will cause agent failures when trying to build or modify workflows.