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.
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
Markdown
[](/listings/varandrew--moor)HTML
<a href="/listings/varandrew--moor"><img src="/api/listings/varandrew--moor/badge.svg" alt="findsafeskills safety rating" /></a>Install
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.
- <p align="center">
- <img src="src-tauri/icons/128x128.png" alt="Moor" width="128">
- </p>
- <h1 align="center">Moor</h1>
- <p align="center">
- <b>Local MCP Gateway Manager for AI Agents</b><br>
- Aggregate multiple MCP servers into a single endpoint, filter tools by Profile, and manage everything from a beautiful native UI.
- </p>
- <p align="center">
- <img src="https://img.shields.io/badge/license-MIT-blue" alt="License">
- <img src="https://img.shields.io/badge/React-19-61DAFB?logo=react" alt="React 19">
- <img src="https://img.shields.io/badge/Tauri-2-24C8D8?logo=tauri" alt="Tauri 2">
- <img src="https://img.shields.io/badge/Node.js-22+-339933?logo=nodedotjs" alt="Node.js 22+">
- <img src="https://img.shields.io/badge/platform-macOS-black?logo=apple" alt="macOS">
- <img src="https://img.shields.io/badge/platform-Windows-0078D4?logo=windows" alt="Windows">
- <img src="https://img.shields.io/badge/platform-Linux-FCC624?logo=linux&logoColor=black" alt="Linux">
- <img src="https://img.shields.io/badge/pnpm-11+-F69220?logo=pnpm" alt="pnpm">
- </p>
- <p align="center">
- <a href="#install">Install</a> ·
- <a href="#quickstart">Quickstart</a> ·
- <a href="#features">Features</a> ·
- <a href="#architecture">Architecture</a> ·
- <a href="#development">Development</a> ·
- <a href="#api">API</a>
- </p>
- <!-- README-I18N:START -->
- **English** | [汉语](./README.zh.md) | [日本語](./README.ja.md) | [Español](./README.es.md)
- <!-- README-I18N:END -->
- ---
- > [!NOTE]
- > 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.
- > _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._
- >
- > _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._
- <p align="center">
- <img src="./assets/Dashboard%20Page.png" alt="Dashboard" width="800"><br>
- <sub>Dashboard — Overview of active Profile, server status, and audit stats.</sub>
- </p>
- <p align="center">
- <img src="./assets/Servers%20Page.png" alt="Servers" width="800"><br>
- <sub>Servers — Manage MCP servers, import configs, monitor health.</sub>
- </p>
- <p align="center">
- <img src="./assets/Profiles%20Page.png" alt="Profiles" width="800"><br>
- <sub>Profiles — Create profiles, toggle servers, enable/disable tools.</sub>
- </p>
- <p align="center">
- <img src="./assets/Audit%20Page.png" alt="Audit" width="800"><br>
- <sub>Audit — Inspect every tool call with full context and filters.</sub>
- </p>
- ## Install
- ### macOS App
- 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.
- ### Windows App
- 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.
- ### 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 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.
- ### Build from Source
- 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.
- ```bash
- git clone https://github.com/varandrew/moor.git
- cd moor
- pnpm install
- ```
- See [Development](#development) for build instructions.
- ## Quickstart
- ### Launch the App
- 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.
- ### Scan Existing Configs
- 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:
- 1. Go to **Servers** → **Import**
- 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`)
- 3. Select the servers you want to import
- 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.
- 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.
- ### Create a Profile
- Profiles let you group servers and control which tools are exposed to Agents:
- 1. Go to **Profiles** → **New Profile**
- 2. Name it (e.g., "Coding", "Research")
- 3. Toggle servers on/off
- 4. Expand a server to enable/disable individual tools
- 5. Optionally choose **Curated listing** and select tools to pin; **Direct listing** is the default
- 6. Click **Activate** — the change is instant
- ### Connect Your Agent
- Point any MCP-compatible client to Moor's single endpoint:
- ```
- http://127.0.0.1:9223/mcp
- ```
- `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.
- 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.
- 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.
- Moor handles the rest — aggregating `tools/list`, routing `tools/call`, and filtering based on your active Profile.
- ### Adjust MCP Timeouts
- 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.
- 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.
- ## Features
- ### MCP Gateway Aggregation
- A single HTTP endpoint (`/mcp`) proxies all backend MCP servers. Agents see a unified tool catalog — no need to configure multiple endpoints.
- ### Multi-Transport Support
- Connect to both **stdio** (subprocess) and **HTTP/SSE** MCP servers. Moor manages connections and server lifecycles, with optional periodic health checks.
- ### Profile Management
- Create unlimited Profiles for different workflows. Each Profile stores:
- - Which servers are enabled
- - Which tools are disabled per server
- - Which tools are pinned, the exposure mode, and the risk policy
- - A global active state
- Switch Profiles with **hot-swap** — connected Agents stay connected, and the next `tools/list` reflects the new configuration immediately.
- ### Tool-Level Toggles
- 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.
- ### Curated Exposure and Pinned Tools
- **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:
- - `moor_search_tools`: search available tools by keyword and server name, with pagination and input schemas in the results
- - `moor_call_tool`: call a discovered tool by its exposed name and return the downstream result
- 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.
- ### Tool Risk Policy
- Moor classifies tools as `safe`, `write`, `destructive`, or `unknown` using their names and descriptions. You can correct a classification on the server detail page.
- 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.
- ### Config Import
- One-click import from:
- - **Claude Code**: `~/.claude.json`
- - **Codex**: `~/.codex/config.toml`
- - **OpenCode**: `~/.config/opencode/opencode.json` / `.jsonc`
- - **Cursor**: `~/.cursor/mcp.json`
- - **Kimi Code**: `~/.kimi-code/mcp.json`
- - **dsh**: `~/.dsh/cordis.patch.yml`
- - **Claude Desktop**: `~/Library/Application Support/Claude/claude_desktop_config.json`
- - **Grok Build**: `~/.grok/config.toml`
- - **Pi**: `~/.pi/agent/mcp.json` (requires `pi install npm:pi-mcp-adapter`)
- Manual entry and pasted JSON batch import are also supported for stdio and HTTP/SSE servers.
- ### Client Configuration
- 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.
- ### Audit Logs
- With audit logging enabled (the default), tool calls are recorded with:
- - Timestamp, Profile, Server, Tool name
- - Arguments (with sensitive data redaction)
- - Result or error
- - Duration and Agent info
- - Call origin (`direct` or `meta`) and refusal reason when blocked
- 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.
- ### System Tray
- 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.
- ### Real-Time Status
- Server status changes and Profile switches are pushed to the UI via SSE. No refresh needed.
- 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.
- ## Architecture
- <details>
- <summary>Architecture Diagram</summary>
- ```
- Moor.app
- ├── UI Layer React + Vite + TypeScript + Tailwind CSS v4 + shadcn/ui
- ├── Desktop Layer Tauri 2 / Rust
- │ ├── Window management + tray icon
- │ └── In-process HTTP server (Axum)
- │ ├── MCP protocol gateway POST /mcp — init, tools/list, tools/call
- │ ├── Server management stdio spawn + HTTP/SSE client
- │ ├── Profile routing Global active Profile, hot-swap
- │ ├── Audit logging Tool call recording
- │ └── SSE push Real-time status sync to WebView
- └── Storage SQLite (rusqlite)
- ├── servers (configs, status)
- ├── profiles (server groups + tool toggles)
- └── audit_logs (tool calls, params, results, errors)
- ```
- </details>
- ### Communication Flow
- ```
- AI Agent ──HTTP──▶ POST /mcp ──▶ Moor Gateway ──stdio/HTTP──▶ MCP Servers
- │
- WebView ──IPC──▶ get_sidecar_info ─┐
- WebView ──env──▶ VITE_MOOR_API_URL/TOKEN ─┤ (fallback in browser dev mode)
- WebView ──fetch──▶ /api/* ─────────┘
- WebView ◀──SSE──── /api/events
- ```
- - **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)
- - **Business operations**: WebView → HTTP `fetch()` → In-process Axum server (Rust)
- - **System operations**: WebView → Tauri IPC → Rust (tray, window, auto-start)
- ## Development
- ### Prerequisites
- - macOS (Apple Silicon / Intel), Windows x64, or Linux (x86_64 / aarch64)
- - [Node.js](https://nodejs.org) >= 22 (CI uses 24)
- - [pnpm](https://pnpm.io) 11.3.0 (pinned in `package.json`)
- - [Rust](https://rustup.rs) stable (the toolchain used by CI)
- - [Xcode Command Line Tools](https://developer.apple.com/xcode/resources/) on macOS
- ### Install Dependencies
- ```bash
- pnpm install
- ```
- ### Development Mode
- Start the full desktop app (Tauri, with the in-process Rust gateway):
- ```bash
- pnpm tauri dev
- ```
- - Frontend dev server: http://localhost:1420 (Vite HMR runs inside the WebView)
- ### Production Build
- ```bash
- pnpm tauri build
- ```
- Outputs:
- - macOS: `src-tauri/target/release/bundle/macos/Moor.app`
- - macOS DMG: `src-tauri/target/release/bundle/dmg/Moor_<version>_aarch64.dmg`
- - Windows: `src-tauri/target/release/bundle/nsis/Moor_<version>_x64-setup.exe`
- - Linux: `.deb` / `.rpm` / `.AppImage` under `src-tauri/target/release/bundle/` (x86_64 + aarch64, built by CI)
- ### Code Quality
- ```bash
- vp check # format + lint + type check
- vp lint # lint only
- vp lint --fix # auto-fix
- vp fmt # format
- ```
- ### Testing
- ```bash
- # Rust gateway tests
- cargo test --manifest-path src-tauri/Cargo.toml
- # Frontend + scripts tests
- vp test
- ```
- ## API
- 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.
- ### MCP Gateway
- | Method | Path | Description |
- | ------ | ------ | --------------------------------------- |
- | `ALL` | `/mcp` | MCP protocol endpoint (Streamable HTTP) |
- ### Server Management
- | Method | Path | Description |
- | -------- | --------------------------------------- | ---------------------------------------------------------- |
- | `GET` | `/api/servers` | List all servers |
- | `POST` | `/api/servers` | Add server |
- | `GET` | `/api/servers/:id` | Server detail |
- | `PUT` | `/api/servers/:id` | Update server config |
- | `DELETE` | `/api/servers/:id` | Remove server |
- | `POST` | `/api/servers/:id/start` | Start server |
- | `POST` | `/api/servers/:id/stop` | Stop server |
- | `GET` | `/api/servers/:id/tools` | Get discovered tools (optionally filter by `?profile_id=`) |
- | `POST` | `/api/servers/:id/tools/refresh` | Rediscover tools on a running server without restarting it |
- | `PATCH` | `/api/servers/:id/tools/:toolName/risk` | Override a tool's `riskLevel` |
- | `PUT` | `/api/servers/order` | Reorder servers |
- ### Profile Management
- | Method | Path | Description |
- | -------- | ------------------------------------- | -------------------------------------------------------------------------------------- |
- | `GET` | `/api/profiles` | List all profiles |
- | `POST` | `/api/profiles` | Create profile |
- | `GET` | `/api/profiles/:id` | Get profile detail (with servers) |
- | `PUT` | `/api/profiles/:id` | Update name, `exposureMode`, `riskPolicy`, or `initialPins` when entering Curated mode |
- | `DELETE` | `/api/profiles/:id` | Delete profile |
- | `PUT` | `/api/profiles/:id/activate` | Set as active profile |
- | `POST` | `/api/profiles/:id/clone` | Clone a profile |
- | `GET` | `/api/profiles/:id/servers/:serverId` | Get server toggle, disabled tools, and pinned tools |
- | `PUT` | `/api/profiles/:id/servers/:serverId` | Update server toggle + disabled tools |
- | `PUT` | `/api/profiles/:id/servers-state` | Bulk update server toggles, `disabledTools`, and `pinnedTools` |
- | `GET` | `/api/profiles/:id/tools` | Profile tool groups with visibility, pin, and risk metadata |
- ### Audit Logs
- | Method | Path | Description |
- | ------ | -------------------- | ----------------------------- |
- | `GET` | `/api/logs` | Query logs (with filters) |
- | `GET` | `/api/logs/stats` | Aggregate statistics |
- | `GET` | `/api/logs/insights` | Tool-call governance insights |
- ### Settings Management
- | Method | Path | Description |
- | ------- | --------------------- | ----------------- |
- | `GET` | `/api/settings` | Get settings |
- | `PATCH` | `/api/settings` | Update settings |
- | `POST` | `/api/settings/reset` | Reset to defaults |
- ### Other
- | Method | Path | Description |
- | ------ | ---------------------- | ------------------------------- |
- | `GET` | `/api/health` | Health check |
- | `GET` | `/api/runtime` | Runtime info (port, URL) |
- | `GET` | `/api/events` | SSE real-time event stream |
- | `POST` | `/api/import/scan` | Scan local client configs |
- | `POST` | `/api/import/parse` | Preview pasted JSON import |
- | `POST` | `/api/import/execute` | Execute import |
- | `GET` | `/api/import/snippets` | Generate client config snippets |
- | `POST` | `/api/import/convert` | Convert configs between clients |
- ## Tech Stack
- | Layer | Technology |
- | ------------- | ------------------------------------------------------------------ |
- | Frontend | React 19, vite-plus, TypeScript 5.7, Tailwind CSS v4 |
- | UI Primitives | Radix UI |
- | UI Components | shadcn/ui (New York style) |
- | Desktop | Tauri 2 (Rust) |
- | Gateway | Rust, Axum, Tokio, rusqlite (in-process) |
- | Database | SQLite (rusqlite) |
- | MCP Protocol | Custom Rust implementation (JSON-RPC over Streamable HTTP / stdio) |
- | Icons | Lucide React |
- | Tooling | vite-plus (vp CLI), Oxlint, Oxfmt, Vitest |
- ## Acknowledgements
- Thanks to the [linuxdo](https://linux.do/) community for discussion, sharing, and feedback.
- ## ❤️ Sponsor
- [](https://ko-fi.com/varandrew)
- ## 🌟 Star History
- [](https://www.star-history.com/#varandrew/moor&Date)
- ## License
- [MIT](LICENSE)
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.