
n8n Pro MCP
io.github.helbertparanhos由 GitHub 帳號 helbertparanhos 發布v1.0.0更新於 Oct 24, 2026
Manage self-hosted n8n (incl. queue mode): workflows, executions, users, audit — 51 tools.
概覽
管理自架 n8n 執行個體(含佇列模式),讓助理處理工作流程、執行紀錄、標籤、使用者與健康檢查。
- 可以做什麼
- 列出、搜尋、建立、更新、複製、刪除、啟用與轉移工作流程,寫入前進行離線 JSON 驗證,並可依標籤批次啟用或停用(支援試運行)。檢視、重試、刪除與批次清理執行紀錄,檢視執行中與排隊中的執行,觸發 webhook,等待執行結束,彙總錯誤並取得各工作流程的成功率與耗時統計。依名稱管理標籤、唯寫憑證、變數以及含成員角色的專案。列出、邀請、刪除使用者並變更角色。檢查執行個體健康狀態、執行內建安全稽核並從已連線的原始碼控管拉取。
- 適用情境
- 適合自架 n8n 執行個體(尤其是搭配 worker 的佇列模式)的使用者,希望由助理來建立與驗證工作流程、排查失敗執行、清理舊紀錄或檢查執行個體健康狀態,而不必手寫 API 呼叫。
- 執行需求
- 透過 npm 或 npx 在本機執行,需要 Node.js 18 或更新版本。需要可連線且已啟用公開 API 的 n8n 執行個體,並設定 N8N_API_URL 與 N8N_API_KEY 環境變數;N8N_WEBHOOK_BASE_URL 為選用,用於專用 webhook 處理器。變數、專案與原始碼控管功能需要 n8n 對應的授權版本。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 n8n Pro MCP,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
n8n Pro MCP ⚙️
Full-instance management for self-hosted n8n — including queue mode — through the Model Context Protocol. 51 tools covering workflows, executions, tags, credentials, variables, projects, users, security audit, source control and health monitoring.
[npm version] [License: MIT] [GitHub Stars] [GitHub Forks] [GitHub Issues] [Glama Quality]
[TypeScript] [Node.js] [MCP] [Claude Code] [Cursor] [Claude Desktop]
[Instagram] [YouTube] [LinkedIn] [Buy Me A Coffee] [Strat Academy]
n8n-pro-mcp connects Claude Code, Claude Desktop, Cursor or any MCP client to your n8n instance via the official n8n public API v1, with automatic cursor pagination, exponential-backoff retry on reads (writes and webhook calls are never retried, so side effects can't duplicate), and offline workflow validation that catches the classic n8n mistakes (malformed {{ }} expressions, webhook data accessed without .body, Code nodes missing return [{json: {...}}]) before they reach your instance.
Why this one?
- Queue mode first-class —
list_running_executions(live queue view),get_execution_stats(success rate + average duration per workflow) andcheck_health(healthz, readiness, API auth) were built for instances runningEXECUTIONS_MODE=queuewith workers and webhook processors.N8N_WEBHOOK_BASE_URLlets webhook calls target dedicated webhook processors. - Complete API v1 coverage — tags, variables, projects, users, source control and cross-project transfers, beyond the usual workflow/execution CRUD.
- Offline validation built in —
validate_workflow_jsonchecks structure, connection integrity, orphan nodes, expression syntax, webhook.bodyaccess, Code node return format and hardcoded secrets without any API call.create_workflow/update_workflowrun it automatically and refuse invalid payloads. - Safe partial updates —
update_workflowfetches the current workflow, merges only what you pass and strips read-only fields, so you never lose nodes by sending an incomplete PUT. - Tags by name —
set_workflow_tagsaccepts tag names and creates missing ones; no manual ID juggling. - Ops compositions the raw API doesn't have —
summarize_execution_error(just the failing node + error, not a giant JSON dump),prune_executions(bulk cleanup with dry run),wait_for_execution(poll until terminal),clone_workflowandset_workflows_active_by_tag(tag-based kill switch).
Installation
From source:
When running from source, you can copy .env.example to .env in the project root — the server loads it from the package root, not the working directory. When installed via npx, set the variables through your MCP client config instead (the .env file is not read from the npx cache).
Configuration
Claude Code
Or in .claude/settings.json / .mcp.json:
Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Cursor
Same JSON block in Cursor's MCP settings (.cursor/mcp.json).
Tools (51)
Workflows (12)
Executions (10)
Tags (6)
list_tags, create_tag, update_tag, delete_tag, get_workflow_tags, set_workflow_tags (by name, auto-creates missing tags).
Credentials (4)
create_credential, delete_credential, get_credential_schema, transfer_credential. Secrets are write-only — the n8n API never returns credential data.
Variables (4)
list_variables, create_variable, update_variable, delete_variable (licensed feature).
Projects (7)
list_projects, create_project, update_project, delete_project, plus member management: add_user_to_project, remove_user_from_project, change_user_project_role (licensed feature).
Users (5)
list_users, get_user, create_user (invite), delete_user, change_user_role.
System (3)
Queue mode playbook
With EXECUTIONS_MODE=queue (main + workers + Redis):
check_health— confirms the main process and DB are up.list_running_executions— what is actually in flight right now; a growing list with oldstartedAtvalues means workers are starved or stuck.get_execution_stats— which workflows fail or crawl; sorted worst-first by success rate.run_webhookwithN8N_WEBHOOK_BASE_URLpointing at your webhook processors to test the production ingestion path end to end.
Development
CI (GitHub Actions) runs build, tests and npm audit on every push and PR.
Requirements
- Node.js ≥ 18
- n8n instance with the public API enabled (
N8N_PUBLIC_API_DISABLEDnot set) and an API key - Variables, projects and source-control tools require the corresponding licensed n8n features
👤 Author
Created by Helbert Paranhos at Strat Academy.
[Instagram] [YouTube] [LinkedIn] [Buy Me A Coffee]
If this project helped you, consider starring ⭐ the repository and following Strat Academy for more AI automation tooling.
📄 License
MIT © Helbert Paranhos / Strat Academy — see LICENSE.
來源:README.md,提交 9a9e156
工具
0版本歷史
1- v1.0.0最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分