MCP
Every Pathrule surface speaks the same MCP contract, so an agent sees the same tools and the same path-scoped context wherever it connects. Locally that means Studio or the CLI; for a cloud-only client there is a hosted endpoint.
local: the server Studio and the CLI already run
$ pathrule start
mcp stdio server ready · hooks registered
cloud-only client: point it at the hosted endpoint
$ https://mcp.pathrule.io/mcp
oauth: pathrule:read pathrule:write pathrule:activity
registry manifest: https://mcp.pathrule.io/server.json
The same typed surface every Pathrule client sees, gated by scope rather than by trust.
Read the workspace
List workspaces and get context for a path. Memories, rules, skills and snapshots come back typed rather than as a blob of text.
Write, path-first
Create, update and delete content at a path. A missing node materializes on demand, so an agent never has to build the tree before writing to it.
Log what happened
Snapshots, refresh tasks and activity logging. This is what lets knowledge be reviewed later instead of only written.
Gated by scope
Access is per workspace. OAuth scopes, database row-level security and rate limiting decide what a client may touch.
`mcp.pathrule.io/mcp`
The hosted endpoint, for clients that only speak to a connector. Nothing to install, and the registry manifest sits beside it at /server.json.
Local, over stdio
Studio and the CLI run the same server on your machine. That is the version that can resolve your working directory and run hooks.
Both speak the same tool contract. What differs is what they can reach, and that is worth being precise about.
01
Local, in Studio or the CLI
Runs on your machine over stdio. It resolves your working directory, reads the local cache and runs hooks.
02
Hosted, for cloud-only clients
An OAuth endpoint for clients like Claude.ai and Codex remote that can only reach a connector. Nothing to install.
03
The difference that matters
The hosted endpoint cannot read local files or run hooks, so it answers on request rather than before the first tool call.
MCP overview
The contract, the roles, and how Pathrule fits into them.
Tools reference
Every tool an agent can call, with its shape.
One contract, every surface
Why the tool surface is identical whether the runtime is local or hosted.
Remote MCP
The hosted endpoint: what it is for, and what it deliberately does not do.
Claude Code
Connecting Claude Code, and where its hooks come from.
Cursor
Connecting Cursor, and how it sits with Cursor's own rules.
