Pathrule

io.pathrulePublished by pathrule.ioOfficial publisherv1.0.6Updated Oct 26, 2026

Path-scoped project memories, rules and skills for coding agents, on your machine or Pathrule Cloud.

The publisher's own server: Pathrule

VerifiedStreamable HTTPWeb executableKnowledge & Memory Developer Tools

Server details

Identifier: io.pathrule/pathrule
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 19, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to pathrule.io, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.pathrule%2Fpathrule.svg)](https://sourceweft.com/mcp/io.pathrule%2Fpathrule?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Pathrule stores path-scoped memories, rules and skills for coding agents and serves each agent only the notes relevant to the code it is about to touch.

What you can do: Retrieve project knowledge scoped to a path, so an agent gets the memories, rules and skills filed for the files it is working on
Fetch context on demand through the get_context MCP tool, at the depth a request needs
Capture decisions, gotchas and lessons from failing commands as short markdown notes filed next to the code they concern
Keep enforced rules ahead of advice and list whatever does not fit the per-prompt budget by title
Share the same knowledge across Claude Code, Codex, Cursor, GitHub Copilot, Windsurf and other MCP clients
When to use it: Useful when you keep repeating the same corrections to coding agents across sessions and tools, or when a CLAUDE.md or AGENTS.md file has grown large and is read in full on every step. It suits teams that want project conventions delivered per path rather than in one global file.
Requirements: Either the remote endpoint at cloud.pathrule.io with OAuth sign-in, or the local npm package @pathrule/mcp run through npx; the CLI setup path needs Node.js 22.14.0 or newer on macOS, Linux or Windows. Local mode needs no account, network or model. Cloud workspaces are opt-in and paid from AI Credits.

Before you install

Cloud mode stores your knowledge on Pathrule's servers and uses the prompt to rank it; its model tier may read a prompt to find a decision meant to last, and it is billed in AI Credits. Local mode runs no model and sends no telemetry, and source code is not uploaded automatically. Setup can change agent configuration, though it shows a plan first.

Installation

In SourceWeft

Open Pathrule in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.pathrule%2Fpathrule/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "pathrule": {
      "type": "http",
      "url": "https://cloud.pathrule.io/mcp"
    }
  }
}

README

[Pathrule]

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.

[npm] [License: Apache-2.0] [PathruleBench: Python · Go · TypeScript] [CI] [VS Code Marketplace] [Open VSX]

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.]

_{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

Quickstart

Node.js 22.14.0 or newer, on macOS, Linux or Windows.

bash

npm i -g @pathrule/clipathrule setup --local    # no account: knowledge stays on this machinepathrule doctor           # see what each agent receives

npm i -g @pathrule/clipathrule setup --local    # no account: knowledge stays on this machinepathrule 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.

Explain it once

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:

[Explain it once]

You fix it once, the way you normally would.
Pathrule files it next to the code it is about: a memory on features/, not a line in a file every session has to read.
Every agent knows from the next session on, whichever one you open.

Only what matters

A workspace collects hundreds of notes. An agent editing features/orders needs four of them.

[Only what matters]

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).

Three kinds of knowledge

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.”

Three ways in

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.

Why not just CLAUDE.md?

[PathruleBench: Python · Go · TypeScript]

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.

[Cost and input tokens a chain: CLAUDE.md climbs as knowledge grows, Pathrule stays flat]

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

Smarter the longer you use it.

Day one needs no account, no network and no model. Everything after builds on what you and your agents already did in this repository.

[Smarter the longer you use it.]

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.}

Switch agents. Keep the knowledge.

[Switch agents. Keep the knowledge.]

Agent	Before it acts	Instruction file	MCP
Claude Code	Hooks, prompt hook included	Pathrule's own `.claude/rules/pathrule/`	Local or Remote
Codex	Hooks, prompt hook included	—	Local or Remote
Cursor	—	—	Local
GitHub Copilot	—	—	Local
Windsurf	—	—	Local
Any MCP client	—	—	Local or Remote

Not another rules file

	A rules file	Pathrule
Written	By hand, kept current by hand	Grows as you and your agents work
Reaches	One tool per file	Every connected agent
Delivered	All of it, every session	Only what the path and the task need
Changes	When someone edits it	Versioned; new knowledge replaces old

Keep your CLAUDE.md and AGENTS.md: Pathrule does not edit them. It delivers the rest per path and per task, where a single file cannot.

What's in this repository

This is Pathrule's open-source foundation. It runs with no account and no network service: the store, retrieval and ranking, the MCP server, the hooks, the learning loop and the CLI.

Part	Here	Licence
Foundation: protocol, agent IR, the local knowledge store, host, MCP server, CLI, Pathrule Cloud client, agent integrations, Local Console, VS Code extension	Yes	Apache-2.0
Pathrule Cloud: team workspaces, sync, the web console, Remote MCP, the Cloud model tier	No	Proprietary

The 11 packages

protocol · agent-ir · core · integrations · mcp · host · ui · local-console · cloud · cli · vscode

bash

pnpm installpnpm typecheck      # every packagepnpm test           # every package's testspnpm build          # each package's npm build

pnpm installpnpm typecheck      # every packagepnpm test           # every package's testspnpm build          # each package's npm build

Your code stays yours

Source code is never uploaded automatically.
Local mode has no account, runs no model, and the open CLI sends no telemetry.
Your agent keeps its own model provider. Pathrule is not a model, an agent or an IDE.
Pathrule Cloud is opt-in. Signed in, it stores your knowledge and uses the prompt to rank it, and its model tier may read a prompt to find a decision meant to last.

Community

[Star history]

Contributors

[Contributors]

Contributing (DCO sign-off) · Code of conduct · Report a vulnerability · Get help · Trademark policy

License

Apache-2.0. See LICENSE and NOTICE. The Pathrule name and logo are not licensed under Apache-2.0.

pathrule.io · Docs · Pathrule Cloud

Source: README.md at commit 37dec9b

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.6LatestOct 19, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Other Pathrule integrations

Pathrule

io.pathruleOfficial publisher

Pathrule provides path-scoped team memories, rules and skills to MCP clients such as Claude Code, Cursor and Codex.

Streamable HTTPWeb executable

Knowledge & MemoryNot indexed yetOct 24, 2026