Skip to content
Back to search

nuphus-mcp

Desktop automation MCP server — computer use for any AI agent: control screen, windows, mouse/keyboard, and Chrome via Model Context Protocol (stdio). Not a DSH plugin — DSH users install dsh-nuphus-mcp.

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/mrpulor-gh/nuphus-mcp 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/mrpulor-gh/nuphus-mcp'

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/mrpulor-gh--nuphus-mcp/badge.svg)](/listings/mrpulor-gh--nuphus-mcp)

HTML

<a href="/listings/mrpulor-gh--nuphus-mcp"><img src="/api/listings/mrpulor-gh--nuphus-mcp/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.

**Install via npm (recommended — all platforms, prebuilt binaries):**

npm install -g @nuphus/nuphus-mcp

The `nuphus-mcp` meta package installs the prebuilt binary for your platform automatically (Windows x64/arm64, macOS arm64, Linux x64/arm64) and puts the `nuphus-mcp` command on your PATH. No Rust toolchain needed:

nuphus-mcp   # stdio MCP server

**Build from source** (requires the Rust toolchain):

cargo build --release -p nuphus-mcp
# binary at target/release/nuphus-mcp(.exe)

The server reads newline-delimited JSON from stdin and writes JSON-RPC responses to stdout. Logs go to stderr.

# quick smoke test
echo '{"jsonrpc":"2.0","id":0,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test"}}}' | nuphus-mcp

🔒 Recommended: enable strict confirmation

This server can physically control the machine it runs on. By default write tools run **without** confirmation; we strongly recommend enabling strict confirmation so destructive operations require an explicit `"confirm": true` argument from the client (otherwise the tool is rejected with `isError`).

**Any one of the following:**

# CLI flag
nuphus-mcp --confirm-write

# Environment variable (recommended — survives across clients, keeps config simple)
export NUPHUS_MCP_CONFIRM_WRITE=1      # macOS / Linux
setx NUPHUS_MCP_CONFIRM_WRITE 1        # Windows (persistent for new shells)

# MCP client args
"args": ["--confirm-write"]

**Claude Desktop** — recommended `claude_desktop_config.json`:

{
  "mcpServers": {
    "nuphus-mcp": {
      "command": "nuphus-mcp",
      "args": ["--confirm-write"]
    }
  }
}

> Prefer the environment variable: one setting applies to every MCP client on > the machine. See [SECURITY.md](SECURITY.md) and the [Safety Annotations > section of TOOLS.md](TOOLS.md#safety-annotations) for the full threat model.

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 · 411 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. # nuphus-mcp
  2. [![npm version](https://img.shields.io/npm/v/@nuphus/nuphus-mcp.svg)](https://www.npmjs.com/package/@nuphus/nuphus-mcp) [![npm downloads](https://img.shields.io/npm/dm/@nuphus/nuphus-mcp.svg)](https://www.npmjs.com/package/@nuphus/nuphus-mcp) [![GitHub stars](https://img.shields.io/github/stars/mrpulor-gh/nuphus-mcp.svg)](https://github.com/mrpulor-gh/nuphus-mcp) [![License: MIT](https://img.shields.io/github/license/mrpulor-gh/nuphus-mcp.svg)](LICENSE) [![CI](https://github.com/mrpulor-gh/nuphus-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/mrpulor-gh/nuphus-mcp/actions/workflows/ci.yml)
  3. **Desktop automation MCP server — computer use for any AI agent. See the screen, control windows/mouse/keyboard, and drive Chrome over the Model Context Protocol (stdio). Desktop & browser automation need no API key; OCR runs locally; vision plugs into your own vision LLM (OpenAI-compatible or Anthropic native, BYOK).**
  4. `nuphus-mcp` is a lightweight, cross-platform **desktop automation MCP server**
  5. that exposes desktop + browser automation as standard MCP tools. It speaks
  6. JSON-RPC 2.0 over stdio — no daemon, no network service, one binary. Claude
  7. Desktop, Cursor, VS Code, Copilot, or any MCP client can connect and
  8. immediately control the screen, windows, keyboard/mouse, and Chrome —
  9. **computer use for any AI agent** — desktop & browser automation need no API
  10. key; local OCR is built in; vision works with your own vision LLM
  11. (OpenAI-compatible, BYOK).
  12. > **🇨🇳 Mainland China mirror**: this repo is mirrored on
  13. > [Gitee](https://gitee.com/nuphus/nuphus-mcp) for fast in-China access
  14. > (Chinese docs served by default there). [中文文档](README.zh-CN.md)
  15. >
  16. > **Part of the Nuphus ecosystem**: [Nuphus](https://github.com/mrpulor-gh/nuphus) — a local-first AI agent with real desktop execution and dual-device (phone-as-second-screen) sync. nuphus-mcp exposes the same desktop + browser automation to any MCP client.
  17. >
  18. > **Using DeepSeek Harness (DSH)?** nuphus-mcp itself is a plain stdio MCP server — **not** a DSH/Cordis plugin. Install the dedicated [dsh-nuphus-mcp](https://github.com/mrpulor-gh/dsh-nuphus-mcp) plugin instead (see [DeepSeek Harness (DSH)](#deepseek-harness-dsh)).
  19. ```
  20. ┌──────────────────┐ stdio JSON-RPC ┌──────────────────────┐
  21. │ Any MCP Client │ ───────────────► │ nuphus-mcp │
  22. │ (Claude/Cursor/ │ ◄─────────────── │ desktop-api crate │──► screen/window/mouse/keyboard
  23. │ Nuphus itself) │ single-line JSON │ nuphus-browser crate│──► Chrome (CDP)
  24. └──────────────────┘ └──────────────────────┘
  25. ```
  26. ## Features
  27. - **45 MCP tools** (22 desktop + 23 browser) — screenshots, window control,
  28. mouse/keyboard, Chrome CDP automation, and more — see [TOOLS.md](TOOLS.md) /
  29. [TOOLS.zh-CN.md](TOOLS.zh-CN.md) for the full reference.
  30. - **Desktop automation**: screen size, screenshot (PNG/base64), window list,
  31. window activate/screenshot/move/resize/info, mouse click/drag/scroll/position,
  32. keyboard input/hotkey, clipboard write/clean — implemented on the
  33. `desktop-api` crate (xcap + Win32, no Tauri dependency).
  34. - **Semantic desktop (Accessibility/UIA)** — 7 tools that drive native UI through
  35. the platform accessibility tree instead of pixel coordinates:
  36. `desktop_targets_list`, `desktop_target_bind`, `desktop_semantic_observe`,
  37. `desktop_semantic_candidate`, `desktop_semantic_execute`,
  38. `desktop_semantic_action`, `desktop_verify_state`. One contract —
  39. **observe → pick a candidate → execute → verify** — where native window
  40. handles, coordinates and platform locators never cross the MCP boundary; the
  41. caller only sees opaque ids and stable semantic locators. Backed by Windows UIA
  42. and the macOS Accessibility (AX) API.
  43. - **Computer vision pair**: `desktop_vision` (BYOK — send a screenshot to your
  44. own vision model via an OpenAI-compatible or Anthropic native API) +
  45. `desktop_perceive` (local OCR with PaddleOCR, models auto-downloaded on first
  46. run; optional YOLO icon detection). Used together they give AI agents **both
  47. semantic understanding
  48. and pixel-precise coordinates** — the battle-tested vision→perceive flow from
  49. the Nuphus desktop app. See [TOOLS.md](TOOLS.md) for BYOK env vars, model
  50. setup, and the recommended flow.
  51. - **Browser automation**: navigate, snapshot (accessibility tree with `@N`
  52. refs), click, type, exec, scroll, extract, screenshot, evaluate,
  53. back/forward, wait_for, cookies get/set/import, upload, tabs, downloads —
  54. implemented on `nuphus-browser` (chromiumoxide CDP).
  55. - **Zero-cost stdio**: no HTTP server, no daemon. The process reads
  56. single-line JSON from stdin and writes responses to stdout.
  57. - **Safety-first**: destructive tools are annotated per the MCP spec; optional
  58. strict-confirm mode; path validation for screenshots, uploads, and file drags.
  59. ## Repository Layout
  60. ```
  61. nuphus-mcp/
  62. ├── Cargo.toml # workspace root
  63. ├── TOOLS.md / TOOLS.zh-CN.md # 45-tool reference
  64. ├── crates/
  65. │ ├── nuphus-mcp/ # MCP Server (this repo's product)
  66. │ ├── nuphus-browser/ # Browser automation core (CDP)
  67. │ └── desktop-api/ # Desktop control core (vendored)
  68. └── ...
  69. ```
  70. ## Prerequisites
  71. - **Rust toolchain** (stable) — build from source with Cargo.
  72. - **Chrome or Edge** — required for browser tools. The server auto-detects an
  73. installed browser; if none is found, `browser_*` tools return a clear error.
  74. - **Windows recommended** for full desktop control — see Platform Support below.
  75. ## Platform Support
  76. | Platform | Browser tools | Desktop tools |
  77. |----------|---------------|---------------|
  78. | Windows | Full | Full (Win32 API) |
  79. | macOS | Full | Semantic (AX) + mouse/keyboard (Accessibility permission required) |
  80. | Linux | Available | Partial — window/input capabilities are limited |
  81. > **Execution HUD**: non-intrusive execution feedback on every platform — Windows shows a compact status card anchored to the bottom-right of the work area, clear of the taskbar/tray (start / done / fail, real-time, styled after the main app HUD), macOS/Linux post a **system notification** on completion (`NUPHUS_MCP_HUD=off` to disable). Window activation is never used as a visibility fallback.
  82. ## API Keys & Local Models
  83. ### Vision — BYOK, OpenAI-compatible or Anthropic native
  84. `desktop_vision` uses **your own** vision model. It speaks two protocols:
  85. - **OpenAI-compatible** Chat Completions (default) — works with OpenAI, MiniMax, Qwen, Ollama, vLLM, …
  86. - **Anthropic native** Messages API — point `NUPHUS_MCP_VISION_BASE_URL` at
  87. `https://api.anthropic.com/v1` and the protocol is auto-detected from the host;
  88. or force it with `NUPHUS_MCP_VISION_PROVIDER=anthropic`.
  89. Nothing is required unless you call this tool — and when it is not configured
  90. the tool returns a clear error instead of silently failing.
  91. | Environment variable | Required | Default | Description |
  92. |----------------------|----------|---------|-------------|
  93. | `NUPHUS_MCP_VISION_API_KEY` | ✅ | — | API key for your vision model |
  94. | `NUPHUS_MCP_VISION_BASE_URL` | — | `https://api.openai.com/v1` | Base URL (`https://api.anthropic.com/v1` for Claude) |
  95. | `NUPHUS_MCP_VISION_MODEL` | ✅ | — | Model id, e.g. `gpt-4o-mini`, `qwen-vl-max`, `claude-sonnet-4-5` |
  96. | `NUPHUS_MCP_VISION_PROVIDER` | — | `auto` | `auto` \| `openai` \| `anthropic`; `auto` infers from the base URL host |
  97. | `NUPHUS_MCP_VISION_MAX_TOKENS` | — | `1024` | Max output tokens (Zhipu GLM-4V-Flash caps at 1024; raise for text-heavy screenshots) |
  98. ### External browser (anti-detect / fingerprint browsers)
  99. By default `browser_*` tools launch and manage their own Chrome instance. To
  100. drive an **external browser** instead — e.g. an anti-detect / fingerprint
  101. browser — start it with a debugging port and point the server at it:
  102. | Environment variable | Required | Default | Description |
  103. |----------------------|----------|---------|-------------|
  104. | `NUPHUS_MCP_BROWSER_CDP_URL` | — | — | External CDP endpoint, e.g. `http://127.0.0.1:9222` |
  105. ```sh
  106. # Example: start your fingerprint browser with a debugging port
  107. chrome --remote-debugging-port=9222 --user-data-dir=...
  108. ```
  109. ```jsonc
  110. // MCP client config
  111. "env": { "NUPHUS_MCP_BROWSER_CDP_URL": "http://127.0.0.1:9222" }
  112. ```
  113. When set, `browser_*` tools attach to that endpoint and never launch a managed
  114. Chrome; attach failures are hard errors (no silent fallback into the wrong
  115. browser). The external browser belongs to you — the server never kills it on
  116. exit.
  117. #### Self-healing on window reopen (recommended)
  118. Fingerprint browsers typically get a **new random debug port every time a
  119. window is reopened**, which would leave a fixed `..._CDP_URL` pointing at a
  120. dead port. Provide the browser identity and the server re-resolves the live
  121. port automatically on the next tool call:
  122. | Environment variable | Required | Default | Description |
  123. |----------------------|----------|---------|-------------|
  124. | `NUPHUS_BROWSER_EXE_PATH` | for self-healing | — | Absolute path to the browser exe — the identity key used to locate the running window process |
  125. | `NUPHUS_BROWSER_NAME` | — | `指纹浏览器` | Display name used in error guidance |
  126. | `NUPHUS_BROWSER_USER_DATA_DIR` | — | — | Profile dir, used to read `DevToolsActivePort` when the window was started with a random port (`--remote-debugging-port=0`) and the process cmdline does not reveal it |
  127. ```jsonc
  128. // MCP client config — attach + self-heal
  129. "env": {
  130. "NUPHUS_MCP_BROWSER_CDP_URL": "http://127.0.0.1:9222",
  131. "NUPHUS_BROWSER_EXE_PATH": "C:\\path\\to\\fingerprint-browser.exe",
  132. "NUPHUS_BROWSER_NAME": "AdsPower",
  133. "NUPHUS_BROWSER_USER_DATA_DIR": "C:\\path\\to\\profile"
  134. }
  135. ```
  136. With the identity set, if the configured endpoint stops answering the server
  137. locates the window process by exe path, re-resolves its actual port (literal
  138. cmdline port, or `DevToolsActivePort` in the profile dir for random-port
  139. launches), verifies the candidate with a proxy-bypassing CDP probe and retries
  140. once — close and reopen the window and the next tool call just works. Without
  141. an identity, attach failures stay hard errors asking you to update the
  142. configured URL. Either way there is **no fallback to a managed Chrome**.
  143. ### Keeping logins: drive a browser that has your extensions & sessions
  144. Want `browser_*` tools to drive a browser carrying your own extensions /
  145. bookmarks / login state? First, a **hard Chrome 136+ restriction**: after
  146. Chrome's official security change, `--remote-debugging-port` and
  147. `--remote-debugging-pipe` are **ignored against the default user data
  148. directory** — they must be paired with `--user-data-dir` pointing at a
  149. non-default directory. This is a deliberate design to stop infostealer malware
  150. from reading real cookies through the local debugging port — **not a
  151. nuphus-mcp defect**, and no flag / registry policy can bypass it
  152. (`RemoteDebuggingAllowed` only allows/disallows the switches; it cannot
  153. re-enable them on the default directory).
  154. So "real default profile + CDP-controllable" are mutually exclusive since
  155. 136+. Pick one of the following, in priority order:
  156. **Option A (recommended, simplest): log in once in the nuphus-managed profile**
  157. nuphus-mcp manages its own Chrome instance by default (a dedicated
  158. `--user-data-dir`, always debuggable). Open it, log into the sites you want to
  159. stay signed in once — the state persists to that profile and every subsequent
  160. `browser_*` call carries those sessions. Zero config, zero copying.
  161. **Option B: copy your real profile to a debuggable directory (keeps
  162. extensions / bookmarks / logins)**
  163. When you need the original browser's extensions and login state, copy the real
  164. profile and launch from the copy:
  165. 1. **Quit** your running Chrome / Edge entirely first (profile-lock conflict)
  166. 2. Copy the profile to a non-default dir:
  167. - Windows: `copy "%LOCALAPPDATA%\Google\Chrome\User Data\Default" <dest>\Default`
  168. - macOS: `cp -R ~/Library/"Application Support"/Google/Chrome/Default <dest>/Default`
  169. - Linux: `cp -R ~/.config/google-chrome/Default <dest>/Default`
  170. 3. Launch the copy with a debug port: `chrome --remote-debugging-port=9222 --user-data-dir=<dest>`
  171. 4. Attach as an external browser: `NUPHUS_MCP_BROWSER_CDP_URL=http://127.0.0.1:9222`
  172. (add `NUPHUS_BROWSER_EXE_PATH` / `NUPHUS_BROWSER_USER_DATA_DIR` for port self-healing)
  173. Notes: on Windows, cookies / passwords are DPAPI user-level encrypted and
  174. decrypt fine from the copy under the same user — login state mostly survives;
  175. on macOS some credentials live in Keychain and a few sites may ask to log in
  176. again. The copy can be hundreds of MB to GBs, and it cannot run at the same
  177. time as the real browser.
  178. **Option C: desktop visual automation — operate the actually-running browser
  179. window**
  180. To operate the user's **currently running** real browser (DOM-level is not
  181. possible), use the desktop OCR + mouse/keyboard chain
  182. (`desktop_perceive` / `desktop_*` tools) — visually click, type and read the
  183. screen without CDP, at the cost of no DOM access and no login-state injection.
  184. ### Perceive models (local, auto-downloaded)
  185. `desktop_perceive` runs PaddleOCR and YOLO icon detection locally with ONNX
  186. Runtime. The first call downloads the OCR models and `icon_detect.onnx` together
  187. automatically into `%APPDATA%\Nuphus\models` (or `NUPHUS_MODELS_DIR`). Download
  188. failures return a clear error with manual instructions. YOLO is optional at
  189. runtime: if its download fails, perceive still returns OCR elements and reports
  190. `yolo_available: false` (use `NUPHUS_MCP_YOLO_MODEL_URL` for a custom source).
  191. See [TOOLS.md → Vision & Local Models](TOOLS.md#vision--local-models).
  192. All other tools need no API key.
  193. ## Install & Run
  194. **Install via npm (recommended — all platforms, prebuilt binaries):**
  195. ```sh
  196. npm install -g @nuphus/nuphus-mcp
  197. ```
  198. The `nuphus-mcp` meta package installs the prebuilt binary for your platform
  199. automatically (Windows x64/arm64, macOS arm64, Linux x64/arm64) and puts the
  200. `nuphus-mcp` command on your PATH. No Rust toolchain needed:
  201. ```sh
  202. nuphus-mcp # stdio MCP server
  203. ```
  204. **Build from source** (requires the Rust toolchain):
  205. ```sh
  206. cargo build --release -p nuphus-mcp
  207. # binary at target/release/nuphus-mcp(.exe)
  208. ```
  209. The server reads newline-delimited JSON from stdin and writes JSON-RPC
  210. responses to stdout. Logs go to stderr.
  211. ```sh
  212. # quick smoke test
  213. echo '{"jsonrpc":"2.0","id":0,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test"}}}' | nuphus-mcp
  214. ```
  215. ### 🔒 Recommended: enable strict confirmation
  216. This server can physically control the machine it runs on. By default write
  217. tools run **without** confirmation; we strongly recommend enabling strict
  218. confirmation so destructive operations require an explicit `"confirm": true`
  219. argument from the client (otherwise the tool is rejected with `isError`).
  220. **Any one of the following:**
  221. ```sh
  222. # CLI flag
  223. nuphus-mcp --confirm-write
  224. # Environment variable (recommended — survives across clients, keeps config simple)
  225. export NUPHUS_MCP_CONFIRM_WRITE=1 # macOS / Linux
  226. setx NUPHUS_MCP_CONFIRM_WRITE 1 # Windows (persistent for new shells)
  227. # MCP client args
  228. "args": ["--confirm-write"]
  229. ```
  230. **Claude Desktop** — recommended `claude_desktop_config.json`:
  231. ```json
  232. {
  233. "mcpServers": {
  234. "nuphus-mcp": {
  235. "command": "nuphus-mcp",
  236. "args": ["--confirm-write"]
  237. }
  238. }
  239. }
  240. ```
  241. > Prefer the environment variable: one setting applies to every MCP client on
  242. > the machine. See [SECURITY.md](SECURITY.md) and the [Safety Annotations
  243. > section of TOOLS.md](TOOLS.md#safety-annotations) for the full threat model.
  244. ## MCP Client Configuration
  245. Point any MCP client at `nuphus-mcp`. After `npm install -g
  246. @nuphus/nuphus-mcp` the command is on your PATH; otherwise use the absolute
  247. path to the binary (`nuphus-mcp` / `nuphus-mcp.exe`).
  248. **Claude Desktop** — `claude_desktop_config.json`:
  249. ```json
  250. {
  251. "mcpServers": {
  252. "nuphus-mcp": {
  253. "command": "nuphus-mcp",
  254. "args": []
  255. }
  256. }
  257. }
  258. ```
  259. **Any MCP client** (generic mcpServers JSON):
  260. ```json
  261. {
  262. "mcpServers": {
  263. "nuphus-mcp": {
  264. "command": "nuphus-mcp",
  265. "args": [],
  266. "env": {}
  267. }
  268. }
  269. }
  270. ```
  271. Supported MCP methods: `initialize`, `notifications/initialized`, `ping`,
  272. `tools/list`, `tools/call`.
  273. ## DeepSeek Harness (DSH)
  274. **Recommended — install the official
  275. [dsh-nuphus-mcp](https://github.com/mrpulor-gh/dsh-nuphus-mcp) plugin** (Gitee
  276. mirror: [gitee.com/nuphus/dsh-nuphus-mcp](https://gitee.com/nuphus/dsh-nuphus-mcp)).
  277. It mounts nuphus-mcp into DSH as native tools with zero config —
  278. `--confirm-write` on by default, no code change needed:
  279. ```sh
  280. npx -p @deepseek-ai/dsh dsh plugin --profile web add github:mrpulor-gh/dsh-nuphus-mcp
  281. ```
  282. **Manual alternative** — plug into
  283. [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) as a plain
  284. stdio MCP server via its built-in MCP client (`@deepseek-ai/dsh-mcp-client`).
  285. Mount in DSH's `cordis.yml` / patch:
  286. ```yaml
  287. - id: nuphus-mcp
  288. name: '@deepseek-ai/dsh-mcp-client'
  289. config:
  290. serverName: nuphus-mcp
  291. transport: stdio
  292. command: nuphus-mcp
  293. args: ["--confirm-write"]
  294. toolCallTimeoutMs: 120000 # DSH default 60000 is too low for screenshots/OCR
  295. ```
  296. Tools register as `mcp__nuphus-mcp__*` (e.g. `mcp__nuphus-mcp__desktop_click`).
  297. Run DSH in the desktop session of the machine you want controlled.
  298. ## Demo
  299. A self-contained stdio client that walks through
  300. `initialize → tools/list → tools/call`:
  301. ```sh
  302. cargo build -p nuphus-mcp
  303. cargo run -p nuphus-mcp --example demo
  304. ```
  305. ## Tests
  306. ```sh
  307. cargo check --workspace
  308. cargo test -p nuphus-mcp # protocol + security + vision + models tests (60)
  309. ```
  310. ## Safety
  311. This server can physically control the machine it runs on. Read
  312. [SECURITY.md](SECURITY.md) and the [Safety Annotations section of
  313. TOOLS.md](TOOLS.md#safety-annotations) before deploying. Recommended: run with
  314. `--confirm-write` (or `NUPHUS_MCP_CONFIRM_WRITE=1`) so write tools require an
  315. explicit `"confirm": true` argument.
  316. ## Contributors
  317. Thanks to the people who have contributed code to this project:
  318. | Contributor | Pull requests | Contribution |
  319. |-------------|---------------|--------------|
  320. | [@Steooenwolf-666](https://github.com/Steooenwolf-666) | [#4](https://github.com/mrpulor-gh/nuphus-mcp/pull/4) · [#5](https://github.com/mrpulor-gh/nuphus-mcp/pull/5) · [#6](https://github.com/mrpulor-gh/nuphus-mcp/pull/6) | Native file drag + mouse button support · tool schema/runtime/docs alignment · trusted key press |
  321. | [@yyyyyyyyiiiii](https://github.com/yyyyyyyyiiiii) | [#3](https://github.com/mrpulor-gh/nuphus-mcp/pull/3) | macOS npm platform package `os` field (`darwin`) |
  322. ## License
  323. MIT
  324. Parallel browser tasks: see [tab ownership, desktop exclusion and upgrade requirements](docs/parallel-tabs.md).

Ratings and comments

Sign in to rate this skill.

Sign in

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