The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Pathrule MCP listing page.
Pathrule Remote MCP exposes Pathrule workspace memory, rules, skills, setup, snapshots, and activity logging over the Model Context Protocol.
Public endpoint:
Registry manifest:
Pathrule gives AI coding agents path-scoped project context. The remote MCP server lets cloud MCP clients use the same Pathrule workspace data without installing Pathrule Desktop or the local CLI on the client host.
Remote MCP is intentionally cloud-only. It can read and write Pathrule cloud records, but it cannot read local files, install hooks, render AGENTS.md / CLAUDE.md, or materialize local skills. For those local runtime features, use Pathrule Desktop or @pathrule/cli.
Pathrule Remote MCP is the MCP endpoint for Pathrule Web workspaces. It is not a general-purpose hosted memory service that works without Pathrule.
To use it:
Create or select a Pathrule workspace in the app.
Connect your MCP client to:
When an MCP client connects, it starts an OAuth flow through Pathrule Web. After approval, the client can access only the Pathrule workspaces visible to that signed-in account, using the scopes you approved.
This repository is the public source and directory listing target for Pathrule's Remote MCP endpoint. It is not a standalone local memory database, and it does not create a usable Pathrule workspace without a Pathrule account.
Workspace and context:
pathrule_list_workspacespathrule_get_contextpathrule_gotopathrule_get_treepathrule_get_nodepathrule_list_memoriespathrule_read_memorypathrule_read_rulepathrule_read_skillpathrule_pingWorkspace setup:
pathrule_list_organizationspathrule_create_workspacepathrule_setupWrites:
pathrule_write_memorypathrule_update_memorypathrule_delete_memorypathrule_write_rulepathrule_update_rulepathrule_delete_rulepathrule_write_skillpathrule_update_skillpathrule_delete_skillSnapshots, refreshes, and activity:
pathrule_take_snapshotpathrule_list_snapshotspathrule_read_snapshotpathrule_list_pending_refreshespathrule_get_refresh_briefpathrule_resolve_refreshpathrule_log_activitypathrule_get_local_runtime_upgradepathrule:read; write tools require pathrule:write; refresh/activity tools require pathrule:activity.The mcp.pathrule.io service is operated by Pathrule. The environment variables below are for Pathrule operators deploying the service against Pathrule's backend. They are not required to connect an MCP client to Pathrule Remote MCP.
Required production secrets are environment variables only. Do not commit values for:
SUPABASE_JWT_SECRET is used to sign short-lived authenticated-role user JWTs for Supabase RLS. Treat it like production infrastructure secret material and store it only in the hosting provider's secret manager.
The public pathrule/mcp repository is staged from the Pathrule monorepo and contains a bundled Node.js server for transparency and deployment reproducibility. Running it yourself requires the environment variables above and Pathrule's compatible backend; it is not the recommended user setup path.
The server listens on PORT and HOST:
Health and metadata:
The public repository includes a Dockerfile for MCP registry scanners such as Glama. The container sets PATHRULE_MCP_PUBLIC_INTROSPECTION=1, which exposes MCP schema introspection without a bearer token so registries can verify the server shape.
That mode does not grant Pathrule data access. Tool calls still require an authenticated Pathrule context and return auth errors without OAuth.
Glama's Docker build runner launches MCP servers through stdio. Use this command in Glama's Dockerfile admin form:
Use these fields for MCP directories:
MIT