Pathrule

Name: Pathrule
Author: io.pathrule

MCP serverMCP

Path-scoped team memories, rules and skills for Claude Code, Cursor, Codex and other MCP clients.

by io.pathrulerepository ↗homepage ↗v0.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"pathrule","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability109/109 checks ok

Endpoints

https://mcp.pathrule.io/mcpmcp streamable http · checked on a schedule

Registry facts

Not distributed through a package registry we index.

when	check	result	http	latency	detail
29 min ago	mcp initialize	ok	200	123 ms	server pathrule-cloud-connector 0.5.1 · protocol 2025-06-18 · 33 tools
7 h ago	mcp initialize	ok	200	125 ms	server pathrule-cloud-connector 0.5.1 · protocol 2025-06-18 · 33 tools
13 h ago	mcp initialize	ok	200	132 ms	server pathrule-cloud-connector 0.5.1 · protocol 2025-06-18 · 33 tools
20 h ago	mcp initialize	ok	200	125 ms	server pathrule-cloud-connector 0.5.1 · protocol 2025-06-18 · 33 tools
25 h ago	mcp initialize	ok	200	130 ms	server pathrule-cloud-connector 0.5.1 · protocol 2025-06-18 · 33 tools
31 h ago	mcp initialize	ok	200	132 ms	server pathrule-cloud-connector 0.5.1 · protocol 2025-06-18 · 33 tools
2 d ago	mcp initialize	ok	200	141 ms	server pathrule-cloud-connector 0.5.1 · protocol 2025-06-18 · 33 tools
2 d ago	mcp initialize	ok	200	143 ms	server pathrule-cloud-connector 0.5.1 · protocol 2025-06-18 · 33 tools
2 d ago	mcp initialize	ok	200	127 ms	server pathrule-cloud-connector 0.5.1 · protocol 2025-06-18 · 33 tools
2 d ago	mcp initialize	ok	200	141 ms	server pathrule-cloud-connector 0.5.1 · protocol 2025-06-18 · 33 tools

Tools observed via MCP handshake

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. R
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 w
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 workspa
pathrule_goto — Resolve a path/name/fuzzy target inside a workspace and return full content for that node plus a compact subtree memory index.
pathrule_get_tree — Return the full Pathrule node tree for a workspace.
pathrule_get_node — Return a single node plus ids for attached memories, rules, and skills. Requires workspace_id to prevent cross-workspace ambiguity.
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. Ret
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
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 ins
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 clou
pathrule_knowledge_map — Read-only map of this workspace's memories, rules and skills, grouped into regions by links and meaning. view=atlas: the whole system in under 1k tokens. view=r
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'
pathrule_update_memory — Update a memory's content or title, optionally moving it. Uses optimistic concurrency via expected_version_id. Cloud-only.
pathrule_delete_memory — Soft-delete a memory by default. Pass hard:true to permanently delete (requires workspace_admin). Cloud-only.
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.
pathrule_update_rule — Update a rule's fields and/or path. Optimistic concurrency via expected_version_id. Cloud-only.
pathrule_delete_rule — Soft-delete a rule by default. hard:true requires workspace_admin. Cloud-only.
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
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 conten
pathrule_delete_skill — Soft-delete a skill by default. hard:true requires workspace_admin. Cloud-only.
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. WORKF
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
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 ne
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
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
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
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.
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_content
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 path
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 cho
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 thi
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 conc
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?'

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Derived by Wellknown

Capabilities

Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.

dev.filesystemFilesystem100%commerce.ecommerceE-commerce Operations54%dev.terminalTerminal & Shell53%content.writingWriting & Editing51%dev.package-managementPackages & Dependencies51%

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.pathrule/pathrule-remote-mcp

first seen 1 mo ago · fetched 33 h agoopen ↗

Field history (7 recent events)

1 mo ago · declared · summary → "Path-scoped team memories, rules and skills for Claude Code, Cursor, Codex and other MCP clients."
1 mo ago · declared · description → "Path-scoped team memories, rules and skills for Claude Code, Cursor, Codex and other MCP clients."
1 mo ago · declared · publisherName → "io.pathrule"
1 mo ago · declared · homepageUrl → "https://www.pathrule.io"
1 mo ago · declared · repoUrl → "https://github.com/sertanhelvaci/pathrule"
1 mo ago · declared · version → "0.1.0"
1 mo ago · declared · protocols → ["mcp"]