n8n Management MCP Server
Provides tools for managing an n8n instance, including creating, updating, and executing workflows, viewing execution history, managing credentials, tags, global variables, and user accounts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@n8n Management MCP Server list my workflows and show which ones are currently active"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
n8n Management MCP Server
MCP (Model Context Protocol) server for connecting AI assistants to your n8n instance. Manage workflows, executions, credentials, tags, variables, and users through 31 tools.
Works with Claude Desktop, Cursor, VS Code, and any MCP client.
Quick Start
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"n8n": {
"command": "npx",
"args": ["-y", "@node2flow/n8n-management-mcp"],
"env": {
"N8N_URL": "https://your-n8n-instance.com",
"N8N_API_KEY": "your-n8n-api-key"
}
}
}
}Cursor / VS Code
Add to MCP settings:
{
"mcpServers": {
"n8n": {
"command": "npx",
"args": ["-y", "@node2flow/n8n-management-mcp"],
"env": {
"N8N_URL": "https://your-n8n-instance.com",
"N8N_API_KEY": "your-n8n-api-key"
}
}
}
}HTTP Mode (Streamable HTTP)
For remote deployment or shared access:
N8N_URL=https://your-n8n.com N8N_API_KEY=your_key npx @node2flow/n8n-management-mcp --httpServer starts on port 3000 (configurable via PORT env var). MCP endpoint: http://localhost:3000/mcp
Related MCP server: n8n MCP Server
Configuration
Environment Variable | Required | Description |
| Yes | URL of your n8n instance (e.g. |
| Yes | n8n API key (how to create) |
| No | Port for HTTP server (default: |
All Tools (31 tools)
Workflow Management (10 tools)
Tool | Description |
| List all workflows with status and tags |
| Get workflow details (nodes, connections) |
| Create a new workflow |
| Update workflow structure |
| Permanently delete a workflow |
| Activate workflow triggers |
| Deactivate workflow triggers |
| Execute a workflow with input data |
| Get tags assigned to a workflow |
| Update workflow tags |
Execution History (4 tools)
Tool | Description |
| List execution history (filter by workflow) |
| Get execution details with node outputs |
| Delete an execution record |
| Retry a failed execution |
Credentials (4 tools)
Tool | Description |
| Store API credentials |
| Update credential data |
| Delete a credential |
| Get required fields for a credential type |
Tags (5 tools)
Tool | Description |
| List all tags |
| Get tag details |
| Create a new tag |
| Rename a tag |
| Delete a tag |
Variables (4 tools)
Tool | Description |
| List all environment variables |
| Create a global variable |
| Update a variable value |
| Delete a variable |
User Management (4 tools)
Tool | Description |
| List all users (owner only) |
| Get user details |
| Delete a user |
| Change user role |
Requirements
Node.js 18+
n8n instance with API enabled
n8n API key
How to Create an n8n API Key
Go to your n8n instance Settings
Select API > API Keys
Click Create API key
Copy the key and use it as
N8N_API_KEY
For Developers
git clone https://github.com/node2flow-th/n8n-management-mcp-community.git
cd n8n-management-mcp-community
npm install
npm run build
# Run in stdio mode
N8N_URL=https://your-n8n.com N8N_API_KEY=your_key npm start
# Run in dev mode (hot reload)
N8N_URL=https://your-n8n.com N8N_API_KEY=your_key npm run dev
# Run in HTTP mode
N8N_URL=https://your-n8n.com N8N_API_KEY=your_key npm start -- --httpLicense
MIT License - see LICENSE
Copyright (c) 2026 Node2Flow
Links
Available Tools
27 toolsn8n_activate_workflowAIdempotent
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.
Inputs: id (required).
n8n_create_credentialA
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.
Inputs: name (required), type (required), data (required).
n8n_create_tagA
Create new tag for workflow categorization. Use meaningful names like "production", "staging", "team-marketing", or "urgent". Tags help filter and organize workflows.
Inputs: name (required).
n8n_create_workflowA
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.
Inputs: name (required), nodes (required), connections (required), active.
n8n_deactivate_workflowAIdempotent
Stop a workflow from listening to triggers. Deactivating prevents automatic execution but preserves workflow configuration. Use before making structure changes.
Inputs: id (required).
n8n_delete_credentialADestructiveIdempotent
Remove stored credential. Cannot delete credentials currently used in active workflows. Deactivate dependent workflows first. Use with caution as this may break workflows.
Inputs: id (required).
n8n_delete_executionADestructiveIdempotent
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.
Inputs: id (required).
n8n_delete_tagADestructiveIdempotent
Remove tag from system. Automatically removes this tag from all workflows using it. Tag removal does not affect workflows themselves, only the tag association.
Inputs: id (required).
n8n_delete_userADestructiveIdempotent
Remove user from n8n instance. Only available to instance owner. Cannot delete the owner account. Deleted users lose access immediately. Workflows created by this user remain intact.
Inputs: id (required).
n8n_delete_workflowADestructiveIdempotent
Permanently delete a workflow and all associated execution history. This action cannot be undone. Workflow must be deactivated first. Use with caution.
Inputs: id (required).
n8n_execute_workflowA
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.
Inputs: id (required), data.
n8n_get_credential_schemaARead-only
Get required fields and format for a credential type before creating it. Returns field names, types, and whether fields are required. Use this to understand what authentication data is needed.
Inputs: credentialType (required).
n8n_get_executionARead-only
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.
Inputs: id (required).
n8n_get_tagARead-only
Get tag details including ID and name. Rarely needed - use list_tags for most cases. Useful for validating tag existence before bulk operations.
Inputs: id (required).
n8n_get_userARead-only
Get detailed user information by ID or email. Only available to instance owner. Returns user profile including role and account status. Use this to verify user details before role changes.
Inputs: identifier (required).
n8n_get_workflowARead-only
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.
Inputs: id (required).
n8n_get_workflow_tagsARead-only
Retrieve tags assigned to a workflow for categorization. Returns array of tag names. Use this to understand workflow organization before bulk operations.
Inputs: id (required).
n8n_list_executionsARead-only
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.
Inputs: workflowId.
n8n_list_tagsARead-only
Retrieve all available tags for workflow organization. Returns tag ID and name. Use this before assigning tags to workflows or to see your tagging structure.
Inputs: limit.
n8n_list_usersARead-only
Retrieve all n8n users with their roles and status. Only available to instance owner. Returns user ID, email, role (owner/admin/member), and disabled status. Use this for user management and auditing.
Inputs: limit.
n8n_list_workflowsARead-only
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.
Inputs: active, tags.
n8n_retry_executionA
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.
Inputs: id (required).
n8n_update_credentialAIdempotent
Update credential name or authentication data. Use this when rotating API keys or changing OAuth tokens. Workflows using this credential will use updated auth immediately.
Inputs: id (required), name, data.
n8n_update_tagAIdempotent
Rename an existing tag. All workflows using this tag will automatically reflect the new name. Use this to standardize tag naming across workflows.
Inputs: id (required), name (required).
n8n_update_user_roleAIdempotent
Change user permission level. Only available to instance owner. Admin can manage workflows and credentials. Member has view-only or limited edit access. Cannot change owner role.
Inputs: id (required), role (required).
n8n_update_workflowAIdempotent
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.
Inputs: id (required), name, nodes, connections.
n8n_update_workflow_tagsAIdempotent
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.
Inputs: id (required), tags (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 27 tools
Most tools have distinct purposes targeting specific resources (workflows, credentials, tags, executions, users), with clear action verbs. However, some overlap exists between 'n8n_list_executions' and 'n8n_get_execution' or 'n8n_list_tags' and 'n8n_get_tag', where the list vs. get distinction might be slightly ambiguous without careful reading of descriptions. Overall, the tool boundaries are well-defined.
All tools follow a consistent 'n8n_verb_noun' naming pattern with snake_case throughout. Verbs like create, get, list, update, delete, and execute are used predictably across different resource types (e.g., n8n_create_workflow, n8n_get_workflow, n8n_update_workflow). This uniformity makes the tool set easy to navigate and understand.
With 27 tools, the count is on the high side for a single server, potentially overwhelming for an agent. While n8n is a complex automation platform requiring management of multiple resources (workflows, credentials, tags, executions, users), the tool set feels heavy and could benefit from consolidation or categorization to improve usability without sacrificing functionality.
The tool set provides comprehensive CRUD and lifecycle coverage for all core n8n resources: workflows (create, get, list, update, delete, activate/deactivate, execute, retry), credentials (create, get schema, update, delete), tags (create, get, list, update, delete), executions (get, list, delete, retry), and users (get, list, delete, update role). There are no obvious gaps, and the tools support essential operations like workflow execution and tagging management.
Maintenance
Related MCP Connectors
Build, check and fix n8n workflows from Claude, Cursor or ChatGPT. Built on 1,100+ real n8n node definitions and curated templates, with a validator that repairs common mistakes (wrong node types, missing settings) and returns JSON ready to import into n8n. Sign in with a free gydmation.com account; nothing to install.
26 pay-per-call AI agent tools for marketing, sales, content, research, verification, and integration testing. Agents pay per call via x402 micropayments (USDC on Base), raw JSON in and out. Includes delivery-acceptance receipts (ACCEPT/REJECT/REVIEW), a webhook capture/replay/conformance lab, and n8n workflow validation with bounded JSON-Patch repair.
AI automation platform (n8n/Zapier alternative): build, schedule and run workflows from your agent.
Know when your n8n workflows, URLs, and AI apps break, before your customers do.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage n8n automation workflows through natural language commands, including creating, executing, monitoring, and organizing workflows with full CRUD operations and execution management.122 npm2MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with n8n workflow automation instances through the REST API. Supports workflow management, execution control, tag organization, execution history monitoring, and webhook management.19128 npm5MIT
- AlicenseNot gradedqualityFmaintenanceProvides AI assistants with direct access to the n8n automation platform to manage and execute workflows, variables, and credentials. It features 18 integrated tools that allow for seamless automation management via the Model Context Protocol.128 npm3MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage n8n workflows and executions, including creating, updating, deleting, activating, deactivating, and executing workflows, as well as listing and retrieving execution details.128 npmMIT