Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Path-scoped project memories, rules and skills for coding agents, on your machine or Pathrule Cloud.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://cloud.pathrule.io/mcp打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"pathrule": {
"command": "npx",
"args": [
"-y",
"@pathrule/mcp"
]
}
}
}在终端中运行这条命令
claude mcp add --transport http pathrule https://cloud.pathrule.io/mcpclaude mcp add pathrule -- npx -y @pathrule/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"pathrule": {
"url": "https://cloud.pathrule.io/mcp"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"pathrule": {
"command": "npx",
"args": [
"-y",
"@pathrule/mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"pathrule": {
"type": "http",
"url": "https://cloud.pathrule.io/mcp"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"pathrule": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pathrule/mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://cloud.pathrule.io/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 pathrule.io 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.0.6)于18天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, LickityClick
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
English · Español · Français · Deutsch · 日本語 · Italiano · Türkçe · Português (Brasil)
Your AI forgets. Pathrule remembers.
The open-source knowledge layer for coding agents. Pathrule keeps what your project has learned as memories, rules and skills scoped to paths in your code, and gives Claude Code, Codex, Cursor, GitHub Copilot and Windsurf only what the task in front of them needs, before they act.
PathruleBench, 2,000 items: 55% lower cost a chain · 2.7× fewer input tokens · 97% of memory probes passed · the numbers
Website · Docs · Quickstart · Benchmarks · Smarter over time · Changelog
Same request, same agent. On the right, Pathrule's hook hands over the three notes filed for apps/web/dashboard before the agent writes a line.
Works with Claude Code · Codex · Cursor · GitHub Copilot · Windsurf · any MCP client
Node.js 22.14.0 or newer, on macOS, Linux or Windows.
npm i -g @pathrule/cli
pathrule setup --local # no account: knowledge stays on this machine pathrule doctor # see what each agent receives
Restart your agent. From the next session on, it gets the notes for the path it is about to touch, and writes new ones as it works.
| Other ways in | Command | Good for |
|---|---|---|
| VS Code extension | code --install-extension Pathrule.pathrule-vscode | Knowledge beside the code. Marketplace and Open VSX. |
| Claude Code / Codex plugin | /plugin marketplace add pathrule/pathrule · codex plugin marketplace add pathrule/pathrule | Installing from inside the agent. Setup shows a plan before it changes anything. |
| Cursor plugin | Cursor Marketplace → Pathrule | The same hooks, MCP and skills inside Cursor. |
| Gemini CLI / OpenCode plugin | gemini extensions install https://github.com/pathrule/gemini-cli-extension · opencode plugin @pathrule/opencode --global | The same setup in Gemini CLI and OpenCode. |
| Any MCP client | npx -y @pathrule/mcp | Agents without a plugin system. Listed in the official MCP Registry. |
| Local Console | pathrule ui | Browse and edit knowledge on 127.0.0.1. No account. |
| Remote MCP | claude mcp add --transport http pathrule https://cloud.pathrule.io/mcp | Trying it with nothing installed. No hooks, no local mode. |
| From source | pnpm install && pnpm cli:bundle | Hacking on Pathrule. See docs/quickstart.md. |
Coding agents start every session blank. So the same correction comes back, day after day, agent after agent:
| Day | Agent | What you typed | |
|---|---|---|---|
| Mon | Claude Code | “use our api client, not fetch” | 1st |
| Tue | Claude Code | “again: api client, not fetch” | 2nd |
| Wed | Codex | “we use the api client.” | 3rd |
| Thu | Cursor | “I told you yesterday. api client.” | 4th |
| Fri | Claude Code | “API CLIENT. NOT FETCH.” | 5th |
Five sessions, three agents, nothing remembered. With Pathrule you say it once:
features/, not a line in a file every session has to read.A workspace collects hundreds of notes. An agent editing features/orders needs four of them.
Knowledge is matched by path, scope and relevance, then fit to a per-prompt budget. Enforced rules are never cut for space. Whatever does not fit is listed by title, so the agent can ask for it. When a prompt names a function or a type, the hook also points the agent to the file and line where it is defined (JS/TS, Python, Go).
| Kind | What it holds | Example on features/ |
|---|---|---|
| Memory | Decisions, gotchas and incidents, in short markdown. | “Use the api client. It handles auth and retries.” |
| Rule | Constraints the agent must follow, ranked above advice. | “Data loading goes through React Query.” |
| Skill | Reusable procedures and checklists an agent can run. | “Run the checks before calling it done.” |
| Channel | When it reaches the agent | Cost |
|---|---|---|
| Path-scoped rule files | Claude Code reads Pathrule's own .claude/rules/pathrule/ at session start, each file scoped to its paths. Your CLAUDE.md and AGENTS.md are left as they are. | Cached by the client. |
| Hooks | Before the agent acts: on session start, on each prompt and on file tools. Only new or changed context is sent again. | Budgeted per prompt. |
MCP get_context | When the agent asks, at the depth the request needs. | Every MCP client has it. |
A CLAUDE.md file is read whole on every step, so every note your team adds makes every session cost more. Pathrule sends each prompt only what the path and the task need. PathruleBench measured the difference with the same agent, the same prompts and the same hidden checks, from 500 to 2,000 items of team knowledge.
| At 2,000 items of team knowledge | CLAUDE.md | Pathrule |
|---|---|---|
| Cost a chain of 8 sessions | $3.89–$4.21 | $1.76–$1.89 |
| Input tokens a chain | 11.8–12.5 M | 4.3–4.7 M |
| Memory probes passed | 89% | 97% |
| Chains that passed every memory probe | 0 of 9 | 5 of 9 |
| A habit said once, followed later | 78% | 97% |
| What a failing command taught, kept | 33% | 78% |
| The work each prompt asked for | 100% | 100% |
From 500 to 2,000 items, a chain with CLAUDE.md costs 89–98% more. With Pathrule it moves between −1% and +10%. Your knowledge base can grow; the bill does not.
Claude Code with claude-sonnet-5-5 in Python, Go and TypeScript; nine chains an arm at 2,000 items (three per language); executable tests decide every pass, no model judges. The Pathrule arm is this repository's open-source CLI in local mode: no Cloud, no model.
[Every condition, chain and check, and how to run it yourself → pathrule/benchmark](https://github.com/pathrule/benchmark)
Day one needs no account, no network and no model. Everything after builds on what you and your agents already did in this repository.
| When | What Pathrule does | Where it runs |
|---|
| Day 0 Foundation | Hooks and the local MCP server are wired into your agents. What you write is delivered per path, within a budget, through the hooks and Claude Code's path-scoped rules; your own CLAUDE.md and AGENTS.md are left as they are. | Open source, this machine | | Week 1 Memory | A decision you state in a prompt (“from now on…”, “we decided…”) is saved in your own words. A lesson a failing command taught is saved once. Each note is filed next to the code it is about, and only new or changed context is sent again. | Open source, this machine | | Month 1 Your habits | A preference you state lives in a local file of your own. Said once in passing, it waits; said again in another session, it reaches every agent. One you call lasting is in force at once. A project rule always wins over a personal one. | Open source, this machine | | Month 3 At scale | Thousands of notes, and a session stays the same size: the root rules file stays around 6k characters and the rest arrives per prompt. A sentence that says where code lives is marked (as of writing), so when a teammate moves the file the agent follows the code. When an edit writes a value a newer decision replaced, the hook quotes the decision at that edit. | Open source, this machine | | When you choose Team | The same knowledge on every machine and for every member. For a Cloud workspace, a model also reads the prompts Pathrule's phrase rules found nothing in and keeps the sentence you meant to last, still in your words. It is paid from AI Credits. | Pathrule Cloud, opt-in |
No model runs on your machine. Everything before Team is the open-source CLI, the same path the benchmark above measured.
<source media="(prefers-color-scheme: dark)" srcset="docs/assets/readme/en/
只显示了开头部分;其余内容请在仓库中阅读