n8n-custom-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the MCP HTTP endpoint | 3000 |
| N8N_HOST | Yes | URL to the n8n instance | http://localhost:5678 |
| N8N_API_KEY | Yes | API Key from n8n Settings | |
| MCP_TRANSPORT | No | Transport mode (e.g., sse, stdio) | sse |
| DB_POSTGRESDB_HOST | No | PostgreSQL host for DB fallback | |
| DB_POSTGRESDB_PORT | No | PostgreSQL port | |
| DB_POSTGRESDB_USER | No | PostgreSQL user | |
| DB_POSTGRESDB_DATABASE | No | PostgreSQL database name | |
| DB_POSTGRESDB_PASSWORD | No | PostgreSQL password |
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 |
|---|---|
| list_workflowsB | List all workflows in n8n |
| get_workflowA | Get detailed information about a workflow (nodes, connections, settings) |
| create_workflowC | Create a new workflow |
| update_workflowC | Update an existing workflow |
| delete_workflowC | Delete a workflow |
| activate_workflowC | Activate or deactivate a workflow |
| execute_workflowC | Manually trigger a workflow |
| trigger_webhookB | Trigger a webhook endpoint for testing |
| list_executionsC | List recent workflow executions to check status |
| get_executionA | Get full details of a specific execution for debugging |
| list_node_typesA | List available node types in this n8n instance |
| get_credential_schemaA | Get required fields and structure for a credential type before creating it |
| list_credentialsA | List all credentials available in n8n (parsed from workflows + database fallback) |
| create_credentialC | Create a new credential with automatic validation against schema |
| update_credentialB | Update an existing credential (name, data, or node access) |
| delete_credentialA | Delete a credential with safety checks (blocks if in use unless forced) |
| test_credentialA | Test credential validity by creating a temporary workflow (heavy operation - use sparingly) |
| validate_workflow_structureA | Validate workflow structure before creation/deployment to catch errors early. Checks for: required fields, unique node IDs/names, valid node types, valid connections, circular dependencies, trigger nodes, and disabled node warnings. |
| validate_workflow_credentialsA | Validate workflow credentials before deployment. Checks: credential IDs exist, credential types match node requirements, and optionally tests credential validity. |
| validate_workflow_expressionsA | Validate n8n expressions {{ }} in workflow. Checks: syntax errors in expressions, valid variable references ($json, $node, $vars), and warns about complex logic that should use Code node. |
| lint_workflowA | Lint workflow for best practices. Checks: orphaned nodes, missing error handling, generic node names, hardcoded secrets, and loops without limits. Returns score (0-100) and list of issues. |
| suggest_workflow_improvementsA | Analyze workflow and suggest improvements. Identifies: missing Set nodes for data transformation, missing error handling, slow loops, hardcoded values that should use credentials, missing triggers, and opportunities for merge nodes. |
| search_templatesB | Search n8n.io template library for workflow templates |
| get_template_detailsB | Get full workflow JSON for a template |
| import_templateB | Import template as new workflow with dependency resolution |
| export_workflow_as_templateB | Export workflow as JSON template (safe for sharing) |
| backup_workflowA | Create a backup snapshot of a workflow before making changes |
| list_workflow_backupsA | List all backup versions for a workflow with metadata (timestamp, size, description) |
| restore_workflowA | Restore a workflow to a previous backup version (auto-backups current state first) |
| diff_workflow_versionsA | Compare two workflow backup versions to see what changed (nodes added/removed/modified) |
| get_node_schemaA | Get the parameter schema for a specific n8n node type. Use this to understand what inputs/options a node accepts. |
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 31 tools
Most tools target distinct resources and actions, but there is notable overlap among the analysis tools: lint_workflow and suggest_workflow_improvements both check error handling, hardcoded values, and loops, while validate_workflow_credentials and test_credential both validate credential validity. Detailed descriptions help, but an agent could easily select the wrong validation tool.
All 31 tools follow a consistent snake_case verb_noun pattern, such as list_workflows, create_credential, restore_workflow, and diff_workflow_versions. Even longer names like export_workflow_as_template and validate_workflow_structure remain predictable and readable.
31 tools is above the 25+ threshold and feels heavy for a single MCP server. While the n8n administration scope is broad, several validation, linting, suggestion, and backup tools could be consolidated without losing core capability.
The tool surface covers workflow CRUD, activation, execution, validation, linting, templates, backups, credentials, and node schemas, so agents have no major dead ends in the primary n8n workflow lifecycle. Minor gaps remain around execution lifecycle operations, such as retrying or deleting executions, and there is no workflow tagging or categorization support.