PathruleTyped tools,
local or hosted.
Pathrule speaks the Model Context Protocol in two places. The local server comes with the CLI and the VS Code extension, and every supported client can use it. Remote MCP is a hosted endpoint you sign in to with your Pathrule account, for clients that connect over HTTP.
zsh
# local: written for you by pathrule setup or pathrule install$ pathrule install cursor[ok] cursor: installed (~/.cursor/mcp.json)# remote: Streamable HTTP, OAuth 2.1 sign-in$ claude mcp add --transport http pathrule https://cloud.pathrule.io/mcp$ codex mcp add pathrule --url https://cloud.pathrule.io/mcpOAuth discovery: https://cloud.pathrule.io/.well-known/oauth-authorization-server
What an agent can do with it.
Read the workspaceGet context and read typed memories, rules and skills. Local helpers can list workspaces; a remote grant is already bound to one approved workspace.Write, path-firstCreate, update and delete content at a path. A missing node is created on demand, so an agent never has to build the tree before writing to it.Log what happenedLocal MCP includes refresh tasks and activity logging. Remote MCP exposes knowledge mutations and history, with its own catalog and schemas.Gated by scopeAccess is per workspace. On the hosted endpoint, OAuth scopes, current workspace membership, server-side access checks and rate limiting decide what a client may touch.
cloud.pathrule.io/mcpThe hosted endpoint, for Claude Code, Codex, Claude.ai as a custom connector, and any other client that supports Streamable HTTP with OAuth. The public server card describes its connection and authorization metadata.Local, over stdioThe CLI and the VS Code extension run the server on your machine. Cursor, GitHub Copilot and Windsurf reach Pathrule through this one alone: the CLI writes no hooks or files for them.Typed tools for workspace knowledge, gated by scope rather than by trust.
Local server, hosted endpoint.
- Local, with the CLI or VS CodeRuns on your machine over stdio and resolves your working directory. The CLI or the extension also writes hooks and knowledge files for Claude Code, and for Codex when the repository has Codex files.
- Remote, for HTTP clientsAn OAuth 2.1 endpoint for Claude Code, Codex, Claude.ai and other clients that support Streamable HTTP. Nothing to install.
- The difference that mattersRemote MCP does not read local files, install hooks or write companion files, and it has no local mode. It answers when the agent asks, rather than before the agent acts.
Both expose typed workspace knowledge. Local stdio and Remote MCP have different tool catalogs, schemas and delivery capabilities.
Where to go deeper.
- MCP overviewThe contract, the roles, and how Pathrule fits into them.
- Tools referenceEvery tool an agent can call, with its shape.
- Local and Remote MCPWhat the local server and Remote MCP share, and where they differ.
- Remote MCPThe hosted endpoint: what it is for, and what it deliberately does not do.
- Claude CodeConnecting Claude Code locally or to Remote MCP, and where its hooks come from.
- CursorConnecting Cursor through the CLI or the VS Code extension.