n8n Management MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP server (default: 3000, only used with --http) | 3000 |
| N8N_URL | Yes | URL of your n8n instance (e.g. https://n8n.example.com) | |
| N8N_API_KEY | Yes | n8n API key (how to create: https://docs.n8n.io/api/authentication/) |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| n8n_list_workflowsA | 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_workflowA | 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_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. |
| n8n_update_workflowA | 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_workflowA | Permanently delete a workflow and all associated execution history. This action cannot be undone. Workflow must be deactivated first. Use with caution. |
| n8n_activate_workflowA | 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_workflowA | Stop a workflow from listening to triggers. Deactivating prevents automatic execution but preserves workflow configuration. Use before making structure changes. |
| 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. |
| n8n_get_workflow_tagsA | 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_tagsA | 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_executionsA | 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_executionA | 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_executionA | 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_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. |
| 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. |
| n8n_update_credentialA | 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_credentialA | 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_schemaA | 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_tagsA | 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_tagA | 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_tagA | Create new tag for workflow categorization. Use meaningful names like "production", "staging", "team-marketing", or "urgent". Tags help filter and organize workflows. |
| n8n_update_tagA | 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_tagA | 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_usersA | 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_userA | 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_userA | 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_roleA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| manage-workflows | Guide for managing n8n workflows — list, create, activate, execute, and organize with tags |
| debug-execution | Step-by-step guide to diagnose and fix failed n8n workflow executions |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| n8n Server Info | Connection status and available tools for this n8n MCP server |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/node2flow-th/n8n-management-mcp-community'
If you have feedback or need assistance with the MCP directory API, please join our Discord server