PathruleLocal and Remote MCP
The same workspace knowledge across Pathrule surfaces, with explicit local and Remote MCP schemas, capabilities and access boundaries.
Your workspace knowledge is shared across the Pathrule surfaces you connect. MCP provides the transport and tool discovery. The local and hosted servers have different capabilities and schemas. An integration should inspect tools/list on the server it actually uses.
Choose a surface
| Surface | Connection | What it adds |
|---|---|---|
| CLI | Local stdio MCP, instruction files and supported hooks | Repository setup, knowledge authoring, project learning and local context delivery |
| VS Code extension | The same local runtime | Knowledge beside your code and client setup from the editor |
| Local Console | pathrule ui on loopback | Browse and edit local knowledge, activity and Local Signals |
| Cloud console | app.pathrule.io | Organizations, workspaces, members, billing and settings |
| Remote MCP | cloud.pathrule.io/mcp, Streamable HTTP and OAuth | Cloud knowledge access without installing a local process |
Shared knowledge, explicit schemas
Both MCP servers expose context and typed operations for memories, rules and skills. Local tools take node_path, support targeted content_edit updates and use expected_version_id for concurrency. Remote tools use a canonical path, title and body, and numeric expectedVersion for updates. Remote mutations also use an operation id for safe retries.
Local helpers include title resolution, batch reads, project learning, activity logging and refresh workflows. Remote MCP is a narrower Cloud knowledge surface, bound to the workspace you approved. Do not copy local tool arguments into a remote call without checking its schema.
Local and remote boundaries
The local runtime knows your repository and installs the files and hooks each client supports. Remote MCP cannot read local files or install hooks. It returns workspace knowledge when called and does not deliver local personal intelligence.
Your coding agent performs the coding work under its own provider account. Pathrule supplies knowledge; changing surfaces does not give Pathrule a coding-agent execution role.
See Remote MCP for remote schemas and authorization, and MCP tools reference for the local catalog.