Surfaces

Pathrule Remote MCP

The cloud-only MCP surface for Pathrule. A hosted Model Context Protocol server at mcp.pathrule.io that gives remote AI clients OAuth-scoped access to your workspace, with no local install.

Ask ChatGPT Ask Claude View as Markdown

Pathrule Remote MCP is a hosted Model Context Protocol server. It gives AI clients that only support cloud connectors access to your Pathrule workspace, memories, rules, skills, snapshots and activity, without installing Pathrule Studio or the CLI.

It runs at https://mcp.pathrule.io/mcp and authenticates with OAuth against your Pathrule account. Use it when your AI client cannot run a local MCP process over stdio and instead expects a remote endpoint.

Source: github.com/pathrule/mcp.

What Remote MCP is for

Cloud-only AI clients. Clients like Claude.ai, Claude Code remote and Codex remote can only reach a hosted connector. Remote MCP is that connector.
Same workspace, no install. Read and write the same memories, rules and skills your team sees on Pathrule Web, Studio and CLI.
Workspace bootstrap. List organizations, create a workspace, fetch the setup brief and write the first round of content entirely over the remote connection.

What Remote MCP does not do

Remote MCP is cloud only by design, the same boundary as Pathrule Web.

It does not read your local filesystem.
It does not run hooks against the working directory.
For hook-time injection and local repo access, use Pathrule Studio or the Pathrule CLI runtime.

Endpoints

MCP endpoint: https://mcp.pathrule.io/mcp
Registry manifest: https://mcp.pathrule.io/server.json

Connecting

Sign in or create an account at https://app.pathrule.io.
Create or select a workspace.
Point your MCP client at https://mcp.pathrule.io/mcp.
Complete the OAuth flow to approve workspace access.

Once approved, the client can read context and write content against the workspace you selected.

Tools and security

Read tools: list workspaces, get context, read memories, rules, skills and snapshots.
Write tools: create, update and delete memories, rules and skills.
Activity: snapshots, refresh tasks and activity logging.
Scopes: access is gated by OAuth scopes pathrule:read, pathrule:write and pathrule:activity, plus database row-level security and rate limiting.

When to use Remote MCP

Use Remote MCP when your AI client only speaks to a hosted connector, or when you want workspace access from a machine where you have not installed Pathrule. For local hook execution and repo-aware context, use the Studio or CLI surfaces instead.