Pathrule Remote

Pathrule Remote MCP exposes Pathrule workspace memory, rules, skills, setup, snapshots, and activity logging over the Model Context Protocol.

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, renderAGENTS.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.
-

Create or select a Pathrule workspace in the app.

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.

- pathrule_list_workspaces
- pathrule_get_context
- pathrule_goto
- pathrule_get_tree
- pathrule_get_node
- pathrule_list_memories
- pathrule_read_memory
- pathrule_read_rule
- pathrule_read_skill
- pathrule_ping

- pathrule_list_organizations
- pathrule_create_workspace
- pathrule_setup

- pathrule_write_memory
- pathrule_update_memory
- pathrule_delete_memory
- pathrule_write_rule
- pathrule_update_rule
- pathrule_delete_rule
- pathrule_write_skill
- pathrule_update_skill
- pathrule_delete_skill

- pathrule_take_snapshot
- pathrule_list_snapshots
- pathrule_read_snapshot
- pathrule_list_pending_refreshes
- pathrule_get_refresh_brief
- pathrule_resolve_refresh
- pathrule_log_activity
- pathrule_get_local_runtime_upgrade

- OAuth scopes decide the tool surface. Read tools requirepathrule:read; write tools requirepathrule:write; refresh/activity tools requirepathrule:activity.
- Every workspace operation runs through the authenticated user's Supabase JWT and database RLS policies.
- The connector does not use Supabase admin keys to widen user access.
- Write tools are also gated by workspace subscription status and per-user/per-workspace rate limits.
- MCP event telemetry is metadata-only: tool name, user/workspace/client identifiers, status/error code, and latency bucket. Tool input and content bodies are not logged.
- The remote server never accesses the user's filesystem and never writes local companion files.

Themcp.pathrule.ioservice 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_URL SUPABASE_ANON_KEY SUPABASE_JWT_SECRET PATHRULE_CONNECTOR_TOKEN_ENCRYPTION_KEY PATHRULE_CONNECTOR_TOKEN_ENCRYPTION_KEY_VERSION PATHRULE_CONNECTOR_TOKEN_ENCRYPTION_PREVIOUS_KEYS PATHRULE_WEB_ORIGIN

SUPABASE_JWT_SECRETis 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 publicpathrule/mcprepository 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.

curl -fsS http://localhost:8787/healthz curl -fsS http://localhost:8787/server.json

The public repository includes aDockerfilefor MCP registry scanners such as Glama. The container setsPATHRULE_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:

["node", "dist/glama-stdio.js"]

GitHub Repository URL: https://github.com/pathrule/mcp npm Package: leave blank unless @pathrule/mcp is published Short Description: Path-scoped team memories, rules and skills for AI coding agents. Server URL: https://mcp.pathrule.io/mcp

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .

Instead of direct calling MCP tools, mcpcode server transforms MCP tool calls into TypeScript programs, enabling smarter, lower-latency orchestration by LLMs.

Supercharge your Agent with Semantic Code Intelligence and save 💰 in the process!

AI-to-AI code review platform — Claude, Codex, and Gemini cross-check each other via MCP, REST API, and CLI for consensus-based results.

A code sandbox for AI assistants to safely execute arbitrary code. Requires a 302AI API key for authentication.

Agent-native developer Q&A API with MCP + A2A endpoints for citations, job pickup, and answer submission.

MCP server to dynamically load Claude Code skills into AI agents

MCP bridge that lets Claude Code delegate heavy tasks to the Antigravity CLI (agy) — purpose-built tools, model routing with fallback, session continuity, and output truncation to save Claude's context and tokens.

Exposes local execution of Aider commands as a detached process using MCP.

An MCP server for offloading AI coding tasks to Aider, enhancing development efficiency and flexibility.