Pathrule's premise is path-scoped context — the rules and memories that apply where you are in the tree. Over the remote endpoint that context reaches any client able to hold an OAuth session, which is what makes the same workspace usable from something other than your own laptop.
The remote MCP endpoint for Pathrule Web workspaces, at https://mcp.pathrule.io/mcp. It exposes workspace memory, rules, skills, setup, snapshots and activity logging, so a cloud client can use Pathrule data without Pathrule Desktop or the CLI installed on its host.
- Workspaces listed, created and set up, and the context for the path you are working under
- The workspace tree walked node by node, with a call to move where you are pointed
- Memories, rules and skills read — and written, updated or deleted where your scopes allow it
- Snapshots taken, listed and read back
- Pending refreshes listed, briefed and resolved
- Activity logged against the workspace
A Pathrule account and a workspace created in the app. Connecting starts an OAuth flow through Pathrule Web, and the client then sees only the workspaces that account can see, under the scopes you approved. It is cloud-only: it cannot read local files, install hooks, or render AGENTS.md or CLAUDE.md.