What it does
Task contract, evidence check and done gate for AI coding agents. Read-only, no sign-in.
- Connects 在云端运行
- Account or key No key needed
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 4/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 24/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 NoBrainer Tech Flow。按照 https://mcp.popnx.com/i/nobrainer-tech-flow.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.nobrainer.tech) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开 Claude 的 Connectors 页面
CustomizeConnectors
点击“Add” → “Custom” → “Web”,填写这 2 项
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Name · 名称NoBrainer Tech FlowRemote MCP server URL · 地址https://mcp.nobrainer.tech/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
在聊天中开启
+ConnectorsNoBrainer Tech Flow
试一试
用 NoBrainer Tech Flow 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 NoBrainer Tech Flow,或回答中出现 NoBrainer Tech Flow 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
在网页版 ChatGPT 打开添加 MCP 的页面
Plugins+Add custom MCP server
填写名称和地址
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Name · 名称NoBrainer Tech FlowConnection · 地址https://mcp.nobrainer.tech/mcp在聊天中选择 NoBrainer Tech Flow
开启新聊天,输入前先从插件列表中选择 NoBrainer Tech Flow
试一试
用 NoBrainer Tech Flow 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 NoBrainer Tech Flow,或回答中出现 NoBrainer Tech Flow 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --transport http --scope user nobrainer-tech-flow https://mcp.nobrainer.tech/mcp在 Claude Code 中输入 /mcp
应能看到 NoBrainer Tech Flow 在列表中并显示已连接
试一试
用 NoBrainer Tech Flow 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 NoBrainer Tech Flow,或回答中出现 NoBrainer Tech Flow 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 NoBrainer Tech Flow 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 NoBrainer Tech Flow,或回答中出现 NoBrainer Tech Flow 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 NoBrainer Tech Flow 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 NoBrainer Tech Flow,或回答中出现 NoBrainer Tech Flow 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.nobrainer.tech/mcpJSON 设置在下方“开发者专用”中
开发者专用:终端命令和 JSON 设置
通过网页连接
Claude Code
claude mcp add --transport http --scope user nobrainer-tech-flow https://mcp.nobrainer.tech/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"nobrainer-tech-flow": {
"url": "https://mcp.nobrainer.tech/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"nobrainer-tech-flow": {
"type": "http",
"url": "https://mcp.nobrainer.tech/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
它能做什么
工具名称和描述与服务器在 2026年11月16日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
start_flow_taskUse at the start of a non-trivial task. Checks your proposed outcome and definition of done (DoD) against Flow's contract rules, chooses the quick or full path, and returns DoD item IDs, a signed contract token and the first step. Computes only; stores nothing. Save the token in
get_flow_stepUse when you need guidance on a Flow stage, an event (e.g. blocked), a module (e.g. nobrainer-review), or a PR's Definition of Done or readiness (topic pr_dod). Returns up to six rules quoted from the pinned release, with their source. With a token, event resume also returns a go
check_flow_evidenceUse after running a check. Validates one to four evidence records against DoD items in the contract token: exit codes, test counts in the output, hashes, URL status and evidence level. It cannot see your machine; it checks structure and consistency only. Returns verdicts and an u
check_flow_doneUse before saying a task is done. Returns DONE only when every DoD item has accepted, current evidence, DONE_WITH_GAPS when the rest are listed in unchecked with a reason, otherwise NOT_DONE with the exact missing items.
draft_flow_handoffUse after check_flow_done. Returns a short final-report skeleton from the done receipt: delivered outcome, proof per DoD item, what was not checked, decisions left to the user and the next action.
recommend_flow_modelUse when picking a model for a Flow task: top-3 from a pinned NoBrainer benchmark snapshot, no invented scores.
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月18日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 nobrainer-tech 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于昨天
- ✓ 通过
有许可证
使用 MIT
- ✓ 通过
端点有响应
在 421 毫秒内响应(HTTP 200)
- – 不适用
使用 OAuth 登录
无需登录
- ✓ 通过
工具描述中没有隐藏指令
已读取 6 个工具描述,未发现针对 AI 的隐藏指令
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/nobrainer-tech-flow)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6083 个服务器的 69%
- 发布到注册中心的时间比此分类中其他 6083 个服务器的 82% 更新
- 基础检查结果等于或优于此分类中其他 6083 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
NoBrainer Tech Flow 安全吗?
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
它还在维护吗?
GitHub 仓库最后更新于昨天,最新版本(2.12.0)于8天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 NoBrainer Tech Flow | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
NoBrainer Tech Flow MCP server
A free, public, stateless remote MCP server for nobrainer-tech-flow. It gives an AI agent one task contract, one evidence check and one done gate, the same in every MCP client, plus guidance quoted from the pinned Flow release and a model advisor based on the NoBrainer AI benchmark.
- Endpoint:
https://mcp.nobrainer.tech/mcp, Streamable HTTP, no sign-in. - Stores nothing, runs no AI model, makes no outbound requests from tools.
- Protocol: MCP
2026-07-28(stateless,server/discover) and 2025-era clients (2025-11-25,2025-06-18, ...) through a stateless JSON-only fallback on the same endpoint.
Tools
| Tool | What it does |
|---|---|
start_flow_task | Checks the outcome and definition of done (DoD), picks the quick or full path, lints vague items, routes Flow modules and owner gates, and returns item IDs (AC01...) with an HMAC-signed contract token to save in your goal file. |
get_flow_step | Up to six rules for one stage, event, module or topic (topic: "pr_dod": a pull request's Definition of Done), quoted verbatim from the pinned Flow release, with the source anchor. Works without a token. With a contract token and event: "resume" it returns two rules plus goal_block for the goal file: GOAL_ID, one DoD row per item (- AC01 test, local: ACCEPTED; statuses OPEN, ACCEPTED, FAILED, STALE), STATUS, CHECKPOINT, NEXT_SAFE_ACTION and the renewed token as FLOW_CONTRACT. OUTCOME, NON_GOALS and the DoD wording stay placeholders because the server never repeats your text. |
check_flow_evidence | Checks one to four evidence records: exit codes, the test-runner summary (pytest, unittest, node:test, Vitest, Jest, Mocha, Playwright, Go, cargo, RSpec, PHPUnit, dotnet), claimed counts, evidence level, URL host and status, file hashes. Marks earlier test results stale when a registered file changes, and returns REPEATED_DEFECT after a second failure. |
check_flow_done | DONE only when every item has accepted, current evidence; DONE_WITH_GAPS when the rest are listed as unchecked with a reason; otherwise NOT_DONE with the exact missing items. |
draft_flow_handoff | A final-report skeleton built only from the done receipt. |
recommend_flow_model | A top-3 model shortlist for a data-backed task type (orchestration, instructions, frontend, research, writing, terminal-coding) from a pinned, dated benchmark snapshot, filtered by the providers, models or client apps you have (have), with an optional priority (quality, balanced, efficient) and role. The legacy coding alias is accepted case-insensitively (for example, Coding) and returns task: "terminal-coding" with a Terminal-Bench shortlist. Never invents scores and says when data is missing. Like the website, it refuses once the snapshot is 14 days past its fetch time (expired: true, expires date in every response). |
All six tools are read-only (readOnlyHint: true, openWorldHint: false). Results are one compact JSON text block. Responses never echo your free text: only IDs, enums, digests and canonical Flow text.
The server checks consistency, not truth: it cannot see your machine, and evidence is reported by the agent. Every handoff says so. A recognised failure in the last 4,000 normalized characters of a test log rejects an exit-zero result, even if a later summary passes. Submit a clean rerun separately.
Install
Server name: nobrainer-tech-flow. To try a local build instead, replace the URL with http://127.0.0.1:8787/mcp (see "Run locally").
| Client | Status |
|---|---|
| Claude Code | Verified 2026-10-20 against the local server (Claude Code 2.1.303): connected over MCP 2026-07-28 and listed the six tools. |
| Codex CLI | Verified 2026-10-20 against the local server (codex-cli 0.163.0): connected over MCP 2025-06-18 and listed the six tools through the app server. |
| OpenCode | Verified 2026-10-23 against the public endpoint (OpenCode 2.0.32): opencode mcp list shows it connected. |
| Claude.ai / Claude Desktop, ChatGPT, Cursor, VS Code / Copilot, Gemini CLI, Cline, Windsurf, Zed | Not verified yet. Snippets follow each client's documentation. |
Claude Code:
claude mcp add --transport http nobrainer-tech-flow https://mcp.nobrainer.tech/mcp
for all projects of this user:
claude mcp add --transport http --scope user nobrainer-tech-flow https://mcp.nobrainer.tech/mcp
Project file .mcp.json:
{"mcpServers": {"nobrainer-tech-flow": {"type": "http", "url": "https://mcp.nobrainer.tech/mcp"}}}
Claude.ai and Claude Desktop (not verified): Customize > Connectors > Add > Add custom connector, name NoBrainer Tech Flow, URL https://mcp.nobrainer.tech/mcp, No sign-in. On Team and Enterprise an Owner adds it under Organization settings > Connectors first.
Codex CLI and IDE, ~/.codex/config.toml (or codex mcp add nobrainer-tech-flow --url https://mcp.nobrainer.tech/mcp):
[mcp_servers.nobrainer-tech-flow]
url = "https://mcp.nobrainer.tech/mcp"
ChatGPT (not verified): open ChatGPT Plugins (chatgpt.com/plugins), select + > Add custom MCP server, name it NoBrainer Tech Flow, enter the URL under Connection, choose no authentication and select Create as a plugin. Workspace policies decide who can add custom MCP servers.
Cursor, .cursor/mcp.json or ~/.cursor/mcp.json (not verified):
{"mcpServers": {"nobrainer-tech-flow": {"url": "https://mcp.nobrainer.tech/mcp"}}}
VS Code / GitHub Copilot, .vscode/mcp.json (not verified):
{"servers": {"nobrainer-tech-flow": {"type": "http", "url": "https://mcp.nobrainer.tech/mcp"}}}
Gemini CLI (not verified):
gemini mcp add --transport http nobrainer-tech-flow https://mcp.nobrainer.tech/mcp
or settings.json: {"mcpServers": {"nobrainer-tech-flow": {"httpUrl": "https://mcp.nobrainer.tech/mcp"}}}
Cline, cline_mcp_settings.json (not verified; set type, because a missing type means legacy SSE):
{"mcpServers": {"nobrainer-tech-flow": {"type": "streamableHttp", "url": "https://mcp.nobrainer.tech/mcp"}}}
OpenCode (verified 2026-10-23 against the public endpoint, OpenCode 2.0.32: opencode mcp list shows it connected):
opencode mcp add nobrainer-tech-flow --url https://mcp.nobrainer.tech/mcp --global
Windsurf, ~/.codeium/windsurf/mcp_config.json, then Refresh in Manage MCPs (not verified):
{"mcpServers": {"nobrainer-tech-flow": {"serverUrl": "https://mcp.nobrainer.tech/mcp"}}}
Zed, Settings > AI > MCP Servers > Add Remote Server, or settings.json (not verified):
{"context_servers": {"nobrainer-tech-flow": {"url": "https://mcp.nobrainer.tech/mcp"}}}
Using it with local Flow skills
The server leads the gates; guidance already in context leads the guidance. If Flow skills are installed locally, keep using them for stage guidance and call get_flow_step only for cards you have not loaded. Pass your local Flow version as local_flow; when it is older than the server's, the response says that gate rules follow the server's version.
In repository work, save the contract token in the Flow goal file as FLOW_CONTRACT: nbf1... so another session or client can continue. To resume, call get_flow_step with that token and event: "resume". Merge the returned goal_block into the goal file by item ID: update each DoD row's status, CHECKPOINT, NEXT_SAFE_ACTION and FLOW_CONTRACT (the renewed token), and keep your own OUTCOME, NON_GOALS, DoD wording, evidence pointers and other fields. Without a goal file yet, start one from the block and fill in those placeholders. Then continue from NEXT_SAFE_ACTION. Each check_flow_evidence call or resume renews a token for 30 days, up to 90 days after start_flow_task.
Run locally
Node.js 22.18 or newer (TypeScript runs directly through Node's type stripping).
cd mcp
npm ci npm run serve # http://127.0.0.1:8787/mcp, loopback only, ephemeral signing key npm test # type check, content pin, unit, protocol, security and budget tests npm run conformance # official MCP conformance suite (2025-11-25) with test/conformance-baseline.yml npm run smoke -- http://127.0.0.1:8787/mcp npm run transcripts # rewrites docs/review/test-cases.md npm run transcripts -- --in-memory # SDK tool calls without an HTTP listener; transport is recorded npm run plugin # dist/nobrainer-tech-flow- .zip for the OpenAI portal
Without FLOW_TOKEN_KEYS, the local server signs with a random key per start, so tokens do not survive a restart. On Vercel the key is required.
How it is built
api/mcp.js Vercel Function; logic compiled from src/ into dist/ by `npm run build`
src/rpcguard.ts fixed-text answers for unknown tool/prompt/resource names, protocol error rewriting src/http.ts POST only (plus CORS preflight for allow-listed origins), 32 KiB body cap, Host and Origin checks, JSON depth limit, one content-free log line; 2026-07-28 traffic -> SDK handler (JSON responses), 2025-era traffic -> fresh stateless transport with JSON responses src/server.ts six tools, prompt flow, resource template flow://card/{id}, instructions src/token.ts 176-byte max binary token, HMAC-SHA-256 (128-bit tag), key ring, expiry src/evidence/ runner parsers, verdicts, staleness, failure budget, secret screening src/rules/ levels, quick/full path, lint, module routing, owner gates src/advisor/ model advisor over data/benchmark/snapshot.json content/ SOURCE.json pin (tag, commit, file hashes) and cards.yaml src/generated/ cards.json built by scripts/build-content.ts from the git tag plugin/ OpenAI submission manifests (plugin.json, mcp.json)
Runtime dependencies: @modelcontextprotocol/server 2.3.1, zod 4.6.7, @vercel/firewall 1.2.6. The spec proposed mcp-handler; it is a thin wrapper over the SDK's own createMcpHandler, so the server uses the SDK directly (one dependency fewer, same dual-era behaviour).
Updating Flow guidance
The module list comes from the release: scripts/build-content.ts enumerates skills/*/SKILL.md at the pinned tag. A released module without a cards.yaml entry gets a description-only card and a warning; a cards.yaml module entry that the release no longer has fails the build (this is how a rename such as nobrainer-codex-context -> nobrainer-context surfaces). To move to a new release: update content/SOURCE.json (tag, commit, hashes), fix cards.yaml, run npm run build:content and npm test, then deploy.
Updating the benchmark snapshot
npm run refresh:benchmark -- --source /public_html/ai/benchmark regenerates data/benchmark/snapshot.json and SOURCE.json deterministically. The website rule applies: a snapshot expires 14 days after its fetch time, so refresh and redeploy at least every 14 days or the advisor answers expired: true with an empty shortlist. See data/benchmark/NOTICE.md for provenance and third-party licences.
Documents
- Deployment: build, checks, environment variables, rate limits, spend guard.
- Security: threat model and controls.
- Privacy policy and terms, published at
https://nobrainer.tech/flow/privacy/andhttps://nobrainer.tech/flow/terms/. - Review test cases and demo recording script.
Source code: MIT, see the repository LICENSE.