MCP Desktop Tools
Related Servers
Alternatives to MCP Desktop Tools
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA local MCP server for Windows that gives Claude control of your screen, enabling screen viewing, image-based element finding, clicking/typing, macro recording and replaying, and scheduled automation with failsafe safety features.MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that lets Claude Desktop and Claude Code control your PC — take screenshots, click, type, manage windows, and more.MIT
- AlicenseNot gradedqualityDmaintenanceThis MCP server enables browser automation (navigation, clicking, screenshots) and file reading (Excel, Word, PowerPoint, CSV, images) for Claude Code and any MCP client.MIT
- AlicenseNot gradedqualityFmaintenanceA standalone MCP server for Windows desktop control, enabling screenshots, mouse and keyboard input, app launch, window/display management, and clipboard access via natural language.3MIT
- FlicenseAqualityCmaintenanceWindows desktop automation MCP server enabling screenshot capture, precise visual locating of UI elements via vision models, and automated mouse clicking.41-
- AlicenseNot gradedqualityBmaintenanceA Windows desktop control MCP server that gives Claude eyes and hands—screen capture with coordinate-grid overlays, pixel-perfect DPI-correct mouse/keyboard input via a Rust backend, and direct PowerShell command execution, enabling full local desktop automation through natural language.4 npm1MIT
TDQS
Scored across 20 tools
Each tool has a clearly distinct purpose with no ambiguity. The browser tools handle web interactions, desktop tools manage OS-level operations, and screenshot tools capture different screen areas, all with specific, non-overlapping functions.
All tools follow a consistent snake_case naming pattern with clear verb_noun structure (e.g., browser_click, desktop_clipboard_read, screenshot_fullscreen). The naming is predictable and organized by domain prefixes (browser_, desktop_, screenshot_).
With 20 tools, the count is slightly high but reasonable for the broad scope of desktop automation covering browser control, OS interactions, and screenshot functionality. Each tool serves a distinct purpose, though some could potentially be consolidated.
The toolset provides comprehensive coverage for desktop automation, including full browser control (navigation, interaction, reading), OS operations (clipboard, keyboard, mouse, windows), and screenshot capabilities (fullscreen, region, window). No obvious gaps exist for the stated purpose.