Skip to main content
Glama
n8n Workflow Builder MCP Server

n8n Workflow Builder MCP Server

by Jimmy974

n8n Workflow Builder MCP Server

A Model Context Protocol (MCP) server for programmatically creating and managing n8n workflows.

Features

  • Create workflows with nodes and connections

  • Validate workflow specifications

  • Export complete workflow configurations

  • REST API interface through MCP

Related MCP server: MCP Server for n8n Integration

Installation

Installing via Smithery

To install n8n Workflow Builder for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install n8n-workflow-builder --client claude

Manual Installation

  1. Clone the repository:

git clone https://github.com/[your-username]/n8n-workflow-builder.git
cd n8n-workflow-builder
  1. Install dependencies:

npm install
  1. Compile TypeScript:

npx tsc
  1. Start the server:

npm start

Usage

The server provides a create_workflow tool that accepts a workflow specification:

{
  "nodes": [
    {
      "type": "n8n-nodes-base.httpRequest",
      "name": "HTTP Request",
      "parameters": {
        "url": "https://example.com",
        "method": "GET"
      }
    }
  ],
  "connections": []
}

Configuration

Add the server to your MCP configuration:

{
  "n8n-workflow-builder": {
    "command": "node",
    "args": ["/path/to/n8n-workflow-builder/dist/index.js"]
  }
}

License

MIT

Available Tools

1 tool
create_workflowC

Create and configure n8n workflows programmatically

Inputs: nodes (required), connections.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'create_workflow' has a clear, distinct purpose that cannot be confused with any other tool in this set.

    Naming Consistency5/5

    The naming pattern is perfectly consistent as there is only one tool. It follows a clear verb_noun convention ('create_workflow'), which would be easy to maintain if more tools were added.

    Tool Count2/5

    A single tool is insufficient for a 'Workflow Builder' server, which implies capabilities like listing, updating, executing, or deleting workflows. This feels thin and under-scoped for the apparent domain of workflow management.

    Completeness1/5

    The tool surface is severely incomplete for workflow building. It only offers creation, with no ability to read, update, delete, execute, or manage existing workflows. This creates significant dead ends for agents trying to perform basic lifecycle operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers