Pathrule is a remote MCP server that gives an AI agent 32 tools, among them pathrule_create_workspace, pathrule_delete_memory, pathrule_delete_rule. It answers at https://mcp.pathrule.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.
Path-scoped team memories, rules and skills for Claude Code, Cursor, Codex and other MCP clients.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
pathrule_create_workspace | Create a new Pathrule workspace inside an organization. Cloud-only: writes the workspace row through the user's JWT (RLS enforces organization membership). Does NOT attach the workspace to a local folder, does NOT install any AI client conf Inputs: organization_id, name, git_remote_url, active_agent_targets |
pathrule_delete_memory | Soft-delete a memory by default. Pass hard:true to permanently delete (requires workspace_admin). Cloud-only. Inputs: workspace_id, memory_id, hard, expected_version_id |
pathrule_delete_rule | Soft-delete a rule by default. hard:true requires workspace_admin. Cloud-only. Inputs: workspace_id, rule_id, hard, expected_version_id |
pathrule_delete_skill | Soft-delete a skill by default. hard:true requires workspace_admin. Cloud-only. Inputs: workspace_id, skill_id, hard, expected_version_id |
pathrule_get_context | Return Pathrule context for a workspace path: relevant memories, rules, skills, subtree index, and a next_required_action hint. Remote clients must pass workspace_id; call pathrule_list_workspaces first when unsure. No cwd or local_root_pat Inputs: workspace_id, node_path, user_intent, known_protocol_version |
pathrule_get_local_runtime_upgrade | Explain what Pathrule CLI (power-user, terminal-first) and Pathrule Studio (GUI) unlock beyond Remote MCP. Call this when the user asks 'is there a better way?', 'why do I need to install something?', wants hook-level automation, or wants t |
pathrule_get_node | Return a single node plus ids for attached memories, rules, and skills. Requires workspace_id to prevent cross-workspace ambiguity. Inputs: workspace_id, node_id |
pathrule_get_refresh_brief | Claim one refresh task and return the subject, stale-signal evidence, AI instructions, and any proposed patch. Call pathrule_list_pending_refreshes first to choose a refresh_id. Remote MCP can inspect cloud records only; use Desktop/CLI bef Inputs: refresh_id |
pathrule_get_tree | Return the full Pathrule node tree for a workspace. Inputs: workspace_id |
pathrule_goto | Resolve a path/name/fuzzy target inside a workspace and return full content for that node plus a compact subtree memory index. Inputs: workspace_id, target, subtree_limit |
pathrule_import_pattern | Import an official Pathrule pattern (a bundle of memories, rules, and skills) into the workspace when the user pastes a `::pathrule:package:<slug>` token. WORKFLOW: (1) First call with `dry_run: true` to see the pattern's `appliesTo` (stack Inputs: workspace_id, slug, node_path, dry_run, verbose |
pathrule_list_memories | List active memories attached to a specific Pathrule tree node. Use pathrule_get_context, pathrule_goto, or pathrule_get_node first to discover the node_id. Returns compact previews only; call pathrule_read_memory with a memory_id when you Inputs: node_id |
pathrule_list_organizations | List Pathrule organizations the authenticated user belongs to. Use this before pathrule_create_workspace when you need to ask the user which organization the new workspace should live under. Returns id, name, slug, plan, subscription_status |
pathrule_list_pending_refreshes | List pending Pathrule refresh tasks for a workspace. Refresh tasks are cloud suggestions that may update stale memories or rules. Use this first, then call pathrule_get_refresh_brief with a returned refresh_id before deciding whether to rej Inputs: workspace_id, include_in_progress |
pathrule_list_snapshots | List the most recent project snapshots for a workspace (compact metadata only — no file_tree, no sampled_contents). Use to find which snapshot to read in full. Up to 25 per call, ordered newest first. Inputs: workspace_id, limit, source |
pathrule_list_workspaces | List Pathrule workspaces visible to the authenticated user through cloud RLS. Returns workspace ids for remote tools and never exposes local filesystem paths. Response includes a `local_runtime.cta` reminder — mention Pathrule Studio/CLI wh |
pathrule_log_activity | Log a file-modifying response from a remote MCP client. Remote MCP requires workspace_id and stamps ai_client='cloud-connector'. task_summary should be ONE concise sentence (ideally ≤300 chars); it is NEVER rejected for length (past ~500 ch Inputs: workspace_id, node_path, domain, action, scope, subjects |
pathrule_ping | Sanity check that Pathrule Remote MCP is reachable. Cloud-safe: returns no local cwd. Response includes a `local_runtime.cta` line you can surface to the user when they ask about deeper Pathrule features. Inputs: message |
pathrule_read_memory | Read the full body and metadata for one Pathrule memory. Use this after pathrule_get_context, pathrule_goto, or pathrule_list_memories returns a memory_id. This reads cloud data only and does not inspect the user's local filesystem. Inputs: memory_id |
pathrule_read_rule | Read the full body and metadata for one Pathrule rule. Use this after pathrule_get_context, pathrule_goto, or pathrule_get_node returns a rule_id. Rules are instructions the AI should obey for a project path; this tool only reads the cloud Inputs: rule_id |
pathrule_read_skill | Read the approved snapshot for one Pathrule skill. Use this after pathrule_get_context, pathrule_goto, or pathrule_get_node returns a skill_id. Returns the cloud SKILL.md content for the AI to follow; it does not install or materialize file Inputs: skill_id |
pathrule_read_snapshot | Load a single project snapshot in full or partial form. Defaults include file_tree and sampled_contents — pass include_file_tree=false / include_sampled_contents=false to keep the response compact when you only need metadata. Inputs: workspace_id, snapshot_id, include_file_tree, include_sampled_contents |
pathrule_remove_pattern | Remove a previously-imported Pathrule pattern bundle in one call — the reverse of pathrule_import_pattern. The pattern definition is the manifest, so this finds and deletes the memories/rules/skills whose titles match the pattern's pieces. Inputs: workspace_id, slug, node_path, verbose |
pathrule_resolve_refresh | Close a Pathrule refresh task after reviewing its brief. Normal remote flow: call pathrule_list_pending_refreshes, then pathrule_get_refresh_brief, then use this tool with status='rejected' when the signal is stale or not actionable. Remote Inputs: refresh_id, status, note |
pathrule_setup | Fetch the active Pathrule bootstrap brief and execute it. Call this ONCE when the user asks to set up / bootstrap / initialize Pathrule for a project (e.g. 'Set up Pathrule for this project', 'Bootstrap Pathrule'). The response `body` is a Inputs: workspace_id, locale |
pathrule_take_snapshot | Record a point-in-time inventory of the user's project under a workspace. Remote MCP cannot see the filesystem, so YOU (the AI) collect this inventory with your own Read/Glob/Grep tools before calling this. Persist it so future setup, boots Inputs: workspace_id, source, project_name, root_path, git_remote_url, git_head |
pathrule_update_memory | Update a memory's content or title, optionally moving it. Uses optimistic concurrency via expected_version_id. Cloud-only. Inputs: workspace_id, memory_id, content, title, expected_version_id, move_to_path |
pathrule_update_rule | Update a rule's fields and/or path. Optimistic concurrency via expected_version_id. Cloud-only. Inputs: workspace_id, rule_id, expected_version_id, patch, move_to_path, allow_duplicate |
pathrule_update_skill | Partially update an existing Pathrule skill record. Use pathrule_update_skill only when you already have a skill_id and want to change metadata, SKILL.md content, source/github_url, tags, or move the skill to another workspace path; use pat Inputs: workspace_id, skill_id, expected_version_id, patch, move_to_path |
pathrule_write_memory | Create a new memory at a workspace path. Missing nodes auto-create. Blocks duplicate titles unless allow_duplicate is set. Cloud-only: never writes to the user's local filesystem. For automatic CLAUDE.md/AGENTS.md sync and on-disk hook inje Inputs: workspace_id, node_path, title, content, source, allow_duplicate |
pathrule_write_rule | Create a new rule at a workspace path. Missing nodes auto-create. Use scope_type/priority honestly: high only when a violation causes a real bug or regression. Cloud-only — Pathrule Studio/CLI also renders the rule into the user's CLAUDE.md Inputs: workspace_id, node_path, name, content, scope_type, priority |
pathrule_write_skill | Create a new skill at a workspace path. Content is the full SKILL.md body (frontmatter + markdown). For github_ref skills set source='github_ref' and github_url. Cloud-only: does NOT materialize the skill into .codex/skills, .claude/skills, Inputs: workspace_id, node_path, name, description, content, source |
Every block below points at https://mcp.pathrule.io/mcp. Pick your client and copy.
claude mcp add --transport http pathrule https://mcp.pathrule.io/mcp
{
"mcpServers": {
"pathrule": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.pathrule.io/mcp"]
}
}
}{
"mcpServers": {
"pathrule": {
"url": "https://mcp.pathrule.io/mcp"
}
}
}{
"servers": {
"pathrule": {
"type": "http",
"url": "https://mcp.pathrule.io/mcp"
}
}
}{
"context_servers": {
"pathrule": {
"url": "https://mcp.pathrule.io/mcp"
}
}
}{
"mcpServers": {
"pathrule": {
"serverUrl": "https://mcp.pathrule.io/mcp"
}
}
}{
"mcpServers": {
"pathrule": {
"url": "https://mcp.pathrule.io/mcp"
}
}
}name: Pathrule
version: 0.0.1
schema: v1
mcpServers:
- name: Pathrule
type: streamable-http
url: https://mcp.pathrule.io/mcp{
"mcpServers": {
"pathrule": {
"httpUrl": "https://mcp.pathrule.io/mcp"
}
}
}{
"mcpServers": {
"pathrule": {
"type": "http",
"url": "https://mcp.pathrule.io/mcp"
}
}
}{
"mcpServers": {
"pathrule": {
"url": "https://mcp.pathrule.io/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.pathrule.io%2Fmcp&type=streamable_http&id=pathrule&name=Pathrule
It answered our last check on 24 October 2026 in 518 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by pathrule.io and served from mcp.pathrule.io, the vendor's own domain: https://mcp.pathrule.io/mcp.
32, as returned by the server's own tools/list on 22 September 2026: pathrule_create_workspace, pathrule_delete_memory, pathrule_delete_rule, pathrule_delete_skill, pathrule_get_context, pathrule_get_local_runtime_upgrade, pathrule_get_node, pathrule_get_refresh_brief, and 24 more.
It answered our last check on 24 October 2026 in 518 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.pathrule.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.pathrule. Endpoint host: mcp.pathrule.io. ARD identifier: urn:air:io.pathrule:mcp:pathrule-remote-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.