M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
N

n8n Workflow Builder

Community
Manage n8n workflows through natural language, connecting AI assistants to your automation platform.
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #315 of 438
Stars
★ 547 Popular
Transport
stdio (local process)
Runtime
Node.js 18+ · Hosted (no local runtime)
Credentials
API key / credential required
License
MIT
Last commit
⚠
Tools
15
44FMRS · D

Based on the provided README, this server is a community project, not officially maintained. It offers a comprehensive toolset, but security depends on proper API key configuration and network access. It is recommended to use with caution in production, and to review permissions regularly.

Strongest · Documentation 13/20 Weakest · Reliability 5/20

Reliability
5/20
Security and permissions
7/20
Maintenance
8/20
Documentation
13/20
Setup experience
11/20
Why each score
Reliability 5/20
Evidence is limited to the README; no source files, tests, or CI workflows were supplied, and the server manifest was not cached, so the claimed 15 tools cannot be cross-checked against real declarations. The README describes a plausible happy path (npx start; list/get/create/execute tools), but there is zero verifiable execution evidence. Per static calibration, reliability cannot exceed 12, and in practice it scores 5. Deductions: no test suite or CI configuration in the supplied material, no way to confirm the MCP init and tool-list handshake, and internal inconsistencies (e.g., 'Zero Configuration' contradicts required N8N_HOST/N8N_API_KEY; two sections both labeled 'Method 2').
Security and permissions 7/20
Credentials are passed via N8N_API_KEY/N8N_HOST environment variables, all examples use placeholders, no real secrets were found, and no red line is triggered (no malware, no covert exfiltration, no real leaked tokens, no irreversible default without confirmation). The server is by design an API wrapper that sends a user-supplied key to a user-supplied host. However, the README recommends the Smithery hosted mode first, which means handing the n8n API key to a third party; destructive tools (delete_workflow, delete_execution, deactivate_workflow) show no confirmation mechanism; and n8n API-key scoping is only hand-waved as 'appropriate permissions' with no visible server-side least-privilege or scoping enforcement. With source code unavailable, these security claims are unverifiable, so 7 is the conservative score.
Maintenance 8/20
The repository is not archived, carries an MIT license, and metadata shows 534 stars and 5 open issues — but stars are only a discovery signal and never add points. No commit history, release cadence, dependency-update evidence, issue-response data, or security-response channel was supplied; the CI badge in the README is untrusted marketing. Because governance details (who maintains, how releases happen, how security issues are handled) cannot be verified from the source, 8 is a conservative estimate.
Documentation 13/20
The README is layered and above average: Smithery/NPX/manual installation, an environment-variable table, concrete Claude Desktop and Cline config JSON, parameter tables for all 15 claimed tools, per-tool-group usage examples, troubleshooting for common errors, an FAQ, and links to four auxiliary guides (GETTING_STARTED/USE_CASES/COMPARISON/TROUBLESHOOTING). Deductions: 'Zero Configuration' contradicts the required env vars; two sections are both numbered 'Method 2'; required API-key permissions and n8n API rate/cost/limits are undocumented; MCP resources and capabilities are not disclosed; troubleshooting is generic and unverified against code. Score: 13.
Setup experience 11/20
The documented setup path is short and clear: run via npx, set two environment variables, and paste one of the provided client configs, with concrete examples for Claude Desktop and Cline — a few-step, actionable path. However, static calibration caps setup at 15 without verifiable execution evidence (real CI plus committed tests), and none was supplied. The npm package's existence, actual npx behavior, Windows path details, and Node 18 checking are all unverified. The hosted Smithery option adds an alternative but also a third-party dependency. Hence 11.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

Best for

  • Teams using n8n for automation who want to leverage AI assistants to simplify workflow management.
  • Users who want to create workflows through conversational interfaces without directly using the n8n Web UI.
  • Developers looking to integrate AI assistants into their existing n8n workflows.

Not for

  • Users without an n8n instance or API key.
  • Those seeking a full low-code visual interface rather than AI-driven management.
  • Users requiring direct support or maintenance from the official n8n product team.

Required permissions

  • Requires access to your n8n instance URL (`N8N_HOST`) and an API key (`N8N_API_KEY`).
  • The API key should have appropriate permissions, typically read/write access to workflows, executions, tags, and audits.
  • The server communicates directly with your n8n instance; it does not store data but requires network access.

Risks and side effects

  • API key leakage could lead to unauthorized access to your n8n workflows and data.
  • Misconfiguration could result in unintended workflow modifications, deletions, or executions.
  • Involving automation actions should first be tested on a small scale.
  • When using third-party hosted services (like Smithery.ai), consider data privacy implications.

Setup

Before you start

Runtime：Node.js 18+ · Hosted (no local runtime)

N8N_HOST required URL of your n8n instance (e.g. http://localhost:5678 or https://your-n8n.com), self-hosted or n8n Cloud.
N8N_API_KEY requiredsecret n8n API key, created under Settings → API Keys in your n8n instance.
  1. Use the hosted version on Smithery.ai (no installation) or run locally with NPX: npx @makafeli/n8n-workflow-builder.\n2. Configure environment variables: N8N_HOST (your n8n instance URL) and N8N_API_KEY (your n8n API key).\n3. Add the server to your AI assistant's MCP configuration. For example, for Claude Desktop, edit claude_desktop_config.json and add the configuration above.
claude_desktop_config.json 
{
  "mcpServers": {
    "n8n-workflow-builder": {
      "command": "npx",
      "args": [
        "@makafeli/n8n-workflow-builder"
      ],
      "env": {
        "N8N_HOST": "http://localhost:5678",
        "N8N_API_KEY": "your-api-key-here"
      }
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "n8n-workflow-builder": {
      "command": "npx",
      "args": [
        "@makafeli/n8n-workflow-builder"
      ],
      "env": {
        "N8N_HOST": "http://localhost:5678",
        "N8N_API_KEY": "your-api-key-here"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add n8n-workflow-builder -e N8N_HOST=http://localhost:5678 -e N8N_API_KEY=your-api-key-here -- npx @makafeli/n8n-workflow-builder

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After adding the config to claude_desktop_config. and restarting, the 15 tools (starting with list_workflows) should appear in the client's tool list; asking "list my workflows" and getting results proves the n8n connection works.

Troubleshooting

  1. Connection refused (ECONNREFUSED): Check that `N8N_HOST` is correct and n8n is running.
  2. 401 error: Verify `N8N_API_KEY` is correct and not expired, and ensure it has proper permissions.
  3. 404 error: Use `list_workflows` to get valid workflow IDs.
  4. Server won't start: Ensure Node.js v18+ is installed, and try `npm cache clean --force`.
  5. Enable debug mode: `DEBUG=n8n-workflow-builder npx @makafeli/n8n-workflow-builder`.

Things to try

Once connected, you can ask your AI assistant things like:

  • List all workflows in my n8n instance
  • Create a workflow with a Schedule Trigger and HTTP Request node and activate it immediately
  • Show my 10 most recent failed workflow executions
  • Create a tag called production for organizing my workflows

Tools 15

list_workflows read-only
List all workflows from your n8n instance.
get_workflow read-only
Retrieve detailed information about a specific workflow.
create_workflow writes
Create a new workflow with nodes and connections.
execute_workflow writes
Manually execute a workflow.
update_workflow writes
Update an existing workflow's configuration.
activate_workflow writes
Activate a workflow to enable automatic execution.
deactivate_workflow writes
Deactivate a workflow to stop automatic execution.
delete_workflow destructive
Permanently delete a workflow.
Show 7 more tools
create_workflow_and_activate writes
Create a new workflow and immediately activate it.
list_executions read-only
List workflow executions with filtering and pagination.
get_execution read-only
Get detailed information about a specific execution.
delete_execution destructive
Delete a workflow execution record.
list_tags read-only
List all workflow tags with pagination.
create_tag writes
Create a new workflow tag for organization.
generate_audit read-only
Generate a comprehensive security audit report.

Use cases

List, browse, and manage n8n workflows via natural language commands.
Automatically create complex workflows by describing them in plain language.
Execute workflows on demand and monitor execution status.
Bulk update or deactivate multiple workflows.
Manage workflow tags for organization and categorization.
Generate security audit reports for compliance purposes.

Supported clients

Claude Desktop
Cline
Continue
Other MCP-compatible clients

Listed from the project's documentation, not tested by this site.

Overview

This MCP server bridges the gap between AI assistants (like Claude Desktop, ChatGPT, Cline, etc.) and your n8n instance, allowing you to create, manage, execute, and monitor n8n workflows through natural language commands. It provides a comprehensive set of tools covering the full workflow lifecycle, including create, read, update, delete, activate/deactivate, execute, view execution history, manage tags, and generate security audit reports. The server uses the official n8n API and requires a valid API key for authentication.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision 411c0a75f512 Data synced 2026-10-12 Read the FMRS scoring method