de en es ja ko ru zh

n8n-workflow-builder-mcp

Name: n8n-workflow-builder-mcp
Author: ifmelate

by ifmelate

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

n8n Workflow Builder MCP

n8nワークフローを構築および操作するためのModel Context Protocol (MCP) サーバーです。AIへのプロンプトだけでn8nワークフローを構築できます。Claude Code、VS Code、Cursor、およびMCP互換クライアントで動作します。

デモ動画:

動画を見る

Cursorルール

ルールファイルは rules/n8n-mcp-server-rules.mdc にあります

Related MCP server: mcp-n8n-builder

主な機能

ワークフロー管理: n8nワークフローをプログラムで作成、更新、実行（実行は未実装）
ノード探索: 利用可能なn8nノードとその機能を探索
接続管理: ワークフローノード間の接続を作成
AI統合: ワークフロー内のAIコンポーネントを接続するための特別なツール
AIフレンドリーなインターフェース: AIエージェントとの対話用に特別に設計
N8Nバージョン管理: 自動バージョン検出と互換性処理 - 184以上のn8nバージョン（1.86.0 – 2.6.2）をサポート。動的なノードフィルタリングと、後方互換性のための「最も近い下位バージョン」マッチング機能付き

前提条件

Node.js (v18以上)
npm (npxコマンド用)
MCP互換クライアント (Claude Code, VS Code, Cursorなど)

インストールとセットアップ

n8n APIキーの取得

ブラウザでn8nインスタンスを開く
Settings > API Keys に移動
Create API Key をクリック
生成されたキーをコピーし、設定で使用する

Claude Code (推奨)

Claude Code CLIを使用してMCPサーバーを追加します:

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

次に、環境変数を設定します:

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 はオプションです。サーバーがAPIから自動的に検出します。

VS Code / Cursor

MCP設定ファイルに追加します（VS Codeの場合は .vscode/mcp.json、Cursorの場合は .cursor/mcp.json）:

{
  "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"
      }
    }
  }
}

変更を反映させるためにIDEを再起動してください。

開発用インストール

開発やローカルテストを行う場合は、ソースからクローンしてビルドします:

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

次に、MCPクライアントをビルドされたエントリポイントに向けます:

# 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"]

自動リビルド付きの開発用:

npm run dev

利用可能なMCPツール

n8nワークフローを操作するために、サーバーは以下のツールを提供します:

コアワークフロー管理

ツール名	説明	主要パラメータ
create_workflow	新しいn8nワークフローを作成	`workflow_name`, `workspace_dir`
list_workflows	ワークスペース内のワークフローを一覧表示	`limit` (オプション), `cursor` (オプション)
get_workflow_details	特定のワークフローの詳細情報を取得	`workflow_name`, `workflow_path` (オプション)
validate_workflow	ノードスキーマと接続性に基づいてワークフローファイルを検証	`workflow_name`, `workflow_path` (オプション)

ノード管理

ツール名	説明	主要パラメータ
add_node	ワークフローに新しいノードを追加	`workflow_name`, `node_type`, `position` (オプション), `parameters` (オプション), `node_name` (オプション), `typeVersion` (オプション), `webhookId` (オプション), `workflow_path` (オプション), `connect_from` (オプション), `connect_to` (オプション)
edit_node	ワークフロー内の既存ノードを編集	`workflow_name`, `node_id`, `node_type` (オプション), `node_name` (オプション), `position` (オプション), `parameters` (オプション), `typeVersion` (オプション), `webhookId` (オプション), `workflow_path` (オプション), `connect_from` (オプション), `connect_to` (オプション)
delete_node	ワークフローからノードを削除	`workflow_name`, `node_id`, `workflow_path` (オプション)
list_available_nodes	オプションのフィルタリング付きで利用可能なノードタイプを一覧表示。タグ形式の同義語やマルチトークンのOR/ANDロジックをサポート	`search_term` (オプション), `n8n_version` (オプション), `limit` (オプション), `cursor` (オプション), `tags` (オプション, デフォルト: true), `token_logic` (オプション: 'or' デフォルト, または 'and')

接続管理

ツール名	説明	主要パラメータ
add_connection	2つのノード間に接続を作成	`workflow_name`, `source_node_id`, `source_node_output_name`, `target_node_id`, `target_node_input_name`, `target_node_input_index` (オプション), `workflow_path` (オプション)
add_ai_connections	AIモデル、ツール、メモリをエージェントに接続	`workflow_name`, `agent_node_id`, `model_node_id` (オプション), `tool_node_ids` (オプション), `memory_node_id` (オプション), `embeddings_node_id` (オプション), `vector_store_node_id` (オプション), `vector_insert_node_id` (オプション), `vector_tool_node_id` (オプション), `workflow_path` (オプション)
connect_main_chain	AIワークフローノードを通る最小限のメインパスを構築 (トリガー → モデル → メモリ → エンベディング → ドキュメントローダー → ベクターストア → ベクターツール → エージェント)	`workflow_name`, `workflow_path` (オプション), `dry_run` (オプション), `idempotency_key` (オプション)

ワークフローの計画と構成

ツール名	説明	主要パラメータ
plan_workflow	ワークフローを更新するための非破壊的な計画（ノードと接続）を作成。ファイルへの書き込みは行わない	`workflow_name`, `target` (nodes, connections), `workspace_dir` (オプション)
review_workflow_plan	計画をメモリ上で適用し、検証エラー、警告、推奨される修正を返す。ファイルへの書き込みは行わない	`workflow_name`, `plan`, `workflow_path` (オプション)
apply_workflow_plan	事前にレビューされた計画をディスク上のワークフローに適用（アトミック書き込み）	`workflow_name`, `plan`, `workflow_path` (オプション)
compose_ai_workflow	複雑なAIワークフロー（エージェント + モデル + メモリ + エンベディング + ベクター + ツール + トリガー）を1回の呼び出しで構成（接続と基本的な検証を含む）	`workflow_name`, `plan`, `n8n_version` (オプション)

パラメータ管理

ツール名	説明	主要パラメータ
suggest_node_params	デフォルト値と必須フィールドを使用して、ノードタイプの最小限の有効なパラメータを提案	`node_type`, `typeVersion` (オプション), `existing_parameters` (オプション)
list_missing_parameters	可視性ルールを考慮して、ノードに不足している必須パラメータを一覧表示	`node_type`, `typeVersion` (オプション), `parameters`
fix_node_params	不足している必須フィールドに対してデフォルト値を適用したパラメータを返す	`node_type`, `typeVersion` (オプション), `parameters` (オプション)

テンプレートと探索

ツール名	説明	主要パラメータ
list_template_examples	無料テンプレートから抽出されたノードの使用例を一覧表示。node_typeまたはtemplate_nameでフィルタリング	`node_type` (オプション), `template_name` (オプション), `limit` (オプション), `cursor` (オプション)
get_n8n_version_info	現在のN8Nバージョンと機能を取得	`random_string`

検証動作

validate_workflow は警告をエラーに昇格させ、さらに有効化されたノードが（直接またはAIポート経由で）推論された startNode から始まるメインチェーンに接続されていない場合に失敗します。接続性を修正するには connect_from/connect_to または add_ai_connections を使用してください。

トラブルシューティング

全般

MCP設定を確認 — JSONが有効であり、サーバー名が一致していることを確認してください。
Node.jsを更新 — 最新のLTSバージョンに更新してください。
npmキャッシュをクリア — npxが失敗する場合: npm cache clean --force
グローバルインストールを試す — フォールバックとして: npm install -g n8n-workflow-builder-mcp

Claude Code

claude mcp list を実行して、サーバーが登録されていることを確認してください。
claude mcp logs n8n-workflow-builder でログを確認してください。

VS Code / Cursor

出力パネルを確認 — ドロップダウンから「MCP」を選択してサーバーログを表示してください。
Settings > Features > MCP Servers でサーバーが有効になっていることを確認してください。
設定変更後はIDEを再起動してください。

プロジェクト構造

/src: メインソースコード
/src/tools: MCPツール実装
/src/models: データモデル
/src/utils: ユーティリティ関数
/src/middleware: 認証とミドルウェア
/config: 設定ファイル
/tests: テストファイル
/workflow_nodes: n8nノード定義
/docs: 追加ドキュメント

貢献

貢献を歓迎します！お気軽にプルリクエストを送信してください。

リポジトリをフォーク
フィーチャーブランチを作成 (git checkout -b feature/amazing-feature)
変更をコミット (git commit -m 'Add some amazing feature')
ブランチにプッシュ (git push origin feature/amazing-feature)
プルリクエストを開く

ライセンス

MITライセンス

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

Deploy Server

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

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

Related MCP Connectors

blinkboxOAuth
io.github.blinkboxhq
Open-source Zapier/n8n alternative as an MCP server: agents build, run and debug your workflows.
App Automation Autonomous Agents
13
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

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
58 npm
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 4 days ago (2026-10-05 17:50 UTC)
10
50 npm
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 6 days ago (2026-10-04 12:17 UTC)
19
133 npm
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)
318 npm
1
MIT

n8n Workflow Builder MCP

デモ動画:

Cursorルール

主な機能

前提条件

インストールとセットアップ

n8n APIキーの取得

Claude Code (推奨)

VS Code / Cursor

開発用インストール

利用可能なMCPツール

コアワークフロー管理

ノード管理

接続管理

ワークフローの計画と構成

パラメータ管理

テンプレートと探索

検証動作

トラブルシューティング

全般

Claude Code

VS Code / Cursor

プロジェクト構造

貢献

ライセンス

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches