n8n-manager-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| n8n_safety_statusA | Show n8n Manager safety settings, backup directory, audit log location, and whether the optional n8n-workflow-manager seam is configured and reachable. |
| n8n_manager_historyA | Read version history, recorded decisions, and sync history from a running n8n-workflow-manager. Requires the N8N_MCP_MANAGER_URL environment variable; without it, this MCP talks to n8n directly and no such history exists. Read-only. |
| n8n_set_safety_modeB | Configure local safety settings: read-only mode, backup-before-mutation, and audit logging. |
| n8n_list_workflowsA | List all workflows on an n8n server. Returns workflow names, IDs, active status, and node counts. |
| n8n_get_workflowA | Get detailed information about a specific n8n workflow including all nodes, connections, and settings. |
| n8n_create_workflowC | Create a new n8n workflow. Provide the full workflow JSON including nodes and connections. |
| n8n_update_workflowC | Update an existing n8n workflow. Send the full updated workflow JSON. |
| n8n_delete_workflowA | Delete a workflow from an n8n server. By default, a JSON backup is saved before deletion. |
| n8n_activate_workflowB | Activate or deactivate an n8n workflow. |
| n8n_list_executionsA | List recent workflow executions on an n8n server. Shows status, timing, and errors. |
| n8n_add_serverB | Add or update an n8n server connection. The API key can be created in n8n under Settings > API. |
| n8n_list_serversA | List all configured n8n server connections. |
| n8n_ping_serverB | Test the connection to an n8n server. |
| n8n_remove_serverB | Remove an n8n server from the configuration. |
| n8n_export_workflowA | Export a workflow from an n8n server as JSON. Returns the complete workflow definition that can be imported into another n8n instance. |
| n8n_list_backupsA | List local workflow backups created before n8n mutations. |
| n8n_restore_workflowA | Restore a workflow from a local backup. By default creates a new workflow; pass target_workflow_id to overwrite an existing workflow. |
| n8n_import_workflowB | Import a workflow JSON onto an n8n server. Takes a full n8n workflow JSON and creates it on the server. |
| n8n_describe_nodesB | Get information about common n8n node types. Useful for understanding which nodes to use when building workflows. |
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 19 tools
Most tools are clearly separated by resource and action, but n8n_create_workflow and n8n_import_workflow are nearly identical in intent, and n8n_get_workflow vs n8n_export_workflow could easily be confused. The safety/manager tools are distinct but add a few overlapping informational surfaces.
The n8n_ prefix and snake_case are consistent, and most tools follow a clear verb_noun pattern (list_workflows, activate_workflow, add_server). Minor deviations like n8n_safety_status and n8n_manager_history use noun phrases instead of get/list verbs, but they do not create real ambiguity.
19 tools is on the heavy side (16-25 range), but the count is largely justified by the distinct subdomains: workflow CRUD, server management, backups, safety, and executions. It could be tighter by merging create/import and get/export, but the scope is coherent.
Workflow lifecycle, server connections, backups, and safety are well covered. Obvious gaps are minor: only list executions (no get/stop execution detail) and no backup deletion/rotation, but the core workflow-management surface is complete.