mcp-electron-driver
Related Servers
Alternatives to mcp-electron-driver
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceVerified control of the whole desktop for agents on Windows and Linux: apps with no API, windows, shell, browser. MCP server + CLI + REST API.3928MIT
- AlicenseNot gradedqualityBmaintenanceLets an AI agent launch or attach to a running Electron app and control it directly over the Chrome DevTools Protocol: capture screenshots (optionally with the native window frame), click, drag, hover, scroll, type, press keys, resize and reload. It also exposes JavaScript execution in both the renderer and main process, an accessibility tree with click-ready coordinates, and console logs, so an agent can inspect and operate the app without adding any code to it.96 npmMIT
- AlicenseAqualityCmaintenanceCross-platform desktop automation MCP server that lets AI agents capture screenshots, run OCR with UI-element classification, control mouse/keyboard, and launch programs on Linux, macOS, and Windows.202MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that gives any AI assistant eyes and hands on your desktop — screenshots, clicking, typing, OCR, window management, accessibility-tree queries, workflow recording.5Apache 2.0
- AlicenseBqualityBmaintenanceMCP server providing AI-friendly computer-use primitives (capture, detect, click) to let LLM agents drive desktop GUI applications on Windows, macOS, and Linux.232MIT
- AlicenseNot gradedqualityBmaintenanceGives AI agents and MCP clients direct control over native desktop apps, Chrome/Electron browsers, and Android devices with screenshots, OCR, accessibility-based element lookup, input simulation, window management, CDP, and ADB in one local server.142MIT
TDQS
Scored across 39 tools
Most tools have distinct purposes, but some overlap exists, such as keyboard_type and press_sequence being aliases, and drag having a complex fallback that could confuse its boundary with other interaction tools. However, descriptions are detailed enough to clarify differences.
All tool names follow a consistent snake_case pattern with clear verb_noun structures, such as click, get_text, wait_for_selector, and accessibility_snapshot. There are no deviations in naming conventions.
With 39 tools, the count is high for an Electron driver, bordering on heavy. While it covers many scenarios, it may overwhelm agents with its breadth, suggesting some tools could be consolidated or omitted for better focus.
The toolset provides comprehensive coverage for Electron app testing, including app lifecycle (start_app, stop_app), window management, UI interaction, evaluation, waiting, and debugging. No obvious gaps are present; it supports full CRUD-like operations for the domain.