pathrule_list_workspacesLABSCO SUMMARY
Project context follows the agent instead of the machine.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
Add the hosted endpoint — paste it into your client
USE CASES
01
Getting an agent up to speed on a directory
Move to the path, read the context that applies there, and walk the tree around it. The agent starts with the rules that govern that part of the project rather than the whole of it.
02
Writing down a decision so the next session has it
Store the decision as a memory, amend it when it changes, and list what is already there before adding a duplicate.
03
Keeping a project rule in force
Write the rule once and read it back where it applies. Updating it in the workspace updates it for every client that connects.
04
Capturing the state of a workspace before a big change
Take a snapshot, then list and read snapshots later to see what the workspace looked like before the change went in.
05
Clearing the queue of context that has gone stale
List what is waiting on a refresh, read the brief for one, and resolve it — the maintenance pass that keeps stored context worth trusting.
06
Standing up a workspace for a new project
Find the organisation, create the workspace under it, and run setup — done from the client rather than in the app.
30 tools
Listed in project docs. Your client may show a different list.
pathrule_get_contextpathrule_gotopathrule_get_treepathrule_get_nodepathrule_list_memoriespathrule_read_memorypathrule_read_rulepathrule_read_skillpathrule_pingpathrule_list_organizationspathrule_create_workspacepathrule_setuppathrule_write_memorypathrule_update_memorypathrule_delete_memorypathrule_write_rulepathrule_update_rulepathrule_delete_rulepathrule_write_skillpathrule_update_skillpathrule_delete_skillpathrule_take_snapshotpathrule_list_snapshotspathrule_read_snapshotpathrule_list_pending_refreshespathrule_get_refresh_briefpathrule_resolve_refreshpathrule_log_activitypathrule_get_local_runtime_upgradeBEFORE YOU INSTALL
What to know first
Tools you get
30 tools named in the project's documentation. Read tools need the pathrule:read scope, the nine write tools pathrule:write, and refresh and activity tools pathrule:activity. Writes also need an active workspace subscription and are rate-limited per user.
INSTALLATION
Connect your client
Paste it into your client.
Server setup
Setup
Create or sign in to a Pathrule account at https://app.pathrule.io
Create or select a Pathrule workspace in the app
Connect your MCP client to https://mcp.pathrule.io/mcp
Approve the OAuth flow through Pathrule Web when the client connects
Hosted endpoint
ENDPOINT URL
https://mcp.pathrule.io/mcpAdd this hosted endpoint to your MCP client.
