McFlow
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKFLOWS_PATH | Yes | Path to your n8n workflows directory |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listB | List all n8n workflows in this project (use deployed to see workflows in n8n) |
| readC | Read a specific n8n workflow JSON file |
| createB | Create a new n8n workflow with REAL nodes only (no mock/placeholder nodes allowed). IMPORTANT: Use dashes in filenames, not underscores (e.g., "my-workflow" not "my_workflow") |
| updateC | Update an existing n8n workflow |
| analyzeC | Analyze a workflow structure and dependencies |
| infoC | Get project or workflow structure information |
| validateC | Validate a workflow structure and check for common issues |
| add_nodeC | Add a REAL n8n node to workflow (no mock/placeholder nodes allowed) |
| connectC | Create a connection between two nodes in a workflow |
| generateC | Generate a workflow from template using REAL n8n nodes (no mock/placeholder nodes). IMPORTANT: Use dashes in filenames, not underscores |
| compileC | Compile all workflows by injecting external code/prompt files |
| deployC | Deploy workflows to n8n instance - handles all n8n import commands internally |
| exportC | Export workflows from n8n - replaces "n8n export:workflow" command |
| executeA | Execute/test an n8n workflow - DO NOT use bash n8n commands, use this tool instead |
| deployedA | List all workflows in n8n instance - replaces "n8n list:workflow" command |
| list_credentialsB | List all credentials in n8n with their IDs - use these IDs in workflow nodes |
| activateC | Activate or deactivate a workflow in n8n |
| startA | Start n8n server - replaces "n8n start" command |
| statusB | Show deployment status of workflows (which are deployed, which need deployment) |
| extract_codeC | Extract code nodes to separate files in workflows/nodes/ for better editing |
| list_codeC | List all extracted code nodes |
| create_moduleC | Create a shared code module that can be used across workflows |
| credentialsA | Analyze credential requirements for workflows (secure - never exposes actual values) |
| add_trackingC | Add generic workflow execution tracking to a workflow (stores data via HTTP requests) |
| configure_trackingC | Configure global tracking settings for workflows |
| add_checkpointC | Add a checkpoint save/restore capability to a workflow |
| generate_appC | Generate a Next.js app for managing workflow data within the current project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_n8n_workflow | Create a new n8n workflow for a specific use case |
| optimize_workflow | Optimize an existing n8n workflow |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| General AI Instructions | General instructions for working with n8n workflows |
| Process Instructions | Instructions for workflow creation process |
| Repository Instructions | Repository-specific instructions |
TDQS
Scored across 27 tools
Most tools have distinct purposes, but some overlap exists. For example, 'list' and 'deployed' both list workflows but in different contexts (project vs n8n instance), which could cause confusion. Similarly, 'analyze' and 'validate' both involve workflow inspection but with different focuses, potentially leading to misselection.
The naming is mostly consistent with a verb-based pattern (e.g., 'activate', 'add_node', 'create', 'deploy'), but there are minor deviations like 'deployed' (past tense verb) and 'info' (noun). Overall, the naming is readable and follows a clear convention, with only a few inconsistencies.
With 27 tools, the count is too high for a focused workflow management server. This many tools suggests feature bloat and can overwhelm agents, making it difficult to navigate and select the right tool efficiently. A more streamlined set of 10-15 tools would be more appropriate.
The tool set provides comprehensive coverage for n8n workflow management, including creation, deployment, execution, analysis, and maintenance. It covers the full lifecycle from 'create' to 'deploy' and 'execute', with additional tools for code extraction, tracking, and validation, leaving no obvious gaps.