MCP N8n Server 60fdc55d

MCP开发工具

提供方 Nourdeo

开发工具 未标注 无需鉴权 社区 / 第三方 Claude DesktopClaude

一个连接Claude AI与n8n工作流自动化的MCP服务器,通过自然语言实现智能工作流创建与管理。

一句话选型结论

按资料字段整理

MCP N8n Server 60fdc55d 属于开发工具类 MCP 服务器,传输方式未标注,无需鉴权,可直接接入 Claude Desktop、Claude,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

支持客户端

适用场景

工作流自动化JavaScript本地部署自然语言处理AI集成开发工具自动化管理

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

    连接成功后客户端会列出约 12 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

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

值得选的地方

  • 资料标注 12 个工具,覆盖面较广,能满足多种调用。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP N8n Server 60fdc55d当前 12 未标注 未标注 无 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Nourdeo上游标注的维护方 Nourdeo
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

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

n8n MCP Server

> A Model Context Protocol (MCP) server that bridges Claude AI with n8n workflow automation, enabling intelligent workflow creation and management through natural language.

Table of Contents

  • What is This?
  • Features
  • Prerequisites
  • Quick Start
  • Installation Methods
  • Method 1: Docker (Recommended)
  • Method 2: Local Development
  • Method 3: Portainer Deployment
  • Configuration
  • Connecting to Claude Desktop
  • Connecting to Claude Code (CLI)
  • Available Tools
  • Usage Examples
  • Project Structure
  • Development
  • Troubleshooting
  • Security Best Practices
  • Contributing
  • License
  • Resources

What is This?

This project provides a Model Context Protocol (MCP) server that connects AI assistants (like Claude) to your n8n workflow automation instance. With this integration, you can:

  • Create workflows using natural language descriptions
  • Manage existing workflows (activate, deactivate, update, delete)
  • Monitor executions and debug issues
  • Query workflow status and configuration
  • Automate workflow operations through conversational AI

Why Use This?

Instead of manually building workflows in the n8n UI, you can simply describe what you want to Claude:

> "Create a workflow that monitors my GitHub repository for new issues, sends a Slack notification to the team channel, and creates a Trello card for tracking."

Claude, connected to your n8n instance via this MCP server, can build the workflow for you automatically.


Features

  • Full Workflow Management
  • List, create, update, and delete workflows
  • Activate and deactivate workflows on demand
  • Get detailed workflow configurations

  • Execution Monitoring

  • View workflow execution history
  • Get detailed execution logs and results
  • Delete old executions

  • Resource Management

  • List and manage credentials
  • Organize workflows with tags

  • Flexible Deployment

  • Docker support for containerized environments
  • Local development setup
  • Portainer-ready for home lab deployments

  • Secure Integration

  • API key authentication
  • Environment-based configuration
  • No hardcoded credentials

Prerequisites

Before you begin, ensure you have:

  • Node.js 20 or higher (for local development)
  • Docker and Docker Compose (for containerized deployment)
  • A running n8n instance (self-hosted or cloud)
  • n8n API key (instructions below)
  • Claude Desktop or Claude Code (CLI)

Getting Your n8n API Key

  1. Log in to your n8n instance
  2. Navigate to Settings → n8n API
  3. Click Create an API Key
  4. Copy the generated API key (you'll need this for configuration)
  5. Store it securely (treat it like a password)

Quick Start

Get up and running in 3 minutes:```bash

Clone the repository

git clone https://github.com/nourdeo/mcp-n8n-server.git
cd mcp-n8n-server

Install dependencies

npm install

Create configuration

cp .env.example .env

Edit .env with your n8n details

Build the project

npm run build

Start the server

npm start


Then configure Claude (see Configuration section).

---

## Installation Methods

### Method 1: Docker (Recommended)

Best for production deployments, home labs, and containerized environments.

#### Step 1: Clone the repository```bash
git clone https://github.com/nourdeo/mcp-n8n-server.git
cd mcp-n8n-server

Step 2: Configure environment variables```bash

cp .env.example .env


Edit `.env` with your n8n details:```env
N8N_BASE_URL=https://your-n8n-instance.com
N8N_API_KEY=your-api-key-here

Step 3: Build and run with Docker Compose```bash

docker-compose up -d


#### Step 4: Verify it's running```bash
docker ps | grep mcp-n8n-server
docker logs mcp-n8n-server

Method 2: Local Development

Best for development, testing, and customization.

Step 1: Install dependencies```bash

npm install


#### Step 2: Configure environment```bash
cp .env.example .env
# Edit .env with your credentials

Step 3: Build the project```bash

npm run build


#### Step 4: Run the server```bash
npm start

For development with auto-reload:```bash
npm run watch


---

### Method 3: Portainer Deployment

Perfect for home lab environments using Portainer.

#### Step 1: Create a new stack

1. Open Portainer
2. Go to **Stacks** → **Add stack**
3. Name it `mcp-n8n-server`

#### Step 2: Upload docker-compose.yml

Either upload the `docker-compose.yml` file or paste its contents:```yaml
version: '3.8'

services:
  mcp-n8n-server:
    build: .
    container_name: mcp-n8n-server
    environment:
      - N8N_BASE_URL=${N8N_BASE_URL}
      - N8N_API_KEY=${N8N_API_KEY}
    restart: unless-stopped
    stdin_open: true
    tty: true

Step 3: Add environment variables

In Portainer's environment variables section, add:

  • N8N_BASE_URL: https://your-n8n-instance.com
  • N8N_API_KEY: your-api-key-here

Step 4: Deploy

Click Deploy the stack and wait for it to start.


Configuration

Connecting to Claude Desktop

Claude Desktop uses a configuration file to connect to MCP servers.

Configuration file location:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

For Local Installation:```json

{
"mcpServers": {
"n8n": {
"command": "node",
"args": ["/absolute/path/to/mcp-n8n-server/build/index.js"],
"env": {
"N8N_BASE_URL": "https://your-n8n-instance.com",
"N8N_API_KEY": "your-api-key-here"
}
}
}
}


Replace `/absolute/path/to/` with the actual path to your installation.

#### For Docker Installation:```json
{
  "mcpServers": {
    "n8n": {
      "command": "docker",
      "args": [
        "exec",
        "-i",
        "mcp-n8n-server",
        "node",
        "build/index.js"
      ],
      "env": {
        "N8N_BASE_URL": "https://your-n8n-instance.com",
        "N8N_API_KEY": "your-api-key-here"
      }
    }
  }
}

After editing the config, restart Claude Desktop.


Connecting to Claude Code (CLI)

Claude Code (the CLI version) has a separate configuration file.

Configuration file location:

  • macOS/Linux: ~/.config/claude/config.json
  • Windows: %USERPROFILE%\.config\claude\config.json

Create or edit this file:```json
{
"mcpServers": {
"n8n": {
"command": "node",
"args": ["/absolute/path/to/mcp-n8n-server/build/index.js"],
"env": {
"N8N_BASE_URL": "https://your-n8n-instance.com",
"N8N_API_KEY": "your-api-key-here"
}
}
}
}


**After editing the config, restart Claude Code.**

---

## Available Tools

The MCP server exposes the following tools to Claude:

### Workflow Management

| Tool | Description |
|------|-------------|
| `list_workflows` | List all workflows with their status |
| `get_workflow` | Get detailed information about a specific workflow |
| `create_workflow` | Create a new workflow from scratch |
| `update_workflow` | Update an existing workflow's configuration |
| `delete_workflow` | Permanently delete a workflow |
| `activate_workflow` | Activate a workflow to make it run |
| `deactivate_workflow` | Deactivate a workflow to stop it |

### Execution Management

| Tool | Description |
|------|-------------|
| `list_executions` | List workflow execution history |
| `get_execution` | Get detailed execution logs and results |
| `delete_execution` | Delete a specific execution record |

### Resource Management

| Tool | Description |
|------|-------------|
| `list_credentials` | List all configured credentials |
| `list_tags` | List all available tags |

---

## Usage Examples

Once connected to Claude, you can use natural language to interact with your n8n instance:

### Basic Queries```
"List all my n8n workflows"
"Show me the details of workflow ID 123"
"What are the recent executions for my email workflow?"

Workflow Management```

"Create a new workflow called 'Daily Backup Notification'"
"Activate the workflow with ID 456"
"Deactivate all workflows tagged with 'testing'"


### Advanced Workflow Creation```
"Help me build a workflow that:
1. Monitors my GitHub repository for new issues
2. Sends a Slack notification to #dev-team
3. Creates a Trello card in the 'To Do' list"
``````
"Create a workflow that checks my website every 5 minutes
and sends me an email if it's down"

Debugging and Monitoring```

"Show me all failed executions from the past week"
"Why did workflow 789 fail? Show me the execution details"
"List all workflows that haven't been executed in the past month"


---

## Project Structure```
mcp-n8n-server/
├── src/
│   ├── index.ts              # Main MCP server implementation
│   └── n8n-client.ts         # n8n API client wrapper
├── build/                    # Compiled JavaScript (generated)
│   ├── index.js
│   └── n8n-client.js
├── node_modules/             # Dependencies (generated)
├── .env                      # Your environment variables (not in git)
├── .env.example              # Example environment variables template
├── .gitignore                # Git ignore rules
├── .dockerignore             # Docker ignore rules
├── package.json              # Node.js dependencies and scripts
├── package-lock.json         # Locked dependency versions
├── tsconfig.json             # TypeScript compiler configuration
├── Dockerfile                # Docker image definition
├── docker-compose.yml        # Docker Compose orchestration
└── README.md                 # This file

Development

Available Scripts```bash

Build the project

npm run build

Watch mode (auto-recompile on changes)

npm run watch

Start the server

npm start

Development mode (build + start)

npm run dev


### Making Changes

1. Edit TypeScript files in `src/`
2. Run `npm run build` to compile
3. Test with `npm start`
4. For active development, use `npm run watch` in one terminal and `npm start` in another

### Adding New Tools

To add a new MCP tool:

1. Add the API method to `src/n8n-client.ts`
2. Register the tool in `src/index.ts`
3. Define the tool's schema and handler
4. Rebuild and test

---

## Troubleshooting

### Connection Issues

#### Verify n8n is accessible:```bash
curl https://your-n8n-instance.com/api/v1/workflows \
  -H "X-N8N-API-KEY: your-api-key"

Expected: JSON response with workflows list

Check Docker logs:```bash

docker logs mcp-n8n-server


Look for connection errors or authentication issues.

#### Verify environment variables:```bash
docker exec mcp-n8n-server env | grep N8N

Ensure both N8N_BASE_URL and N8N_API_KEY are set correctly.


Authentication Errors

Symptoms: 401 Unauthorized or 403 Forbidden

Solutions:
- Ensure your API key is valid and hasn't expired
- Verify the API key has the necessary permissions
- Check that you're using the correct API key format
- Confirm the base URL is correct (no trailing slash)


Claude Not Seeing the Server

Symptoms: MCP server not listed in Claude, tools unavailable

Solutions:
- Restart Claude Desktop/Code after updating config
- Verify the config file path is correct
- Check JSON syntax in config file (use a JSON validator)
- Ensure the server process is running:
- Docker: docker ps | grep mcp-n8n-server
- Local: Check if the process is active
- Review Claude's MCP logs for error messages


Build Errors

Symptoms: TypeScript compilation fails

Solutions:
- Ensure Node.js 20+ is installed: node --version
- Delete node_modules and reinstall: rm -rf node_modules && npm install
- Clear build directory: rm -rf build && npm run build


Security Best Practices

  1. Never commit .env files
    - Already in .gitignore, but always double-check
    - Use .env.example as a template

  2. Use HTTPS for n8n
    - Always use https:// in N8N_BASE_URL
    - Don't expose n8n over plain HTTP

  3. Secure your API keys
    - Treat API keys like passwords
    - Rotate keys regularly
    - Use separate keys for different environments

  4. Network restrictions
    - Use firewall rules to limit access to n8n API
    - Consider VPN or private networks for home labs
    - Use Docker networks for container isolation

  5. Regular updates
    - Keep dependencies up to date: npm update
    - Monitor for security advisories
    - Rebuild Docker images periodically

  6. Access control
    - Limit who can access the MCP server
    - Use read-only API keys when possible
    - Audit workflow changes regularly


Contributing

Contributions are welcome! Here's how you can help:

  1. Report bugs: Open an issue with details and reproduction steps
  2. Suggest features: Open an issue with your idea and use case
  3. Submit pull requests: Fork the repo, make changes, and submit a PR
  4. Improve documentation: Help make this README even better

Development Setup```bash

Fork and clone the repository

git clone https://github.com/nourdeo/mcp-n8n-server.git
cd mcp-n8n-server

Install dependencies

npm install

Create a feature branch

git checkout -b feature/your-feature-name

Make your changes and test

npm run build
npm start

Commit and push

git add .
git commit -m "Add your feature description"
git push origin feature/your-feature-name
```


License

MIT License - see LICENSE file for details.


Resources

Official Documentation

  • n8n Documentation - Learn about n8n workflow automation
  • n8n API Reference - Complete n8n API documentation
  • Model Context Protocol - Learn about MCP architecture
  • Claude Desktop - Download Claude Desktop app
  • Claude Code Documentation - Claude CLI documentation

Community and Support

  • n8n Community Forum - Get help from the n8n community
  • MCP GitHub - MCP specification and examples
  • Anthropic Discord - Join the Anthropic community

Related Projects

  • n8n - The n8n workflow automation tool
  • MCP Servers - Collection of MCP server implementations

Built with Claude Code - An AI-assisted development project demonstrating the power of human-AI collaboration.


Questions?

If you have questions or need help:

  1. Check the Troubleshooting section
  2. Search existing issues
  3. Open a new issue with details

Happy automating!

常见问题

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

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

MCP N8n Server 60fdc55d 怎么在 Claude Desktop、Claude 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

MCP N8n Server 60fdc55d 收费吗?

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

MCP N8n Server 60fdc55d 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

MCP N8n Server 60fdc55d 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

MCP N8n Server 60fdc55d 能提供哪些能力?

资料显示约 12 个工具;能力标签包括 工作流自动化、开发工具、JavaScript、Claude、自动化管理。具体工具清单以官方文档为准。

热门专题

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

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