What is Mcp N8n Builder

mcp-n8n-builder is a Model Context Protocol (MCP) server designed for the programmatic creation and management of n8n workflows. It provides tools for interacting with n8n’s REST API, enabling AI assistants to build, modify, and manage workflows without direct user intervention.

Use cases

Use cases for mcp-n8n-builder include automating repetitive tasks, managing complex workflows programmatically, integrating AI assistants to handle workflow modifications, and providing a user-friendly interface for non-technical users to manage workflows indirectly.

How to use

To use mcp-n8n-builder, configure it through your MCP client by adding the necessary settings for your environment. You can set up the server using JSON configurations for different environments, such as Cline or WSL, and specify environment variables like N8N_HOST and N8N_API_KEY.

Key features

Key features of mcp-n8n-builder include workflow management (create, read, update, delete workflows), execution management (retrieve execution details), schema validation (input and output data validation), error handling (detailed error messages), extensive documentation, and search & filter capabilities for workflows.

Where to use

mcp-n8n-builder can be used in various fields that require automation and workflow management, such as software development, data processing, and business process automation, where integration with n8n is beneficial.

mcp-n8n-builder

A Model Context Protocol (MCP) server for programmatic creation and
management of n8n workflows. This server provides tools and resources
for interacting with n8n’s REST API, allowing AI assistants to build,
modify, and manage workflows without direct user intervention.

Features

• 🔄 Workflow Management: Create, read, update, delete, activate,
  and deactivate workflows
• 📊 Execution Management: List and retrieve workflow execution
  details
• ✅ Schema Validation: Comprehensive validation with Zod for both
  input and output data
• 🔍 Node Validation: Validates node types against n8n’s available
  nodes before workflow creation to prevent errors
• 🤔 Smart Suggestions: Provides suggestions for similar node
  types when invalid nodes are detected
• 🛠️ Error Handling: Detailed error messages for troubleshooting
• 📝 Documentation: Extensive documentation for all tools and
  resources
• 🔍 Search & Filter: Filter workflows by name, tags, or active
  status

Configuration

This server requires configuration through your MCP client. Here are
examples for different environments:

Cline Configuration

Add this to your Cline MCP settings:

Claude Desktop with WSL Configuration

For WSL environments, add this to your Claude Desktop configuration:

{
  "mcpServers": {
    "n8n-workflow-builder": {
      "command": "wsl.exe",
      "args": [
        "bash",
        "-c",
        "N8N_HOST=http://localhost:5678/api/v1 N8N_API_KEY=your-n8n-api-key OUTPUT_VERBOSITY=concise npx -y mcp-n8n-builder"
      ]
    }
  }
}

Environment Variables

The server can be configured using environment variables:

MCP Tools

Node Management

• list_available_nodes: Lists all available nodes in the n8n
  instance. IMPORTANT: Use this tool BEFORE creating or updating
  workflows to ensure you only use valid node types. This helps
  prevent errors caused by using node types that don’t exist in the
  current n8n instance.

Workflow Management

• list_workflows: Lists all workflows from n8n with their basic
  information including ID, name, status, creation date, and tags.
  Results can be filtered by active status, tags, or name.
• create_workflow: Creates a new workflow in n8n with specified
  nodes and connections. Returns the created workflow with its
  assigned ID. Validates that all node types exist in the n8n
  instance.
• get_workflow: Retrieves complete details of a specific workflow by
  its ID, including all nodes, connections, settings, and metadata.
• update_workflow: Updates an existing workflow with new
  configuration. The entire workflow structure must be provided, not
  just the parts being changed. Validates that all node types exist in
  the n8n instance.
• delete_workflow: Permanently deletes a workflow by its ID. This
  action cannot be undone.
• activate_workflow: Activates a workflow by its ID, enabling it to
  run automatically based on its trigger.
• deactivate_workflow: Deactivates a workflow by its ID, preventing
  it from running automatically.

Execution Management

• list_executions: Lists workflow execution history with details on
  success/failure status, duration, and timestamps. Results can be
  filtered by workflow ID, status, and limited to a specific number.
• get_execution: Retrieves detailed information about a specific
  workflow execution, including execution time, status, and optionally
  the full data processed at each step.

MCP Resources

• n8n://workflows: List of all workflows in n8n
• n8n://workflows/{id}: Details of a specific n8n workflow
• n8n://executions/{id}: Details of a specific n8n workflow
  execution

Development

Setup

1. Clone the repository
2. Install dependencies:

npm install

3. Build the project:

npm run build

4. Run in development mode:

npm run dev

Publishing

The project uses changesets for version management. To publish:

1. Create a changeset:

npm changeset

2. Version the package:

npm changeset version

3. Publish to npm:

npm release

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT License - see the LICENSE file for details.

Acknowledgments

• Built on the
  Model Context Protocol
• Powered by n8n