Loading ToolBench
MCP server for n8n workflow management -- view, create, sync, and manage n8n workflows via AI assistants
The server provides 19 tools for n8n workflow management with complete parameter schemas and descriptions. Most tools follow verb_noun naming conventions (n8n_add_server, n8n_list_workflows, etc.). However, there are significant gaps in output schema documentation, error handling guidance, and description depth. Tool descriptions average ~60-80 characters, which is below the 194-char baseline for A+ tools. Parameters are typed and described, but many descriptions lack actionable constraints (e.g., what constitutes valid node/connection arrays for create_workflow). Error responses are not documented, and there is no guidance on recovery strategies. The 'n8n_manager_history' tool accepts a workflowId typed as 'number' but the description lacks clarity on what 'positive integer' constraint means in the n8n context. Output schemas are inferred rather than explicitly documented in code comments or return-type annotations.
Activate a workflow on an n8n server
Add a new n8n server to the configuration
Create a new workflow on an n8n server
Delete a workflow from an n8n server
Describe available n8n node types
Export a workflow to a JSON file
Retrieve a specific workflow by ID
Output schemas not documented. Tools return results but the response structure (fields, types, pagination) is not visible in code or description. LLMs cannot plan downstream calls without knowing what fields a tool returns.
Create and update workflow tools accept 'nodes' and 'connections' as array parameters with no description of the expected structure. LLMs cannot construct valid node/connection payloads without examples or schema details.
No error handling guidance documented. Tools do not explain what errors might occur, how to recover from them, or whether failures are retryable. Descriptions lack recovery hints per pattern:recovery-guide.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 60 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 26 | - | v1 |
Import a workflow from a JSON file
List backup files for workflows
List workflow executions on an n8n server
List all configured n8n servers
List workflows on an n8n server
Retrieve version history and decision records from the n8n-workflow-manager
Test connectivity to an n8n server
Remove an n8n server from the configuration
Restore a workflow from a backup file
Get the current safety settings status
Configure safety settings for the MCP server
Update an existing workflow
Destructive operations (n8n_delete_workflow) have no confirmation or dry-run step documented. Agents may accidentally delete workflows without a safeguard pattern.
Tool descriptions are short (55-70 chars average) and lack WHEN-to-use guidance. Baseline A+ tools average 194 chars. Descriptions should state the purpose, when to call it, and what it returns.
n8n_manager_history tool accepts 'workflowId' as a number but the context and purpose of 'Manager workflow ID' are unclear. Description lacks guidance on what this ID refers to and where to obtain it.
Many tools default the 'server' parameter to the default server but the description does not explain how the default is determined or warn about precedence. Parameter dependency documentation is sparse.