Mouse Movement And Click Control Via Mcp

via “mouse-cursor-movement-and-clicking”

Computer Use MCP Server

Unique: Abstracts OS-specific input APIs (Xdotool, CGEvent, SendInput) behind a unified MCP interface, allowing agents to perform mouse interactions without knowledge of underlying platform; includes configurable movement curves and timing to simulate human-like interaction patterns

vs others: Provides cross-platform mouse automation in a single MCP tool without requiring separate platform-specific libraries, and integrates directly into agent decision loops unlike standalone automation frameworks

via “mouse control with absolute positioning”

Computer Use MCP Server

Unique: Exposes mouse control as discrete MCP tools (move, click) with absolute coordinate parameters, allowing agents to compose clicks with screenshot analysis in a tight perception-action loop. No gesture or drag abstractions — forces explicit coordinate calculation.

vs others: More granular than high-level UI automation frameworks (Selenium, Playwright) because it operates at raw input level; more flexible for non-web UIs but requires agent to handle coordinate math

Zero-dependency macOS desktop automation for AI agents. Screenshot, mouse, keyboard, clipboard, and window control via MCP. 18 tools, macOS 13+, one command: npx mac-use-mcp.

Unique: Integrates mouse control directly into MCP tool schema with coordinate-based targeting, allowing agents to chain screenshot analysis → coordinate extraction → click execution in a single agent loop without external tool dependencies or subprocess management

vs others: More direct than PyAutoGUI or xdotool because it uses native macOS CGEvent APIs with MCP protocol binding, eliminating subprocess overhead and enabling real-time feedback loops between vision analysis and mouse actions

via “dom-element-interaction-via-selectors”

Experimental MCP server for browser automation using Puppeteer (inspired by @modelcontextprotocol/server-puppeteer)

Unique: Wraps Puppeteer's low-level click/type/hover methods as discrete MCP tools with selector parameters, allowing Claude to reference elements by CSS/XPath without needing to understand Puppeteer API syntax. Implements implicit element visibility and existence checks before interaction, reducing error handling burden on the client.

vs others: More accessible than raw Puppeteer API because Claude can specify selectors in natural language and the MCP server handles the Puppeteer method dispatch; more reliable than simple coordinate-based clicking because it uses semantic element selection rather than pixel positions.

via “user-interaction-simulation”

MCP Server for Browser Dev Tools

Unique: Combines CDP Input domain (for low-level event injection) with element targeting via selectors, providing agents with high-level interaction primitives (click element by selector) without requiring coordinate calculation or JavaScript event handling

vs others: More reliable than JavaScript-based click simulation because it uses CDP's native input injection, which properly triggers browser event handlers and respects z-index/visibility rules

via “keyboard-and-mouse-input-simulation”

MCP server: playwright-mcp

Unique: Exposes Playwright's low-level keyboard and mouse APIs as MCP tools, enabling agents to simulate complex user interactions beyond simple element clicks. Supports modifier key combinations and arbitrary key sequences.

vs others: More flexible than element-based interaction because it supports coordinate-based clicking and keyboard shortcuts. More reliable than simulating keyboard input via JavaScript because it uses native browser input events.

via “keyboard-and-mouse-event-simulation”

Model Context Protocol servers for Playwright

Unique: Exposes Playwright's keyboard and mouse APIs as discrete MCP tools with modifier key support and drag-and-drop coordination, enabling Claude to simulate complex user interactions without JavaScript event construction

vs others: More reliable than raw JavaScript event dispatch because Playwright's keyboard/mouse APIs account for browser-specific event ordering and timing; more flexible than Selenium because it supports drag-and-drop natively

via “mouse-control-with-coordinate-targeting”

MCP server exposing desktop computer-use as an MCP tool

Unique: Exposes raw coordinate-based mouse control through MCP protocol, allowing clients to implement their own coordinate detection strategies (vision models, OCR, element detection) rather than bundling a specific vision system, enabling flexibility in how coordinates are determined.

vs others: More flexible than vision-integrated automation tools because it decouples coordinate detection from mouse control, allowing clients to use any vision model or coordinate source while maintaining a simple, stateless MCP interface.

via “game-window-interaction-and-control”

MCP tool for Garry's Mod: RCON, Lua execution, window screenshot/control, and SFTP file management

Unique: Wraps OS-level input simulation (SendInput, etc.) as MCP tools, enabling LLM agents to control the game window without custom input handling; integrates with screenshot capture for closed-loop automation

vs others: More direct than scripting game mods for client-side automation; enables AI agents to interact with the game UI and client without modifying game code

via “programmatic mouse control with pixel-level positioning”

** - Programmatic control over Windows system operations including mouse, keyboard, window management, and screen capture using nut.js.

Unique: Uses nut.js's abstraction over Windows native input APIs (SendInput) rather than simulating raw hardware events, enabling reliable cross-application mouse control that respects Windows input queuing and cursor acceleration

vs others: More reliable than raw Win32 SendInput calls because nut.js handles platform-specific quirks; faster than image-recognition-based automation because it uses direct coordinate targeting rather than screen analysis