Skip to content
nuphus-mcp

nuphus-mcp

by Nuphus Team
Released
22 views
MIT
Repository
Developer Tools

Summary

Computer use for any MCP client: 36 tools covering screenshots, window control, mouse and keyboard, and Chrome over CDP, with local OCR built in and vision on your own key.

Features

  • 36 MCP tools — 15 desktop, 21 browser
  • Screenshots, window activate/move/resize, mouse, keyboard, clipboard
  • Chrome automation over the DevTools Protocol
  • Local OCR with PaddleOCR plus optional YOLO icon detection — no key needed
  • Vision through your own OpenAI-compatible or Anthropic-native model (BYOK)
  • Single Rust binary over stdio — no daemon, no network service
  • --confirm-write gating and a documented threat model with per-tool safety annotations

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "nuphus-mcp" tools will be available.
{
  "mcpServers": {
    "nuphus-mcp": {
      "command": "nuphus-mcp",
      "args": [
        "--confirm-write"
      ]
    }
  }
}

Description

nuphus-mcp is a cross-platform desktop-automation server that gives any MCP client the ability to see and drive the machine it runs on. It speaks JSON-RPC 2.0 over stdio — one binary, no daemon, no network service — so Claude Desktop, Cursor, VS Code, Copilot or any other client can connect and immediately control the screen, windows, keyboard, mouse and Chrome.

The 36 tools

15 desktop tools: screen size, screenshot as PNG or base64, window listing, per-window activate / screenshot / move / resize / info, mouse click, drag, scroll and position, keyboard input and hotkeys, clipboard write and clear. These are implemented on the desktop-api crate over xcap and Win32, with no Tauri dependency.

21 browser tools driving Chrome through the DevTools Protocol via the nuphus-browser crate.

Seeing the screen

Two complementary tools handle perception. desktop_perceive runs local OCR with PaddleOCR — models download on first run, with optional YOLO icon detection — so text on screen is readable without sending anything anywhere. desktop_vision sends a screenshot to your own vision model over an OpenAI-compatible or Anthropic-native API. Used together they give an agent both semantic understanding and precise coordinates.

Desktop and browser automation need no API key at all; only the vision tool does, and it is bring-your-own.

Safety

Write operations can be gated behind --confirm-write, or the equivalent environment variable so one setting covers every MCP client on the machine. The repository documents a threat model and per-tool safety annotations — worth reading before you hand an agent your mouse.

Written in Rust, MIT licensed, and mirrored on Gitee with Chinese documentation for access from mainland China.

Related MCP Servers

MCP: Mux MCP Server

by Mux

New

Official MCP server for the Mux video API, built on a code-execution scheme: the agent writes TypeScript against the SDK and runs it in a Deno sandbox.

Developer Tools
1 views

MCP: ripwire

by Red Hat

New

Red Hat's zero-dependency C++23 code-context engine — ranked call graphs and blast-radius analysis, indexing a repo in under half a second with no server and no database.

Developer Tools
2 views

MCP: Graft

by Trail

New

Builds a searchable markdown graph of your repo so coding agents stop re-exploring it on every task — reported 42% fewer tokens and 46% fewer tool calls.

Developer Tools
1 views

MCP: Expo MCP Server

by Expo

New

Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.

Developer Tools
1 views
Browse all MCP servers →