n8n-development-framework

MCP安全风控

提供方 MrMinor-dev

安全风控 stdio · 本地进程 未标注 社区 / 第三方 ClaudeZed

A development framework for building, auditing, and managing n8n workflows, covering automation scenarios across knowledge, comms, intel, and infra, with a 65-point audit to ensure workflow quality.

一句话选型结论

按资料字段整理

n8n-development-framework 属于安全风控类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,可直接接入 Claude、Zed,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

Local Deployment n8n workflow development workflow audit automation ops AI-assisted development error handling workflow governance

支持客户端

适用场景

Local Deploymentn8nworkflow development

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
  1. 1
    准备运行环境

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

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
资产与漏洞排查

盘点资产、扫漏洞、看暴露面。

日志与审计

汇总日志、查异常行为。

合规检查

按规则检查配置与权限是否合规。

选择建议

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

值得选的地方

  • 已适配 Claude、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
n8n-development-framework当前 未标注 stdio · 本地进程 本地部署 无 2026-09-30
Cyber Strike AI 75 未标注 未标注 无 2026-05-17
mcp-for-beginners 未标注 stdio · 本地进程 本地部署 有 2026-04-13
casdoor 未标注 stdio · 本地进程 本地部署 有 2026-04-12
kubeshark 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Modelcontextprotocol C22988b0 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

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

详细介绍

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

n8n Development Framework

24 n8n workflows from a running system, and the 65-point audit each one passes before it goes live.

Building n8n workflows by hand stops scaling somewhere around 5. You remember the node patterns. At 40, you are guessing at property names, copying from broken examples, and finding failure modes in production.

Governance is the second problem. Workflows that start clean drift. Credentials get hardcoded. Error handling gets skipped. A workflow that ran fine last month can start failing because a full API update stripped its credentials. No error and no alert. You find out through downstream failures.

So I brought Claude into the build from the start, and I wrote the audit before I scaled the workflow count. I have built more than 40 workflows. 26 are active. 36 are published across these repos, and 24 of them are here.

The other 10 live with their domain: 2 in security-governance-framework, 2 in database-security-framework, 1 in rag-knowledge-base, and 5 in back-office-automation. The catalog lists all 33.

What's here

Knowledge

Workflow What it does Trigger Level Nodes
AOS - Intel Asset-Wikifier Extracts signals from a business asset with Claude, routes them to wiki pages, and writes or updates those pages. webhook L2 37
HAIOS-Intel-Wiki-Explore Picks recent analyses and sends each one to the wikifier. schedule, webhook - 12
HAIOS-Intel-Wiki-Lint Checks wiki pages with Claude and records new issues. schedule, webhook - 22
HAIOS-Intel-Wiki-Lint-Triage Classifies open wiki issues with Claude Haiku, dismisses false positives, and writes fix instructions for the rest. schedule, webhook - 25
HAIOS-Intel-Wiki-Query Answers a question from the wiki pages with Claude. webhook - 15

Comms

Workflow What it does Trigger Level Nodes
HAIOS - Comms - Daily Digest Compiles overnight messages, expenses, health checks, intel, pending remediations and wiki issues into one Slack digest. schedule L2 29
HAIOS - Comms - Slack Inbound (Control Plane) Receives Slack commands (kill, resume, status, help), ignores the bot's own messages, and routes each command. Slack L2 27
HAIOS - Comms - Slack Outbound Shared send service. Any workflow calls it to post a Slack message. webhook L2 9
HAIOS - Comms - Weekly Report Monday summary of landscape intelligence and win/loss. schedule L2 12
Utility - Gmail Query Lists Gmail labels on demand for other workflows. manual/chat L1 7

Intel

Workflow What it does Trigger Level Nodes
AOS - Intel - Email Collector Collects signals from platform and vendor emails each night. schedule L2 15
AOS - Intel - Stack Updates Collector Collects release news from the tools the system runs on, nightly. schedule, feeds L2 23
AOS-Intel-n8n-Metrics-Collector Every 6 hours, aggregates execution metrics from n8n and stores them. schedule, webhook - 16
HAIOS - Intel - 3P Collector Collects third-party signals from social and blog sources into the intel tables. schedule L2 27
HAIOS - Intel - Analyzer Analyzes collected signals with Claude and semantic search, classifies them, and writes the analyses. schedule L2 31
HAIOS - Intel - Disposition Webhook that records what was decided about an analysis. webhook L2 14

Infra

Workflow What it does Trigger Level Nodes
AOS - Infra - Site Restore Rolls a site back to a known-good commit after a confirmed failure. 15-minute cooldown, 5 restores per 24 hours. webhook L2 48
AOS-Infra-Site-Validator Checks a site on a schedule and calls the restore workflow after a confirmed failure. (not in production) schedule, webhook - 22
HAIOS - Infra - CC Config Weekly Digest Weekly Slack digest of open findings about the coding agent's configuration. schedule L2 9
HAIOS - Infra - Doc Governance Weekly check that workflow folders, snapshots and documentation match what is live. Writes remediation rows. schedule L2 20
HAIOS - Infra - Log Retention Monthly archive-then-prune of resolved remediation rows older than 90 days. Copies them to an archive table first, verifies, then deletes from the hot table. schedule L2 7
HAIOS - Infra - Remediation Cleanup Deletes stale remediation prompt files and clears their references. schedule L2 12
HAIOS - Infra - Remediation Trigger Counts errors per workflow, catches silent failures, and drafts a remediation prompt when a threshold is met. webhook, schedule L2 28
HAIOS - Infra - Weekly Audit Sunday audit of workflow liveness, errors, coverage, backlog, naming, database security and registry gaps. schedule L2 20
Other files What it is
sql/health-and-remediation-schema.sql The shared health log, the workflow registry, and the remediation log every workflow writes to.
LICENSE MIT.

Every export is sanitized. Hostnames, credential IDs, webhook paths, Slack IDs and similar are placeholders such as {{N8N_HOST}} and {{CREDENTIAL}}. Execution data has been removed. Workflows tagged "not in production" are exported as they last ran.

The audit itself is a skill and lives in ai-skills-framework, with the full checklist.

How a workflow gets built```

DESIGN Claude, given the real node specs, drafts the workflow.
BUILD The n8n API creates it directly. No JSON import.
Test after each major node.
AUDIT 65 points in 2 phases. Pass mark 48.
DEPLOY Error handling confirmed, README written, indexed for search.


Claude reads real node definitions through the n8n MCP server. Without them, Claude writes JSON that looks right and has wrong property names or missing required fields. With them, it knows what each node needs. That's the gap between "looks right" and "is right."

**The build steps:**
1. Name it with a layer, a domain and a capability, and a maturity tag.
2. Start it at L1. It moves up after testing.
3. Look at similar workflows before drawing a new one.
4. Build through the API. Never fall back to JSON import on the first error.
5. Test after each major node.
6. Audit before deploy.

## The audit

Every workflow gets scored against 65 points in 2 phases. A few defects are blockers whatever the score, such as a Code node in the wrong execution mode.

**Phase 1: JSON analysis, 43 points.** Runs on the workflow file. Nothing has to execute.

| Category | Points | What gets checked |
|---|---|---|
| A: Triggers | 6 | One trigger, right type, valid schedule or path |
| D: Strategy | 3 | Purpose fits the domain and layer |
| G: Metrics | 4 | Logs to the health table, on success and on error |
| I: Tech stack | 3 | Current node versions, credentials referenced and not hardcoded |
| J: Cadence | 5 | Schedule matches the purpose, no conflicts |
| L: Parameters | 5 | No secrets in node parameters |
| M: Error handling | 12 | Error Trigger present, retries, connected error paths, logging |
| N: Remediation maturity | 5 | Logging and error paths match the workflow's maturity level |

**Phase 2: runtime verification, 22 points.** Runs after Phase 1 passes.

| Category | Points | What gets checked |
|---|---|---|
| B: Outputs | 5 | Recent executions, success rate at or above 80% |
| C: Database | 4 | Target tables exist, recent records, no test data |
| E: Testing | 4 | A test run passes without side effects |
| F: Docs | 4 | A README exists and is current |
| K: Indexed | 5 | The README turns up in semantic search |

**Thresholds:** 48 or more passes. 36 to 47 is conditional, fix and re-audit. Under 36 fails.

The audit runs in a fresh Claude context, separate from the one that built the workflow. Builders rate their own work too high, and the skill says never to audit a workflow you just built.

## Error handling on every workflow

All 36 published workflows have an Error Trigger and write to the health table.```
Any workflow error
    -> Error Trigger writes state='error' to the health table
    -> Daily digest surfaces errors each morning
    -> Slack alert only for critical, time-sensitive failures

4 failures that changed how I work

Credential stripping. A full API update silently removed the credentials from every node. No error and no warning. I found it days later through authentication failures downstream. Now there is a mandatory check before any full workflow update, and it is a standing item in the audit.

Two call paths, two payload shapes. The same workflow called from MCP and from a webhook received its input in different places. Failures were intermittent and looked random. Now every utility workflow checks both.

Green run, empty database. An execution showed success and wrote nothing. An upstream node had returned an unexpected shape and passed nothing forward, with no error. Phase 2 category C now catches this by looking for recent records in the target tables, since execution status alone missed it.

Stale search index after a rename. I renamed a workflow folder and the old path stayed in the index. Search returned documents pointing at a location that no longer existed. Renames now trigger an index update.

A related lesson from the tooling side: installing the n8n MCP server through npx broke Claude's connection, because download messages landed in the protocol stream. Installing it globally first fixed it. The write-up is in mcp-server-installation-framework.

Why this matters

Workflow governance is release management and change control under a different name. You apply standards consistently. You don't rely on remembering them. The credential failure and the empty-database failure share a cause: no step asked whether the workflow did what it was supposed to do. Phase 2 is that step.

Built with

n8n, the n8n MCP server, Claude, Supabase (Postgres) for logging and health checks.


Jordan Waxman · LinkedIn · GitHub profile

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
n8n-development-framework 怎么安装?

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

n8n-development-framework 怎么在 Claude、Zed 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

n8n-development-framework 收费吗?

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

n8n-development-framework 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

n8n-development-framework 支持哪些客户端?

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

n8n-development-framework 能提供哪些能力?

资料显示能力标签包括 Local Deployment、n8n、workflow development、workflow audit、automation ops、AI-assisted development。具体工具清单以官方文档为准。

n8n-development-framework 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

n8n-development-framework 是本地还是远程?

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

热门专题

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

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