Desktop Automation

Created By
tanoba year ago
Overview

what is MCP Desktop Automation?

MCP Desktop Automation is a Model Context Protocol server that provides desktop automation capabilities using RobotJS, allowing LLMs to control mouse movements, keyboard inputs, and capture screenshots of the desktop environment.

how to use MCP Desktop Automation?

To use the MCP Desktop Automation server, configure it in your application by using the provided NPX command. Ensure you grant the necessary system-level permissions for mouse and keyboard control, as well as screenshot capture.

key features of MCP Desktop Automation?

  • Control mouse movements and clicks
  • Simulate keyboard input
  • Capture screenshots of the desktop
  • Detect screen size
  • Simple JSON response format

use cases of MCP Desktop Automation?

  1. Automating repetitive tasks on the desktop.
  2. Creating scripts for testing user interfaces.
  3. Capturing screenshots for documentation or reporting.

FAQ from MCP Desktop Automation?

  • What permissions are required to use this server?

The server requires system-level permissions to capture screenshots and control mouse and keyboard inputs.

  • What are the limitations of this server?

The server has a 1MB response size limit, and high-resolution screenshots may exceed this limit.

  • Is there a specific Node.js version required?

Yes, Node.js version 14.x or higher is required to run the server.

Server Config

{
  "mcpServers": {
    "desktop-automation": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-desktop-automation"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tanob
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago