What can you do with this server?

This n8n Workflow Builder MCP server provides an AI-friendly interface for programmatically creating and managing n8n workflows within the Cursor IDE. With it, you can: * Create, list, and manage n8n workflows * Manipulate workflow nodes: Add, edit, delete, and connect nodes * Discover node types: Explore available n8n nodes with optional filtering * Configure node details: Set parameters, type versions, and webhook IDs * Integrate AI components: Connect language models, agents, tools, and memory nodes * Add specialized connections: Support for LangChain nodes and AI-specific components The server is designed specifically for AI agents to automate workflow creation and modification tasks.

Which integrations are available for this server?

Supports integration with LangChain components in n8n workflows, offering special tools for connecting AI components and establishing connections between agent nodes, model nodes, and tool nodes. Provides tools for building and manipulating n8n workflows through an AI-friendly interface, including creating new workflows, adding/editing nodes, managing connections between nodes, and discovering available node types.

How do I use n8n-workflow-builder-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@n8n-workflow-builder-mcp create a workflow that fetches new GitHub issues and sends them to Slack" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ja ko ru zh

n8n-workflow-builder-mcp

by ifmelate

Overview Schema Source Related Servers Score Discussions Admin

JavaScript

Local

n8n Workflow Builder MCP

A Model Context Protocol (MCP) server for building and manipulating n8n workflows. Build n8n workflows just by prompting with AI — works with Claude Code, VS Code, Cursor, and any MCP-compatible client.

DEMO VIDEO:

Watch the video

Cursor rules

File with rules is in rules/n8n-mcp-server-rules.mdc

Related MCP server: mcp-n8n-builder

Key Features

Workflow Management: Create, update, and execute n8n workflows programmatically (execute is not implemented yet)
Node Discovery: Explore available n8n nodes and their capabilities
Connection Management: Create connections between workflow nodes
AI Integration: Special tools for connecting AI components in workflows
AI-Friendly Interface: Designed specifically for interaction with AI agents
N8N Version Management: Automatic version detection and compatibility handling - supports 184+ n8n versions (1.86.0 – 2.6.2) with dynamic node filtering and "closest lower version" matching for backward compatibility

Prerequisites

Node.js (v18 or higher)
npm (for npx command)
An MCP-compatible client (Claude Code, VS Code, Cursor, etc.)

Installation & Setup

Getting your n8n API Key

Open your n8n instance in a browser
Go to Settings > API Keys
Click Create API Key
Copy the generated key and use it in your configuration

Claude Code (Recommended)

Add the MCP server using the Claude Code CLI:

claude mcp add n8n-workflow-builder -- npx -y n8n-workflow-builder-mcp

Then set the environment variables:

claude mcp add n8n-workflow-builder \
  -e N8N_API_URL=http://localhost:5678 \
  -e N8N_API_KEY=your-n8n-api-key-here \
  -- npx -y n8n-workflow-builder-mcp

N8N_VERSION is optional — the server auto-detects it from the API.

VS Code / Cursor

Add to your MCP config file (.vscode/mcp.json for VS Code, .cursor/mcp.json for Cursor):

{
  "mcpServers": {
    "n8n-workflow-builder": {
      "command": "npx",
      "args": ["-y", "n8n-workflow-builder-mcp"],
      "env": {
        "N8N_API_URL": "http://localhost:5678",
        "N8N_API_KEY": "your-n8n-api-key-here"
      }
    }
  }
}

Restart your IDE for changes to take effect.

Development Installation

For development or local testing, clone and build from source:

git clone https://github.com/ifmelate/n8n-workflow-builder-mcp.git
cd n8n-workflow-builder-mcp
npm install
npm run build

Then point your MCP client to the built entry point:

# Claude Code
claude mcp add n8n-workflow-builder -- node /absolute/path/to/n8n-workflow-builder-mcp/dist/index.js

# VS Code / Cursor — use the same JSON config above with "command": "node" and "args": ["/absolute/path/to/dist/index.js"]

For development with auto-rebuild:

npm run dev

Available MCP Tools

The server provides the following tools for working with n8n workflows:

Core Workflow Management

Tool Name	Description	Key Parameters
create_workflow	Create a new n8n workflow	`workflow_name`, `workspace_dir`
list_workflows	List workflows in the workspace	`limit` (optional), `cursor` (optional)
get_workflow_details	Get detailed information about a specific workflow	`workflow_name`, `workflow_path` (optional)
validate_workflow	Validate a workflow file against node schemas and connectivity	`workflow_name`, `workflow_path` (optional)

Node Management

Tool Name	Description	Key Parameters
add_node	Add a new node to a workflow	`workflow_name`, `node_type`, `position` (optional), `parameters` (optional), `node_name` (optional), `typeVersion` (optional), `webhookId` (optional), `workflow_path` (optional), `connect_from` (optional), `connect_to` (optional)
edit_node	Edit an existing node in a workflow	`workflow_name`, `node_id`, `node_type` (optional), `node_name` (optional), `position` (optional), `parameters` (optional), `typeVersion` (optional), `webhookId` (optional), `workflow_path` (optional), `connect_from` (optional), `connect_to` (optional)
delete_node	Delete a node from a workflow	`workflow_name`, `node_id`, `workflow_path` (optional)
list_available_nodes	List available node types with optional filtering. Supports tag-style synonyms and multi-token OR/AND logic	`search_term` (optional), `n8n_version` (optional), `limit` (optional), `cursor` (optional), `tags` (optional, default: true), `token_logic` (optional: 'or' default, or 'and')

Connection Management

Tool Name	Description	Key Parameters
add_connection	Create a connection between two nodes	`workflow_name`, `source_node_id`, `source_node_output_name`, `target_node_id`, `target_node_input_name`, `target_node_input_index` (optional), `workflow_path` (optional)
add_ai_connections	Wire AI model, tools, and memory to an agent	`workflow_name`, `agent_node_id`, `model_node_id` (optional), `tool_node_ids` (optional), `memory_node_id` (optional), `embeddings_node_id` (optional), `vector_store_node_id` (optional), `vector_insert_node_id` (optional), `vector_tool_node_id` (optional), `workflow_path` (optional)
connect_main_chain	Build a minimal main path through AI workflow nodes (Trigger → Model → Memory → Embeddings → Doc Loader → Vector Store → Vector Tool → Agent)	`workflow_name`, `workflow_path` (optional), `dry_run` (optional), `idempotency_key` (optional)

Workflow Planning & Composition

Tool Name	Description	Key Parameters
plan_workflow	Create a non-destructive plan (nodes and connections) to update a workflow. Does not write files	`workflow_name`, `target` (nodes, connections), `workspace_dir` (optional)
review_workflow_plan	Apply a plan in-memory and return validation errors, warnings, and suggested fixes. Does not write files	`workflow_name`, `plan`, `workflow_path` (optional)
apply_workflow_plan	Apply a previously reviewed plan to the workflow on disk (atomic write)	`workflow_name`, `plan`, `workflow_path` (optional)
compose_ai_workflow	Compose a complex AI workflow (agent + model + memory + embeddings + vector + tools + trigger) in one call, including wiring and basic validation	`workflow_name`, `plan`, `n8n_version` (optional)

Parameter Management

Tool Name	Description	Key Parameters
suggest_node_params	Suggest minimal valid parameters for a node type using defaults and required fields	`node_type`, `typeVersion` (optional), `existing_parameters` (optional)
list_missing_parameters	List required parameters missing for a node considering visibility rules	`node_type`, `typeVersion` (optional), `parameters`
fix_node_params	Return parameters with defaults applied for required fields that are missing	`node_type`, `typeVersion` (optional), `parameters` (optional)

Templates & Discovery

Tool Name	Description	Key Parameters
list_template_examples	List node usage examples extracted from free templates. Filter by node_type or template_name	`node_type` (optional), `template_name` (optional), `limit` (optional), `cursor` (optional)
get_n8n_version_info	Get current N8N version and capabilities	`random_string`

Validation behavior

validate_workflow promotes warnings to errors and additionally fails when any enabled node is not connected (directly or via AI ports) to the main chain starting at the inferred startNode. Use connect_from/connect_to or add_ai_connections to fix connectivity.

Troubleshooting

General

Check your MCP config — make sure JSON is valid and the server name matches.
Update Node.js to the latest LTS version.
Clear npm cache if npx fails: npm cache clean --force
Try global install as a fallback: npm install -g n8n-workflow-builder-mcp

Claude Code

Run claude mcp list to verify the server is registered.
Check logs with claude mcp logs n8n-workflow-builder.

VS Code / Cursor

Check the Output panel — select "MCP" from the dropdown to see server logs.
Make sure the server is enabled in Settings > Features > MCP Servers.
Restart the IDE after config changes.

Project Structure

/src: Main source code
/src/tools: MCP tools implementation
/src/models: Data models
/src/utils: Utility functions
/src/middleware: Authentication and middleware
/config: Configuration files
/tests: Test files
/workflow_nodes: n8n node definitions
/docs: Additional documentation

Contributing

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

Fork the repository
Create your feature branch (git checkout -b feature/amazing-feature)
Commit your changes (git commit -m 'Add some amazing feature')
Push to the branch (git push origin feature/amazing-feature)
Open a Pull Request

License

MIT License

Available Tools

10 tools

add_ai_connectionsD

ParametersJSON Schema

Name	Required	Description
`agent_node_id`	Yes	The ID of the agent node that will use the model and tools
`memory_node_id`	No	The ID of the memory node (optional)
`model_node_id`	No	The ID of the language model node (optional)
`tool_node_ids`	No	Array of tool node IDs to connect to the agent (optional)
`workflow_name`	Yes	The Name of the workflow to add the AI connections to

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

add_connectionD

ParametersJSON Schema

Name	Required	Description
`source_node_id`	Yes	The ID of the source node for the connection
`source_node_output_name`	Yes	The name of the output handle on the source node (e.g., 'main')
`target_node_id`	Yes	The ID of the target node for the connection
`target_node_input_index`	No	The index for the target node's input handle (default: 0)
`target_node_input_name`	Yes	The name of the input handle on the target node (e.g., 'main')
`workflow_name`	Yes	The Name of the workflow to add the connection to

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

add_nodeD

ParametersJSON Schema

Name	Required	Description
`node_name`	No	The name for the new node (e.g., 'My Gmail Node')
`node_type`	Yes	The type of node to add (e.g., 'gmail', 'slack', 'openAi'). You can specify with or without the 'n8n-nodes-base.' prefix. The system will handle proper casing (e.g., 'openai' will be converted to 'openAi' if that's the correct casing).
`parameters`	No	The parameters for the node
`position`	No	The position of the node {x,y} - will be converted to [x,y] for N8nWorkflowNode
`typeVersion`	No	The type version for the node (e.g., 1, 1.1). Defaults to 1 if not specified.
`webhookId`	No	Optional webhook ID for certain node types like triggers.
`workflow_name`	Yes	The Name of the workflow to add the node to
`workflow_path`	No	Optional direct path to the workflow file (absolute or relative to current working directory). If not provided, uses standard workflow_data directory approach.

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

create_workflowD

ParametersJSON Schema

Name	Required	Description	Default
`workflow_name`	Yes	The name for the new workflow
`workspace_dir`	Yes	Absolute path to the project root directory where workflow_data will be stored

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

delete_nodeD

ParametersJSON Schema

Name	Required	Description
`node_id`	Yes	The ID of the node to delete
`workflow_name`	Yes	The Name of the workflow containing the node
`workflow_path`	No	Optional direct path to the workflow file (absolute or relative to current working directory). If not provided, uses standard workflow_data directory approach.

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

edit_nodeD

ParametersJSON Schema

Name	Required	Description
`node_id`	Yes	The ID of the node to edit
`node_name`	No	The new name for the node
`node_type`	No	The new type for the node (e.g., 'gmail', 'slack', 'openAi'). You can specify with or without the 'n8n-nodes-base.' prefix. The system will handle proper casing (e.g., 'openai' will be converted to 'openAi' if that's the correct casing).
`parameters`	No	The new parameters
`position`	No	The new position {x,y} - will be converted to [x,y]
`typeVersion`	No	The new type version for the node
`webhookId`	No	Optional new webhook ID for the node.
`workflow_name`	Yes	The Name of the workflow containing the node
`workflow_path`	No	Optional workflow path to the workflow file

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_n8n_version_infoD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_workflow_detailsD

ParametersJSON Schema

Name	Required	Description	Default
`workflow_name`	Yes	The Name of the workflow to get details for
`workflow_path`	No	Optional direct path to the workflow file (absolute or relative to current working directory). If not provided, uses standard workflow_data directory approach.

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_available_nodesD

ParametersJSON Schema

Name	Required	Description	Default
`n8n_version`	No	Filter nodes by N8N version compatibility. If not provided, uses current configured N8N version.
`search_term`	No	An optional search term to filter nodes by their name, type, or description.

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_workflowsD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

10 tool updatesv1.0.0Aug 15, 2025
- First observedadd_ai_connections
- First observedadd_connection
- First observedadd_node
- First observedcreate_workflow
- First observeddelete_node
- First observededit_node
- First observedget_n8n_version_info
- First observedget_workflow_details
- First observedlist_available_nodes
- First observedlist_workflows

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2/5.0

Scored 2026-04-18 10:00 across 10 tools

Disambiguation4/5

Most tools have distinct purposes targeting different aspects of n8n workflow management (e.g., create_workflow vs. list_workflows, add_node vs. edit_node vs. delete_node). However, add_ai_connections and add_connection could potentially be confused without descriptions, as their relationship is unclear—they might overlap in handling connections.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case throughout (e.g., add_connection, create_workflow, get_workflow_details). There are no deviations in naming conventions, making the set predictable and readable.

Tool Count5/5

With 10 tools, the count is well-scoped for a workflow builder server, covering core operations like creating, listing, and managing workflows and nodes. Each tool appears to earn its place without being excessive or insufficient for the domain.

Completeness3/5

The tools cover basic CRUD operations for workflows and nodes (create, list, get, edit, delete), but there are notable gaps. For example, there's no update_workflow or delete_workflow tool, and the absence of descriptions makes it hard to assess if AI connections and general connections are fully covered, potentially leaving dead ends in workflow management.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

microservices.sh
sh.microservices
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Cloud Platforms Agent Orchestration Developer Tools
21
llm-orchestration-agent-mcp
ai.getvda
LLM Orchestration Agent (Mcp)
Agent Orchestration Autonomous Agents
1
secureflows-mcp A
io.github.michal-lefler
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
Code Analysis Developer Tools Security
181
mcp-serverOAuth
com.niftypm
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Project Management Communication File Systems
2

Related MCP Servers

n8n MCP Server
App Automation Developer Tools
illuminaresolutions
A
license
B
quality
D
maintenance
An MCP server enabling secure interaction with n8n workflows, executions, and settings via the Model Context Protocol, designed for integration with Large Language Models (LLMs).
Updated 2 years ago (2025-02-19 14:57 UTC)
33
48
119
MIT
mcp-n8n-builder
App Automation Developer Tools
spences10
A
license
A
quality
D
maintenance
🪄 MCP server for programmatic creation and management of n8n workflows. Enables AI assistants to build, modify, and manage workflows without direct user intervention through a comprehensive set of tools and resources for interacting with n8n's REST API.
Updated a day ago (2026-09-10 03:32 UTC)
10
24
86
MIT
n8n-manager-mcp
App Automation AI & Machine Learning Developer Tools
ellmos-ai
A
license
B
quality
A
maintenance
MCP server for managing n8n workflows through AI assistants. Supports workflow CRUD operations, synchronization, inspection, and execution support for automation-focused workflows.
Updated a day ago (2026-09-10 08:00 UTC)
19
190
2
MIT
mcp-n8n
App Automation Developer Tools
backsoul
A
license
Not graded
quality
D
maintenance
MCP server for integrating with n8n, enabling workflow automation and management through natural language.
Updated a year ago (2025-09-17 10:59 UTC)
158
1
MIT

n8n Workflow Builder MCP

DEMO VIDEO:

Cursor rules

Key Features

Prerequisites

Installation & Setup

Getting your n8n API Key

Claude Code (Recommended)

VS Code / Cursor

Development Installation

Available MCP Tools

Core Workflow Management

Node Management

Connection Management

Workflow Planning & Composition

Parameter Management

Templates & Discovery

Validation behavior

Troubleshooting

General

Claude Code

VS Code / Cursor

Project Structure

Contributing

License

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Appeared in Searches