n8n-workflows-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| N8N_API_KEY | Yes | REST API key, sent as X-N8N-API-KEY on every discovery request. | |
| N8N_MCP_TAG | No | Tag used as the discovery/execution boundary. | mcp |
| N8N_BASE_URL | Yes | Base URL of your n8n instance, no trailing slash. Must be a valid URL. | |
| N8N_WEBHOOK_AUTH_HEADER_NAME | No | Name of a header sent on every webhook call. Requires N8N_WEBHOOK_AUTH_HEADER_VALUE if set. | |
| N8N_WEBHOOK_AUTH_HEADER_VALUE | No | Value of that header. Requires N8N_WEBHOOK_AUTH_HEADER_NAME if set. |
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 | Lists n8n workflows opted in through the configured MCP tag. This tag is the governance boundary for workflows this agent may call. |
| get_workflow_schemaA | Returns the input schema and webhook details needed to call a given n8n workflow. |
| execute_workflowA | Executes a tagged n8n workflow through its webhook using the supplied JSON input. Delivery is at-least-once: a timeout or network error does not mean the workflow didn't run, so don't blindly retry on failure. |
| get_execution_statusA | Fetches the status of a previously triggered n8n execution 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 4 tools
Each tool has a clearly distinct purpose: listing workflows, retrieving schema, executing a workflow, and checking execution status. No overlap or ambiguity exists between them.
All tool names follow a consistent verb_noun pattern (list_workflows, get_workflow_schema, execute_workflow, get_execution_status), making the naming predictable and uniform.
With only 4 tools, the server is well-scoped for its purpose. Each tool is essential and earns its place without unnecessary bloat or missing core functionality.
The tool set covers the full execution lifecycle: discover workflows, understand their input schema, execute them, and check execution status. No obvious dead ends or missing operations for the stated purpose.