Pathrule Remote MCP

Connect a hosted MCP client to https://cloud.pathrule.io/mcp to read and write knowledge in a Pathrule Cloud workspace. It uses Streamable HTTP and OAuth 2.1 with PKCE. You need a Pathrule account and access to the workspace you approve.

Connect

Create or sign in to your account at https://app.pathrule.io, then connect your MCP client:

claude mcp add --transport http pathrule https://cloud.pathrule.io/mcp
codex mcp add pathrule --url https://cloud.pathrule.io/mcp

For Claude.ai or another HTTP MCP client, use the same endpoint. Complete the authorization flow and approve the workspace and scopes the client requests.

Discovery

• MCP: https://cloud.pathrule.io/mcp
• Authorization server: https://cloud.pathrule.io/.well-known/oauth-authorization-server
• Protected resource: https://cloud.pathrule.io/.well-known/oauth-protected-resource/mcp

Tools and grants

A read grant exposes pathrule_get_context and list and read tools for memories, rules and skills. A write grant also exposes creation, updates, deletion and per-item history. Access is limited to the grant's workspace; supplying another workspace id cannot widen it.

Remote writes use title, body and a canonical path. Updates use an item id and numeric expectedVersion. Mutations need a stable operation_id or idempotency key, so retrying an operation does not create a second copy. These are remote schemas, not the local server's content_edit and expected_version_id schemas. Ask the connected server for tools/list before using them.

The authorization server recognizes pathrule:read, pathrule:write, pathrule:refresh and pathrule:activity. A recognized scope does not imply a tool exists: the current remote catalog covers knowledge and context. Organization administration, workspace creation, snapshots, local project learning, pattern imports, activity logging and refresh workflows use the CLI, local MCP tools or Cloud console.

Permissions remain current

The server checks your session, workspace state and membership when it authorizes access and executes a tool. Removal from a workspace, archive or deletion revokes its grants. Restoring the workspace does not revive those grants; reconnect and approve access again. Refresh tokens rotate, and replaying an already rotated token revokes its token family.

Local delivery

Remote MCP cannot read your filesystem, install hooks, write companion files or send local personal preferences. An agent must call its tools to obtain context. Use the CLI or VS Code when you want repository-aware context and hooks before the agent acts.