Loading ToolBench
MCP server for managing n8n workflows, executions, credentials, tags, variables, and users
The n8n Management MCP server demonstrates solid definition quality with consistent schema coverage, well-articulated descriptions, and proper tool composition. All 31 tools are explicitly registered with descriptions, input schemas, and annotations. Descriptions average ~150 characters and clearly state purpose, preconditions, and return value. However, output schemas are not documented, the tool definitions specify inputs but not the structure of returned data. Parameter descriptions are generally good but lack specific constraints (ranges, patterns, enums) that would elevate LLM reliability. Error handling guidance is minimal. Tool annotations (readOnlyHint, destructiveHint, idempotentHint) are present and accurate, following production patterns. Naming convention is consistent (verb_noun, n8n_ prefix) and unambiguous across all 31 tools. The credential system (create_credential, get_credential_schema) shows good design: get_credential_schema acts as a discovery tool that guides the user on required fields before creation. However, the incomplete documentation of credential data structure and lack of validation rules in descriptions represent the main quality gap.
Start a workflow to listen for triggers (webhooks, schedules, etc). Activating enables automatic execution when trigger conditions are met. Workflow must have valid trigger nodes.
Store new API credentials for services like GitHub, Slack, or databases. Provide credential type, descriptive name, and authentication data. Use get_credential_schema first to see required fields for each type.
Create a new tag for organizing workflows. Provide tag name. Returns newly created tag with assigned ID.
Create a new environment variable for use across all workflows. Provide key (name) and value. Variables are accessible in node expressions.
Create a new automation workflow with nodes and connections. Provide workflow name, node array, and connection object. Optionally activate immediately. Returns new workflow with assigned ID.
Output schemas not documented. Tool definitions specify input schemas but omit the structure of returned data. LLMs cannot reason about downstream tool chaining without knowing what fields are available in responses.
Parameter descriptions lack explicit constraints. Numeric parameters (e.g., limits, counts) do not specify ranges. String parameters do not specify formats, patterns, or length limits. This reduces LLM's ability to generate valid input without trial-and-error.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 65 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 0 | - | v1 |
Stop a workflow from listening to triggers. Deactivating prevents automatic execution but preserves workflow configuration. Use before making structure changes.
Remove stored credential permanently. Workflows using this credential will fail if executed. Useful for removing expired or unused credentials.
Remove execution record from history to save storage or clean up test runs. Permanently deletes execution data. Use after debugging or to maintain clean execution logs.
Delete a tag permanently. Workflows assigned this tag are not deleted, only the tag association is removed.
Remove a user account permanently from the n8n instance. Requires owner permissions. User's workflows are not deleted, only the account is removed.
Delete an environment variable permanently. Workflows referencing this variable will fail if executed.
Permanently delete a workflow and all associated execution history. This action cannot be undone. Workflow must be deactivated first. Use with caution.
Manually trigger workflow execution with optional input data. Useful for testing or API-driven workflows without webhooks. Returns execution ID to track progress. Does not require workflow to be active.
Retrieve required and optional fields for a credential type. Returns schema with field names, types, and descriptions. Use before creating credentials to understand what data is needed.
Get detailed execution data including node outputs, error messages, and timing. Returns full execution log with data passed between nodes. Essential for debugging failed workflows or understanding data flow.
Get details of a specific tag including ID and name. Returns tag metadata.
Get details of a specific user including email, name, role, and creation date. Requires owner permissions.
Get complete workflow definition including all nodes, connections, and settings. Returns full workflow JSON with node configurations and data flow. Use this to inspect workflow logic before modifying or executing.
Retrieve tags assigned to a workflow for categorization. Returns array of tag names. Use this to understand workflow organization before bulk operations.
Retrieve execution history with status, timestamps, and workflow info. Filter by workflow ID or get all executions. Returns execution ID, status (success/error/running), start time, and workflow name. Use this to monitor automation performance or debug failures.
Retrieve all tags used in the n8n instance. Returns tag ID and name. Use this to understand available tags before filtering workflows or assigning tags.
Retrieve all user accounts in the n8n instance. Returns user ID, email, name, and role. Requires owner permissions. Use this to manage team members and permissions.
Retrieve all environment variables available in the n8n instance. Returns variable key, value, and type. Use this to reference variables in workflows or understand configuration.
Retrieve all workflows with their status, tags, and metadata. Returns workflow ID, name, active status, creation date, and tags. Use this to browse available automations or find a specific workflow by name.
Rerun a failed execution with the same input data. Useful for transient errors like network timeouts. Creates new execution while preserving original execution log. Only works with failed executions.
Modify stored credential data without changing type. Updates authentication details for existing credential. Useful for refreshing API keys or updating passwords.
Rename an existing tag. Provides new tag name. All workflows with this tag remain associated.
Change a user's role to control permissions. Accepts 'admin' or 'member' role. Requires owner permissions. Use to grant or revoke admin privileges.
Modify an existing environment variable. Updates key and/or value. Changes apply immediately to all active workflows.
Modify existing workflow structure or settings. Update workflow name, add/remove nodes, or change connections. Workflow must be deactivated first for structure changes. Returns updated workflow.
Assign tags to a workflow for organization and filtering. Replaces existing tags completely. Use tags like "production", "testing", or team names. Create missing tags automatically.
Error handling and recovery guidance absent. Tool descriptions do not specify what errors are possible, what they mean, or how to recover. For example, 'invalid credential type' or 'workflow not found' errors lack actionable guidance.
Credential creation lacks discovery guidance. The n8n_create_credential tool accepts a 'type' parameter but does not document how to discover valid types or what fields each type requires. Users must call get_credential_schema separately, which invites errors if the wrong type is guessed.
Pagination not documented. Tools like list_workflows, list_executions, list_tags, and list_variables lack pagination parameters (offset, limit, cursor). Large result sets could exhaust context or be truncated without warning.
Destructive operations lack confirmation/dry-run support. delete_workflow, delete_execution, delete_credential, delete_user, and delete_tag perform irreversible actions without a safeguard like a confirm step or dry-run preview.
Missing prerequisites documentation. Several tools have implicit ordering requirements (e.g., activate_workflow requires the workflow to exist and have valid trigger nodes, create_workflow requires nodes and connections to be valid) but do not document these in the description.