Skip to main content
Glama
deenesjakoruzh
ifmelate

n8n-workflow-builder-mcp

by ifmelate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

n8n Workflow Builder MCP

n8n 워크플로우를 구축하고 조작하기 위한 MCP(Model Context Protocol) 서버입니다. 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 키 얻기

  1. 브라우저에서 n8n 인스턴스를 엽니다.

  2. Settings > API Keys로 이동합니다.

  3. Create API Key를 클릭합니다.

  4. 생성된 키를 복사하여 구성에 사용합니다.

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

두 노드 간의 연결 생성

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 (노드, 연결), workspace_dir (선택 사항)

review_workflow_plan

계획을 메모리 내에서 적용하고 검증 오류, 경고 및 제안된 수정 사항 반환. 파일에 쓰지 않음

workflow_name, plan, workflow_path (선택 사항)

apply_workflow_plan

이전에 검토된 계획을 디스크의 워크플로우에 적용 (원자적 쓰기)

workflow_name, plan, workflow_path (선택 사항)

compose_ai_workflow

복잡한 AI 워크플로우(에이전트 + 모델 + 메모리 + 임베딩 + 벡터 + 도구 + 트리거)를 한 번의 호출로 구성 (연결 및 기본 검증 포함)

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는 경고를 오류로 승격시키며, 활성화된 노드가 추론된 startNode에서 시작하는 메인 체인에 (직접 또는 AI 포트를 통해) 연결되지 않은 경우 실패합니다. 연결성을 수정하려면 connect_from/connect_to 또는 add_ai_connections를 사용하세요.

문제 해결

일반

  1. MCP 구성 확인 — JSON이 유효하고 서버 이름이 일치하는지 확인하세요.

  2. Node.js 업데이트 — 최신 LTS 버전으로 업데이트하세요.

  3. npm 캐시 지우기 — npx가 실패하는 경우: npm cache clean --force

  4. 전역 설치 시도 — 대체 방법: 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: 추가 문서

기여

기여를 환영합니다! 자유롭게 Pull Request를 제출해 주세요.

  1. 저장소 포크

  2. 기능 브랜치 생성 (git checkout -b feature/amazing-feature)

  3. 변경 사항 커밋 (git commit -m 'Add some amazing feature')

  4. 브랜치에 푸시 (git push origin feature/amazing-feature)

  5. Pull Request 열기

라이선스

MIT 라이선스

Available Tools

10 tools
add_ai_connectionsD
ParametersJSON Schema
NameRequiredDescriptionDefault
agent_node_idYesThe ID of the agent node that will use the model and tools
memory_node_idNoThe ID of the memory node (optional)
model_node_idNoThe ID of the language model node (optional)
tool_node_idsNoArray of tool node IDs to connect to the agent (optional)
workflow_nameYesThe 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
NameRequiredDescriptionDefault
source_node_idYesThe ID of the source node for the connection
source_node_output_nameYesThe name of the output handle on the source node (e.g., 'main')
target_node_idYesThe ID of the target node for the connection
target_node_input_indexNoThe index for the target node's input handle (default: 0)
target_node_input_nameYesThe name of the input handle on the target node (e.g., 'main')
workflow_nameYesThe 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
NameRequiredDescriptionDefault
node_nameNoThe name for the new node (e.g., 'My Gmail Node')
node_typeYesThe 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).
parametersNoThe parameters for the node
positionNoThe position of the node {x,y} - will be converted to [x,y] for N8nWorkflowNode
typeVersionNoThe type version for the node (e.g., 1, 1.1). Defaults to 1 if not specified.
webhookIdNoOptional webhook ID for certain node types like triggers.
workflow_nameYesThe Name of the workflow to add the node to
workflow_pathNoOptional 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
NameRequiredDescriptionDefault
workflow_nameYesThe name for the new workflow
workspace_dirYesAbsolute 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
NameRequiredDescriptionDefault
node_idYesThe ID of the node to delete
workflow_nameYesThe Name of the workflow containing the node
workflow_pathNoOptional 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
NameRequiredDescriptionDefault
node_idYesThe ID of the node to edit
node_nameNoThe new name for the node
node_typeNoThe 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).
parametersNoThe new parameters
positionNoThe new position {x,y} - will be converted to [x,y]
typeVersionNoThe new type version for the node
webhookIdNoOptional new webhook ID for the node.
workflow_nameYesThe Name of the workflow containing the node
workflow_pathNoOptional 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
NameRequiredDescriptionDefault

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
NameRequiredDescriptionDefault
workflow_nameYesThe Name of the workflow to get details for
workflow_pathNoOptional 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
NameRequiredDescriptionDefault
n8n_versionNoFilter nodes by N8N version compatibility. If not provided, uses current configured N8N version.
search_termNoAn 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
NameRequiredDescriptionDefault

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.

  1. 10 tool updatesv1.0.0
    • 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 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

Related MCP Connectors

Related MCP Servers

  • n8n MCP Server

    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).
    33
    58 npm
    119
    MIT

  • mcp-n8n-builder

    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.
    10
    50 npm
    86
    MIT

  • mcp-n8n

    backsoul
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for integrating with n8n, enabling workflow automation and management through natural language.
    318 npm
    1
    MIT

Appeared in Searches