n8n-admin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| N8N_API_KEY | No | n8n API key | |
| N8N_API_BASE_URL | No | Base URL of your n8n instance | |
| N8N_ADMIN_CONFIG_FILE | No | Path to a local JSON configuration file to load settings instead |
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 |
|---|---|
| get_policyC | Returns active write safety policy |
| list_workflowsC | Lists workflows from n8n API |
| get_workflowC | Gets a workflow by ID |
| get_workflow_by_nameC | Finds a workflow by exact name |
| export_workflow_jsonC | Exports workflow JSON to local backup file |
| get_active_stateC | Returns whether workflow is active |
| derive_tool_schemaC | Derives candidate IO schema from workflow node parameters |
| inspect_node_output_shapeC | Inspects output type shape for a node sample |
| validate_tool_ioC | Validates tool output type against expectation |
| replay_sample_payloadC | Parses and normalizes a sample payload |
| create_workflowC | Creates a new inactive workflow and exports a local source backup |
| duplicate_workflowC | Duplicates a workflow as immutable baseline |
| update_workflow_jsonC | Updates workflow with full or partial workflow object |
| patch_node_paramsC | Patches parameters on a named workflow node |
| set_workflow_activeD | Sets workflow active state |
| rollback_workflowC | Rolls back a workflow to a baseline workflow snapshot |
| list_backupsC | Lists backup records made by this admin tool |
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 17 tools
Most tools have clearly distinct purposes (get_workflow by ID vs get_workflow_by_name, patch_node_params vs update_workflow_json). Minor overlap between get_active_state and get_workflow (which likely returns active state anyway), and the four IO/schema tools form a related cluster, but descriptions keep them distinguishable.
Consistent verb_noun snake_case throughout (get_policy, list_workflows, create_workflow, update_workflow_json, patch_node_params, rollback_workflow). Minor word-order variance in set_workflow_active does not break the predictable pattern.
17 tools is reasonable for an admin server covering workflow CRUD, state management, backups, and IO schema analysis, though it sits near the upper end of comfortably scannable.
Strong lifecycle coverage: create, get, update, patch, activate, duplicate, rollback, export, and backup listing. No delete_workflow and no execution/run tooling, which are minor gaps for a full n8n admin surface.