Pathrule

io.pathrulePublished by pathrule.ioOfficial publisherv0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Pathrule provides path-scoped team memories, rules and skills to MCP clients such as Claude Code, Cursor and Codex.

What you can do
Pathrule is a remote MCP server that supplies path-scoped team memories, rules and skills to compatible MCP clients. It is aimed at coding assistants like Claude Code, Cursor and Codex, so that shared guidance can be applied according to file paths. The registry description does not list individual tools, so the exact operations are not documented here.
When to use it
Consider it when a team wants shared memories, rules or skills to be available to several MCP-capable coding assistants and scoped by path. It is less relevant for individual users who do not need team-level, path-scoped guidance.
Requirements
A remote MCP endpoint at over streamable HTTP. The manifest declares no authentication, environment variables or headers, and no packages. A compatible MCP client is needed.
Before you install
The manifest declares no authentication, so anyone who can reach the endpoint may be able to use it; confirm access control before relying on it. The registry description does not state what data is sent to the service or whether it writes, changes or deletes anything.

Installation

In SourceWeft

  1. Open Pathrule in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.pathrule%2Fpathrule-remote-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "pathrule": {
      "type": "http",
      "url": "https://mcp.pathrule.io/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Pathrule integrations