Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Path-scoped project memories, rules and skills for coding agents, on your machine or Pathrule Cloud.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://cloud.pathrule.io/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"pathrule": {
"command": "npx",
"args": [
"-y",
"@pathrule/mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http pathrule https://cloud.pathrule.io/mcpclaude mcp add pathrule -- npx -y @pathrule/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pathrule": {
"url": "https://cloud.pathrule.io/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pathrule": {
"command": "npx",
"args": [
"-y",
"@pathrule/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"pathrule": {
"type": "http",
"url": "https://cloud.pathrule.io/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"pathrule": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pathrule/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://cloud.pathrule.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain pathrule.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.0.6) reached the registry 18 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Recta
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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/
Only the beginning is shown; read the rest in the repo