n8n-Management
MCP server for n8n workflow automation — manage workflows, executions, credentials, tags, and users.
What it can do
- N8n List Workflows: 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
- N8n Get Workflow: 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
- N8n Create Workflow: Create a new automation workflow with nodes and connections. Provide workflow name, node array, and connection object. Optionally activate immediately. Returns new workflow with a
What data it sees
Do you need an account
An API key from the service settings is required
MCP server for n8n workflow automation — manage workflows, executions, credentials, tags, and users. Features
- Full workflow lifecycle (create, activate, execute, deactivate, delete) - Execution monitoring and debugging (list, inspect, retry, cleanup)
- Credential management (create, update, rotate, schema lookup)
- Tag-based workflow organization
- User management with role control (owner permissions required)
27 Tools
Workflows: list, get, create, update, delete, activate, deactivate, execute, get tags, update tags Executions: list, get, delete, retry Credentials: create, update, delete, get schema Tags: list, get, create, update, delete Users: list, get, delete, update role
Configuration
- N8N_URL — Your n8n instance URL (e.g. https://your-n8n.example.com)
- N8N_API_KEY — API key from n8n Settings → API → Create API Key
How to connect
How to connect n8n-Management to Claude
The server address to paste into Claude settings:
https://n8n-management--node2flow.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect n8n-Management to ChatGPT
The server address to paste into ChatGPT settings:
https://n8n-management--node2flow.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect n8n-Management to Cursor
The server address to paste into Cursor settings:
https://n8n-management--node2flow.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (27)
Raw names from tools/list. Only developers need these.
| n8n_list_workflows | 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. |
| n8n_get_workflow | 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. |
| n8n_create_workflow | 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. |
| n8n_update_workflow | 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. |
| n8n_delete_workflow | Permanently delete a workflow and all associated execution history. This action cannot be undone. Workflow must be deactivated first. Use with caution. |
| n8n_activate_workflow | 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. |
| n8n_deactivate_workflow | Stop a workflow from listening to triggers. Deactivating prevents automatic execution but preserves workflow configuration. Use before making structure changes. |
| n8n_execute_workflow | 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. |
| n8n_get_workflow_tags | Retrieve tags assigned to a workflow for categorization. Returns array of tag names. Use this to understand workflow organization before bulk operations. |
| n8n_update_workflow_tags | 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. |
| n8n_list_executions | 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. |
| n8n_get_execution | 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. |
| n8n_delete_execution | 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. |
| n8n_retry_execution | 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. |
| n8n_create_credential | 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. |
| n8n_update_credential | 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. |
| n8n_delete_credential | Remove stored credential. Cannot delete credentials currently used in active workflows. Deactivate dependent workflows first. Use with caution as this may break workflows. |
| n8n_get_credential_schema | 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. |
| n8n_list_tags | 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. |
| n8n_get_tag | Get tag details including ID and name. Rarely needed - use list_tags for most cases. Useful for validating tag existence before bulk operations. |
| n8n_create_tag | Create new tag for workflow categorization. Use meaningful names like "production", "staging", "team-marketing", or "urgent". Tags help filter and organize workflows. |
| n8n_update_tag | Rename an existing tag. All workflows using this tag will automatically reflect the new name. Use this to standardize tag naming across workflows. |
| n8n_delete_tag | Remove tag from system. Automatically removes this tag from all workflows using it. Tag removal does not affect workflows themselves, only the tag association. |
| n8n_list_users | 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. |
| n8n_get_user | 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. |
| n8n_delete_user | 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. |
| n8n_update_user_role | 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. |