mrpulor-gh/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.

nuphus‑mcp – Desktop & Browser Automation Server for AI Agents

What it isnuphus-mcp is a lightweight, cross‑platform server that lets any MCP‑compatible AI agent (Claude Desktop, Cursor, VS Code Copilot, etc.) control the local computer. It talks JSON‑RPC 2.0 over standard input/output, so there is no network daemon to run – just a single binary.

Why it matters – Modern LLM‑based agents need to see the screen and act on it (move the mouse, type, click, read OCR, drive Chrome). nuphus-mcp provides that bridge while keeping the heavy lifting (vision, OCR) local, so no external API keys are required for desktop work. Vision can be hooked to any OpenAI‑compatible or Anthropic model you supply (BYOK – bring‑your‑own‑key).


Core Features

Category Tools (total) Highlights
Desktop 15 Screen size, PNG/base64 screenshots, window list & manipulation, mouse click/drag/scroll, keyboard input, hotkeys, clipboard write/clear. Implemented via the desktop-api Rust crate (xcap + Win32, no Tauri).
Vision desktop_vision forwards a screenshot to your own vision model (OpenAI‑compatible or Anthropic). desktop_perceive runs PaddleOCR (and optional YOLO icon detection) locally, auto‑downloading models on first use.
Browser 23 Full Chrome/Edge CDP control via nuphus-browser (chromiumoxide): navigation, DOM‑level clicks, typing, script execution, scrolling, accessibility‑tree snapshots, cookie management, tab handling, file uploads/downloads, etc.
Transport JSON‑RPC 2.0 over stdin/stdout – no HTTP server, no background daemon.
Safety Destructive tools are annotated; optional --confirm-write (or NUPHUS_MCP_CONFIRM_WRITE=1) forces an explicit `

Related

  • Project
  • Project
  • Project
  • Project