Skip to content
Back to search

moor

Moor is a local MCP control plane for Mac. It gives every coding agent one safe, observable, configurable gateway to your MCP servers.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/varandrew/moor with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/varandrew/moor'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/varandrew--moor/badge.svg)](/listings/varandrew--moor)

HTML

<a href="/listings/varandrew--moor"><img src="/api/listings/varandrew--moor/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

macOS App

Download the `.dmg` from [Releases](https://github.com/varandrew/moor/releases), drag to Applications, done. The app bundles the HTTP server as an in-process Rust binary — no pre-installed Node.js runtime required.

Windows App

Download the Windows installer from [Releases](https://github.com/varandrew/moor/releases) and run it. The app bundles the HTTP server as an in-process Rust binary — no pre-installed Node.js runtime required.

Linux App

Download the `.deb`, `.rpm`, or `.AppImage` from [Releases](https://github.com/varandrew/moor/releases) (x86_64 and aarch64 builds are produced by CI). The app bundles the HTTP server as an in-process Rust binary — no pre-installed Node.js runtime required. macOS remains the primary target; Linux builds are produced by CI but less extensively tested.

Build from Source

Requires macOS (Apple Silicon / Intel), Windows x64, or Linux (x86_64 / aarch64), Node.js >= 22 (CI uses 24), pnpm >= 10, and Rust >= 1.77.

git clone https://github.com/varandrew/moor.git
cd moor
pnpm install

See [Development](#development) for build instructions.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 422 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <img src="src-tauri/icons/128x128.png" alt="Moor" width="128">
  3. </p>
  4. <h1 align="center">Moor</h1>
  5. <p align="center">
  6. <b>Local MCP Gateway Manager for AI Agents</b><br>
  7. Aggregate multiple MCP servers into a single endpoint, filter tools by Profile, and manage everything from a beautiful native UI.
  8. </p>
  9. <p align="center">
  10. <img src="https://img.shields.io/badge/license-MIT-blue" alt="License">
  11. <img src="https://img.shields.io/badge/React-19-61DAFB?logo=react" alt="React 19">
  12. <img src="https://img.shields.io/badge/Tauri-2-24C8D8?logo=tauri" alt="Tauri 2">
  13. <img src="https://img.shields.io/badge/Node.js-22+-339933?logo=nodedotjs" alt="Node.js 22+">
  14. <img src="https://img.shields.io/badge/platform-macOS-black?logo=apple" alt="macOS">
  15. <img src="https://img.shields.io/badge/platform-Windows-0078D4?logo=windows" alt="Windows">
  16. <img src="https://img.shields.io/badge/platform-Linux-FCC624?logo=linux&logoColor=black" alt="Linux">
  17. <img src="https://img.shields.io/badge/pnpm-11+-F69220?logo=pnpm" alt="pnpm">
  18. </p>
  19. <p align="center">
  20. <a href="#install">Install</a> ·
  21. <a href="#quickstart">Quickstart</a> ·
  22. <a href="#features">Features</a> ·
  23. <a href="#architecture">Architecture</a> ·
  24. <a href="#development">Development</a> ·
  25. <a href="#api">API</a>
  26. </p>
  27. <!-- README-I18N:START -->
  28. **English** | [汉语](./README.zh.md) | [日本語](./README.ja.md) | [Español](./README.es.md)
  29. <!-- README-I18N:END -->
  30. ---
  31. > [!NOTE]
  32. > This README describes the current source tree. Packaged releases may not yet include every feature documented here; check the [release notes](https://github.com/varandrew/moor/releases) for your version.
  33. > _AI Agents need tools, but managing dozens of MCP servers across different clients is a mess. I wanted a single gateway that aggregates everything, filters by context, and keeps running in the background — all controllable from a beautiful native UI._
  34. >
  35. > _Moor exposes one endpoint (`http://127.0.0.1:<port>/mcp`) that dynamically serves only the tools you want, based on your active Profile. Switch profiles without disconnecting your Agent, with tool-call auditing enabled by default. That's why I built it._
  36. <p align="center">
  37. <img src="./assets/Dashboard%20Page.png" alt="Dashboard" width="800"><br>
  38. <sub>Dashboard — Overview of active Profile, server status, and audit stats.</sub>
  39. </p>
  40. <p align="center">
  41. <img src="./assets/Servers%20Page.png" alt="Servers" width="800"><br>
  42. <sub>Servers — Manage MCP servers, import configs, monitor health.</sub>
  43. </p>
  44. <p align="center">
  45. <img src="./assets/Profiles%20Page.png" alt="Profiles" width="800"><br>
  46. <sub>Profiles — Create profiles, toggle servers, enable/disable tools.</sub>
  47. </p>
  48. <p align="center">
  49. <img src="./assets/Audit%20Page.png" alt="Audit" width="800"><br>
  50. <sub>Audit — Inspect every tool call with full context and filters.</sub>
  51. </p>
  52. ## Install
  53. ### macOS App
  54. Download the `.dmg` from [Releases](https://github.com/varandrew/moor/releases), drag to Applications, done. The app embeds a Rust HTTP gateway in the desktop process — no pre-installed Node.js runtime required.
  55. ### Windows App
  56. Download the Windows installer from [Releases](https://github.com/varandrew/moor/releases) and run it. The app embeds a Rust HTTP gateway in the desktop process — no pre-installed Node.js runtime required.
  57. ### Linux App
  58. Download the `.deb`, `.rpm`, or `.AppImage` from [Releases](https://github.com/varandrew/moor/releases) (x86_64 and aarch64 builds are produced by CI). The app embeds a Rust HTTP gateway in the desktop process — no pre-installed Node.js runtime required. macOS remains the primary target; Linux builds are produced by CI but less extensively tested.
  59. ### Build from Source
  60. Requires macOS (Apple Silicon / Intel), Windows x64, or Linux (x86_64 / aarch64), Node.js >= 22 (CI uses 24), pnpm 11.3.0 (as pinned in `package.json`), and the stable Rust toolchain used by CI.
  61. ```bash
  62. git clone https://github.com/varandrew/moor.git
  63. cd moor
  64. pnpm install
  65. ```
  66. See [Development](#development) for build instructions.
  67. ## Quickstart
  68. ### Launch the App
  69. Open **Moor** from your applications menu (`Moor.app` on macOS). The Dashboard shows your active Profile, server status, and recent audit logs at a glance.
  70. ### Scan Existing Configs
  71. Moor can automatically detect MCP servers you've already configured for Claude Code, Claude Desktop, Codex, OpenCode, Cursor, Kimi Code, dsh, Grok Build, and Pi:
  72. 1. Go to **Servers** → **Import**
  73. 2. Click **Scan** — Moor reads `~/.claude.json`, `~/.codex/config.toml`, `~/.config/opencode/opencode.json` / `.jsonc`, `~/.cursor/mcp.json`, `~/.kimi-code/mcp.json`, `~/.dsh/cordis.patch.yml`, `~/Library/Application Support/Claude/claude_desktop_config.json`, `~/.grok/config.toml`, and `~/.pi/agent/mcp.json` (Pi needs the community adapter: `pi install npm:pi-mcp-adapter`)
  74. 3. Select the servers you want to import
  75. You can also paste a JSON MCP configuration with **Import JSON**. Moor imports stdio and HTTP/SSE servers, and reports unsupported entries such as OpenAPI configs without saving them.
  76. Start the imported servers from **Servers** so Moor can discover their tools. Enabling a server in a Profile controls exposure; it does not start the server.
  77. ### Create a Profile
  78. Profiles let you group servers and control which tools are exposed to Agents:
  79. 1. Go to **Profiles** → **New Profile**
  80. 2. Name it (e.g., "Coding", "Research")
  81. 3. Toggle servers on/off
  82. 4. Expand a server to enable/disable individual tools
  83. 5. Optionally choose **Curated listing** and select tools to pin; **Direct listing** is the default
  84. 6. Click **Activate** — the change is instant
  85. ### Connect Your Agent
  86. Point any MCP-compatible client to Moor's single endpoint:
  87. ```
  88. http://127.0.0.1:9223/mcp
  89. ```
  90. `9223` is the default gateway port. If it is already in use, Moor picks the next available port and shows the actual endpoint in the Dashboard and Client Config pages.
  91. By default the `/mcp` endpoint is loopback-only and does not require `X-Moor-Token` (see LAN access below). Moor uses `X-Moor-Token` only for local management APIs between the WebView and gateway, so you do not need to paste it into agent configs.
  92. To connect from WSL2 (NAT mode) or another LAN device, enable **Settings → Advanced → Allow LAN MCP Access** and restart Moor. The gateway then binds to all interfaces and `/mcp` additionally accepts private-network hosts (`10.x.x.x`, `172.16.x.x`–`172.31.x.x`, `192.168.x.x`); `/api/*` stays loopback-only and token-protected. Windows may prompt to allow Moor through the firewall.
  93. Moor handles the rest — aggregating `tools/list`, routing `tools/call`, and filtering based on your active Profile.
  94. ### Adjust MCP Timeouts
  95. If a stdio server starts through `npx`, `pnpm dlx`, or a package manager that downloads dependencies, its first `initialize` / `tools/list` may exceed the default 30 seconds. In **Settings → Advanced**, increase **Server Start Timeout** for startup or **Request Timeout** for running `tools/call` requests. Both settings accept 5–300 seconds.
  96. Preinstall frequently used servers and use absolute command paths to reduce startup delays. To start them when Moor launches, enable **Auto-start** on each server and **Auto-start Servers on Launch** in Settings; only servers enabled in the active Profile are started.
  97. ## Features
  98. ### MCP Gateway Aggregation
  99. A single HTTP endpoint (`/mcp`) proxies all backend MCP servers. Agents see a unified tool catalog — no need to configure multiple endpoints.
  100. ### Multi-Transport Support
  101. Connect to both **stdio** (subprocess) and **HTTP/SSE** MCP servers. Moor manages connections and server lifecycles, with optional periodic health checks.
  102. ### Profile Management
  103. Create unlimited Profiles for different workflows. Each Profile stores:
  104. - Which servers are enabled
  105. - Which tools are disabled per server
  106. - Which tools are pinned, the exposure mode, and the risk policy
  107. - A global active state
  108. Switch Profiles with **hot-swap** — connected Agents stay connected, and the next `tools/list` reflects the new configuration immediately.
  109. ### Tool-Level Toggles
  110. Beyond server-level on/off, drill into any server to disable specific tools. Disabled tools are excluded from the Agent's tool catalog and cannot be called.
  111. ### Curated Exposure and Pinned Tools
  112. **Direct listing** is the default for new and existing Profiles and lists every enabled, callable tool allowed by the Profile's policy. **Curated listing** lists only pinned tools plus two gateway meta tools:
  113. - `moor_search_tools`: search available tools by keyword and server name, with pagination and input schemas in the results
  114. - `moor_call_tool`: call a discovered tool by its exposed name and return the downstream result
  115. Use the Profile's pin controls to keep individual tools or a server's tools in the default catalog. Switching to Curated listing opens a picker for the initial pins. With no pinned tools, the catalog still contains the two meta tools. Unpinned tools remain searchable and callable, including by a previously cached exposed name; disabled or policy-blocked tools do not. You can switch back to Direct listing at any time.
  116. ### Tool Risk Policy
  117. Moor classifies tools as `safe`, `write`, `destructive`, or `unknown` using their names and descriptions. You can correct a classification on the server detail page.
  118. Each Profile defaults to **Advisory**, which displays risk without blocking calls. **Block destructive** removes tools classified as `destructive` from listings and search results, and refuses calls with error code `-32002` and a structured reason. The policy applies in both exposure modes and takes precedence over pins. It does not block `write` or `unknown` tools; the classification is a heuristic, not a guarantee of read-only access.
  119. ### Config Import
  120. One-click import from:
  121. - **Claude Code**: `~/.claude.json`
  122. - **Codex**: `~/.codex/config.toml`
  123. - **OpenCode**: `~/.config/opencode/opencode.json` / `.jsonc`
  124. - **Cursor**: `~/.cursor/mcp.json`
  125. - **Kimi Code**: `~/.kimi-code/mcp.json`
  126. - **dsh**: `~/.dsh/cordis.patch.yml`
  127. - **Claude Desktop**: `~/Library/Application Support/Claude/claude_desktop_config.json`
  128. - **Grok Build**: `~/.grok/config.toml`
  129. - **Pi**: `~/.pi/agent/mcp.json` (requires `pi install npm:pi-mcp-adapter`)
  130. Manual entry and pasted JSON batch import are also supported for stdio and HTTP/SSE servers.
  131. ### Client Configuration
  132. Generate ready-to-copy configuration snippets for Claude Code, Claude Desktop, Codex, OpenCode, Cursor, Kimi Code, dsh, Grok Build, and Pi. The snippets contain only the `/mcp` endpoint; Moor's `X-Moor-Token` is reserved for internal management API calls.
  133. ### Audit Logs
  134. With audit logging enabled (the default), tool calls are recorded with:
  135. - Timestamp, Profile, Server, Tool name
  136. - Arguments (with sensitive data redaction)
  137. - Result or error
  138. - Duration and Agent info
  139. - Call origin (`direct` or `meta`) and refusal reason when blocked
  140. Filter by time range, server, or tool. View aggregate statistics on the Dashboard and policy-blocked call counts in Insights. Audit logging can be disabled in **Settings → Advanced**. Logs are retained for 30 days by default; set `logRetentionDays` to `0` to keep them indefinitely.
  141. ### System Tray
  142. By default, closing the window hides Moor in the macOS menu bar or Windows system tray while the gateway keeps running. Disable **Minimize to Tray on Close** in Settings to quit on window close, or use **Quit Moor** in the tray menu. Quitting stops the gateway.
  143. ### Real-Time Status
  144. Server status changes and Profile switches are pushed to the UI via SSE. No refresh needed.
  145. MCP clients listening on `GET /mcp` receive `notifications/tools/list_changed` when the Profile, pins, risk policy, or tool catalog changes. Clients that handle this notification can fetch the updated catalog without reconnecting. Refresh tools on a running server from its detail page to repeat discovery without restarting the process.
  146. ## Architecture
  147. <details>
  148. <summary>Architecture Diagram</summary>
  149. ```
  150. Moor.app
  151. ├── UI Layer React + Vite + TypeScript + Tailwind CSS v4 + shadcn/ui
  152. ├── Desktop Layer Tauri 2 / Rust
  153. │ ├── Window management + tray icon
  154. │ └── In-process HTTP server (Axum)
  155. │ ├── MCP protocol gateway POST /mcp — init, tools/list, tools/call
  156. │ ├── Server management stdio spawn + HTTP/SSE client
  157. │ ├── Profile routing Global active Profile, hot-swap
  158. │ ├── Audit logging Tool call recording
  159. │ └── SSE push Real-time status sync to WebView
  160. └── Storage SQLite (rusqlite)
  161. ├── servers (configs, status)
  162. ├── profiles (server groups + tool toggles)
  163. └── audit_logs (tool calls, params, results, errors)
  164. ```
  165. </details>
  166. ### Communication Flow
  167. ```
  168. AI Agent ──HTTP──▶ POST /mcp ──▶ Moor Gateway ──stdio/HTTP──▶ MCP Servers
  169. │
  170. WebView ──IPC──▶ get_sidecar_info ─┐
  171. WebView ──env──▶ VITE_MOOR_API_URL/TOKEN ─┤ (fallback in browser dev mode)
  172. WebView ──fetch──▶ /api/* ─────────┘
  173. WebView ◀──SSE──── /api/events
  174. ```
  175. - **Runtime discovery**: WebView → Tauri IPC (`get_sidecar_info`) → Rust (port, token); in browser dev mode (`pnpm dev`) falls back to the `VITE_MOOR_API_URL` / `VITE_MOOR_API_TOKEN` env vars — see `src/lib/api/runtime.ts` (`GET /api/runtime` exists but is token-protected)
  176. - **Business operations**: WebView → HTTP `fetch()` → In-process Axum server (Rust)
  177. - **System operations**: WebView → Tauri IPC → Rust (tray, window, auto-start)
  178. ## Development
  179. ### Prerequisites
  180. - macOS (Apple Silicon / Intel), Windows x64, or Linux (x86_64 / aarch64)
  181. - [Node.js](https://nodejs.org) >= 22 (CI uses 24)
  182. - [pnpm](https://pnpm.io) 11.3.0 (pinned in `package.json`)
  183. - [Rust](https://rustup.rs) stable (the toolchain used by CI)
  184. - [Xcode Command Line Tools](https://developer.apple.com/xcode/resources/) on macOS
  185. ### Install Dependencies
  186. ```bash
  187. pnpm install
  188. ```
  189. ### Development Mode
  190. Start the full desktop app (Tauri, with the in-process Rust gateway):
  191. ```bash
  192. pnpm tauri dev
  193. ```
  194. - Frontend dev server: http://localhost:1420 (Vite HMR runs inside the WebView)
  195. ### Production Build
  196. ```bash
  197. pnpm tauri build
  198. ```
  199. Outputs:
  200. - macOS: `src-tauri/target/release/bundle/macos/Moor.app`
  201. - macOS DMG: `src-tauri/target/release/bundle/dmg/Moor_<version>_aarch64.dmg`
  202. - Windows: `src-tauri/target/release/bundle/nsis/Moor_<version>_x64-setup.exe`
  203. - Linux: `.deb` / `.rpm` / `.AppImage` under `src-tauri/target/release/bundle/` (x86_64 + aarch64, built by CI)
  204. ### Code Quality
  205. ```bash
  206. vp check # format + lint + type check
  207. vp lint # lint only
  208. vp lint --fix # auto-fix
  209. vp fmt # format
  210. ```
  211. ### Testing
  212. ```bash
  213. # Rust gateway tests
  214. cargo test --manifest-path src-tauri/Cargo.toml
  215. # Frontend + scripts tests
  216. vp test
  217. ```
  218. ## API
  219. Management endpoints under `/api/*` require a loopback Host and the `X-Moor-Token` header. The `/mcp` endpoint follows the loopback/LAN rules described above and does not require that token.
  220. ### MCP Gateway
  221. | Method | Path | Description |
  222. | ------ | ------ | --------------------------------------- |
  223. | `ALL` | `/mcp` | MCP protocol endpoint (Streamable HTTP) |
  224. ### Server Management
  225. | Method | Path | Description |
  226. | -------- | --------------------------------------- | ---------------------------------------------------------- |
  227. | `GET` | `/api/servers` | List all servers |
  228. | `POST` | `/api/servers` | Add server |
  229. | `GET` | `/api/servers/:id` | Server detail |
  230. | `PUT` | `/api/servers/:id` | Update server config |
  231. | `DELETE` | `/api/servers/:id` | Remove server |
  232. | `POST` | `/api/servers/:id/start` | Start server |
  233. | `POST` | `/api/servers/:id/stop` | Stop server |
  234. | `GET` | `/api/servers/:id/tools` | Get discovered tools (optionally filter by `?profile_id=`) |
  235. | `POST` | `/api/servers/:id/tools/refresh` | Rediscover tools on a running server without restarting it |
  236. | `PATCH` | `/api/servers/:id/tools/:toolName/risk` | Override a tool's `riskLevel` |
  237. | `PUT` | `/api/servers/order` | Reorder servers |
  238. ### Profile Management
  239. | Method | Path | Description |
  240. | -------- | ------------------------------------- | -------------------------------------------------------------------------------------- |
  241. | `GET` | `/api/profiles` | List all profiles |
  242. | `POST` | `/api/profiles` | Create profile |
  243. | `GET` | `/api/profiles/:id` | Get profile detail (with servers) |
  244. | `PUT` | `/api/profiles/:id` | Update name, `exposureMode`, `riskPolicy`, or `initialPins` when entering Curated mode |
  245. | `DELETE` | `/api/profiles/:id` | Delete profile |
  246. | `PUT` | `/api/profiles/:id/activate` | Set as active profile |
  247. | `POST` | `/api/profiles/:id/clone` | Clone a profile |
  248. | `GET` | `/api/profiles/:id/servers/:serverId` | Get server toggle, disabled tools, and pinned tools |
  249. | `PUT` | `/api/profiles/:id/servers/:serverId` | Update server toggle + disabled tools |
  250. | `PUT` | `/api/profiles/:id/servers-state` | Bulk update server toggles, `disabledTools`, and `pinnedTools` |
  251. | `GET` | `/api/profiles/:id/tools` | Profile tool groups with visibility, pin, and risk metadata |
  252. ### Audit Logs
  253. | Method | Path | Description |
  254. | ------ | -------------------- | ----------------------------- |
  255. | `GET` | `/api/logs` | Query logs (with filters) |
  256. | `GET` | `/api/logs/stats` | Aggregate statistics |
  257. | `GET` | `/api/logs/insights` | Tool-call governance insights |
  258. ### Settings Management
  259. | Method | Path | Description |
  260. | ------- | --------------------- | ----------------- |
  261. | `GET` | `/api/settings` | Get settings |
  262. | `PATCH` | `/api/settings` | Update settings |
  263. | `POST` | `/api/settings/reset` | Reset to defaults |
  264. ### Other
  265. | Method | Path | Description |
  266. | ------ | ---------------------- | ------------------------------- |
  267. | `GET` | `/api/health` | Health check |
  268. | `GET` | `/api/runtime` | Runtime info (port, URL) |
  269. | `GET` | `/api/events` | SSE real-time event stream |
  270. | `POST` | `/api/import/scan` | Scan local client configs |
  271. | `POST` | `/api/import/parse` | Preview pasted JSON import |
  272. | `POST` | `/api/import/execute` | Execute import |
  273. | `GET` | `/api/import/snippets` | Generate client config snippets |
  274. | `POST` | `/api/import/convert` | Convert configs between clients |
  275. ## Tech Stack
  276. | Layer | Technology |
  277. | ------------- | ------------------------------------------------------------------ |
  278. | Frontend | React 19, vite-plus, TypeScript 5.7, Tailwind CSS v4 |
  279. | UI Primitives | Radix UI |
  280. | UI Components | shadcn/ui (New York style) |
  281. | Desktop | Tauri 2 (Rust) |
  282. | Gateway | Rust, Axum, Tokio, rusqlite (in-process) |
  283. | Database | SQLite (rusqlite) |
  284. | MCP Protocol | Custom Rust implementation (JSON-RPC over Streamable HTTP / stdio) |
  285. | Icons | Lucide React |
  286. | Tooling | vite-plus (vp CLI), Oxlint, Oxfmt, Vitest |
  287. ## Acknowledgements
  288. Thanks to the [linuxdo](https://linux.do/) community for discussion, sharing, and feedback.
  289. ## ❤️ Sponsor
  290. [![ko-fi](https://ko-fi.com/img/githubbutton_sm.svg)](https://ko-fi.com/varandrew)
  291. ## 🌟 Star History
  292. [![Star History Chart](https://api.star-history.com/svg?repos=varandrew/moor&type=Date)](https://www.star-history.com/#varandrew/moor&Date)
  293. ## License
  294. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.