# Pathrule MCP server > Give coding agents path-scoped project memories, rules and skills, stored locally or in Pathrule Cloud. - Listing: https://mcp.tc/i/pathrule - Connect: use the server's own URL `https://cloud.pathrule.io/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [AI & Machine Learning](https://mcp.tc/c/ai-ml) - Vendor: Pathrule - Homepage: - Repository: - Package: npm `@pathrule/mcp` ## About Pathrule is a knowledge layer for coding agents. It serves project, personal and team memories, rules and skills scoped to paths in your code, so agents such as Claude Code, Codex, Cursor, Copilot and Windsurf get the relevant context. Tools include pathrule\_get\_context, pathrule\_resolve, pathrule\_read\_memory and pathrule\_write\_memory. It runs as a local stdio package (@pathrule/mcp via npx) over a store on your machine, or as a hosted streamable-http endpoint at Pathrule Cloud. The hosted endpoint needs a Pathrule Cloud account. The vendor's access documentation does not describe the sign-in method in detail. ## What it can do - Fetch path-scoped context for the code being edited - Read stored project memories - Write new memories for future sessions - Resolve rules and skills that apply to a path - Use a local store or a Pathrule Cloud workspace ## Example prompts - "Get the Pathrule context for the src/auth folder before changing it." - "Save a memory that token refresh broke login once in this project." - "Read the memories that apply to the billing module." - "Resolve which rules and skills apply to this file." ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http pathrule https://cloud.pathrule.io/mcp ``` 2. Start Claude Code, type `/mcp`, pick **pathrule** and choose **Authenticate**. A browser window opens for the Pathrule sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**. 2. Name it **Pathrule** and paste this URL: ```url https://cloud.pathrule.io/mcp ``` 3. Click **Add**, then **Connect**, and sign in when Pathrule asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://cloud.pathrule.io/mcp` and click **Add**. 3. Click **Connect** and sign in when Pathrule asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://cloud.pathrule.io/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Pathrule to sign in. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "pathrule": { "url": "https://cloud.pathrule.io/mcp" } } } ``` Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"pathrule","type":"http","url":"https://cloud.pathrule.io/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "pathrule": { "type": "http", "url": "https://cloud.pathrule.io/mcp" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "pathrule": { "serverUrl": "https://cloud.pathrule.io/mcp" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add pathrule --url https://cloud.pathrule.io/mcp codex mcp login pathrule ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.pathrule] url = "https://cloud.pathrule.io/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http pathrule https://cloud.pathrule.io/mcp ``` Then, inside Gemini CLI, run `/mcp auth pathrule` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "pathrule": { "type": "http", "url": "https://cloud.pathrule.io/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://cloud.pathrule.io/mcp`. ## Details - Server version: 1.0.6 - Last checked: 2026-10-25 (reachable, asks for credentials) - Listed: 2026-10-25 - Updated: 2026-10-25 --- Source: https://mcp.tc/i/pathrule (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report