MCP D4ed53bd

MCPAI代理

提供方 未标注

AI代理 stdio · 本地进程 OAuth 授权 社区 / 第三方
查看接入方式

全面解析MCP N8n BuilderMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,MCP N8n Builder能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

MCP D4ed53bd 属于AI代理类 MCP 服务器,stdio · 本地进程,OAuth 授权,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
npm install mcp-server\"

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP D4ed53bd当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

6.9 KB
来自项目仓库与上游目录的原文,未做删改

mcp-n8n-builder

A Model Context Protocol (MCP) server for programmatic creation and
management of n8n workflows. This server provides tools and resources
for interacting with n8n's REST API, allowing AI assistants to build,
modify, and manage workflows without direct user intervention.

Features

  • 🔄 Workflow Management: Create, read, update, delete, activate,
    and deactivate workflows
  • 📊 Execution Management: List and retrieve workflow execution
    details
  • ✅ Schema Validation: Comprehensive validation with Zod for both
    input and output data
  • 🔍 Node Validation: Validates node types against n8n's available
    nodes before workflow creation to prevent errors
  • 🤔 Smart Suggestions: Provides suggestions for similar node
    types when invalid nodes are detected
  • 🛠️ Error Handling: Detailed error messages for troubleshooting
  • 📝 Documentation: Extensive documentation for all tools and
    resources
  • 🔍 Search & Filter: Filter workflows by name, tags, or active
    status

⚠️ Token Consumption Warning

This tool is a "token monster" due to the nature of n8n workflows:

  • N8N workflows are complex JSON structures with nested nodes, connections, parameters, and settings
  • A single workflow can easily consume thousands of tokens when viewed or edited
  • The JSON structure cannot be meaningfully reduced without losing essential workflow information
  • LLM context windows are finite - complex workflows may exceed available context

Mitigation Strategies

The tool implements several optimizations to reduce token usage:

  • Verbosity Control: Use OUTPUT_VERBOSITY=concise (default) for summaries instead of full JSON
  • Object Simplification: Workflow listings show only essential fields (id, name, status, node count)
  • Selective Guide Inclusion: Error messages include only relevant sections of the composition guide
  • Per-tool Verbosity: Override verbosity on individual tool calls with the verbosity parameter

Recommended Usage

  • List workflows first to identify what you need (low token cost)
  • Work with simple workflows when possible
  • Use concise verbosity unless you specifically need full JSON
  • Break complex workflows into smaller pieces for easier management
  • Consider the token cost before retrieving or editing large workflows

Configuration

This server requires configuration through your MCP client. Here are
examples for different environments:

Cline Configuration

Add this to your Cline MCP settings:```json
{
"mcpServers": {
"n8n-workflow-builder": {
"command": "npx",
"args": ["-y", "mcp-n8n-builder"],
"env": {
"N8N_HOST": "http://localhost:5678/api/v1",
"N8N_API_KEY": "your-n8n-api-key",
"OUTPUT_VERBOSITY": "concise" // Options: 'concise' or 'full'
}
}
}
}


### Claude Desktop with WSL Configuration

For WSL environments, add this to your Claude Desktop configuration:```json
{
    "mcpServers": {
        "n8n-workflow-builder": {
            "command": "wsl.exe",
            "args": [
                "bash",
                "-c",
                "N8N_HOST=http://localhost:5678/api/v1 N8N_API_KEY=your-n8n-api-key OUTPUT_VERBOSITY=concise npx -y mcp-n8n-builder"
            ]
        }
    }
}

Environment Variables

The server can be configured using environment variables:

Variable Description Default
N8N_HOST URL of the n8n API http://localhost:5678/api/v1
N8N_API_KEY API key for n8n authentication ""
SERVER_NAME Name of the MCP server "n8n-workflow-builder"
SERVER_VERSION Version of the MCP server Package version
LOG_LEVEL Logging level "info"
CACHE_ENABLED Enable caching false
CACHE_TTL Cache TTL in seconds 300
OUTPUT_VERBOSITY Output verbosity level (concise or full) "concise"

MCP Tools

Node Management

  • list_available_nodes: Lists all available nodes in the n8n
    instance. IMPORTANT: Use this tool BEFORE creating or updating
    workflows to ensure you only use valid node types. This helps
    prevent errors caused by using node types that don't exist in the
    current n8n instance.

Workflow Management

  • list_workflows: Lists all workflows from n8n with their basic
    information including ID, name, status, creation date, and tags.
    Results can be filtered by active status, tags, or name.
  • create_workflow: Creates a new workflow in n8n with specified
    nodes and connections. Returns the created workflow with its
    assigned ID. Validates that all node types exist in the n8n
    instance.
  • get_workflow: Retrieves complete details of a specific workflow by
    its ID, including all nodes, connections, settings, and metadata.
  • update_workflow: Updates an existing workflow with new
    configuration. The entire workflow structure must be provided, not
    just the parts being changed. Validates that all node types exist in
    the n8n instance.
  • delete_workflow: Permanently deletes a workflow by its ID. This
    action cannot be undone.
  • activate_workflow: Activates a workflow by its ID, enabling it to
    run automatically based on its trigger.
  • deactivate_workflow: Deactivates a workflow by its ID, preventing
    it from running automatically.

Execution Management

  • list_executions: Lists workflow execution history with details on
    success/failure status, duration, and timestamps. Results can be
    filtered by workflow ID, status, and limited to a specific number.
  • get_execution: Retrieves detailed information about a specific
    workflow execution, including execution time, status, and optionally
    the full data processed at each step.

MCP Resources

  • n8n://workflows: List of all workflows in n8n
  • n8n://workflows/{id}: Details of a specific n8n workflow
  • n8n://executions/{id}: Details of a specific n8n workflow
    execution

Development

Setup

  1. Clone the repository
  2. Install dependencies:```bash
    npm install

3. Build the project:```bash
npm run build
  1. Run in development mode:```bash
    npm run dev

### Publishing

The project uses changesets for version management. To publish:

1. Create a changeset:```bash
npm changeset
  1. Version the package:```bash
    npm changeset version

3. Publish to npm:```bash
npm release

Contributing

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

License

MIT License - see the LICENSE file for details.

Acknowledgments

  • Built on the
    Model Context Protocol
  • Powered by n8n

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
MCP D4ed53bd 怎么安装?

在客户端按下面的安装命令接入:npm install mcp-server\"。装完在客户端配置里引用同一个包或端点。

MCP D4ed53bd 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

MCP D4ed53bd 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP D4ed53bd 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

MCP D4ed53bd 能提供哪些能力?

资料显示能力标签包括 版本管理、构建工具、JavaScript、OAuth认证。具体工具清单以官方文档为准。

MCP D4ed53bd 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

MCP D4ed53bd 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。