A
licenseC
qualityD
maintenanceEnables AI models to test and interact with Electron applications using Playwright, supporting CDP connection and app launch modes.
28
16 npm
MIT
electron-mcp-server
Related Servers
Alternatives to electron-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI-powered automation, debugging, and observability of Electron applications through Chrome DevTools Protocol integration, providing real-time UI interaction and inspection capabilities.25 npm23MIT
- AlicenseAqualityAmaintenanceDrive, inspect, and assert on real Electron desktop apps from an AI agent — agent-native, Playwright-style automation with accessibility refs, stable error codes, and retrying assertions558MIT
- AlicenseAqualityDmaintenanceDrive Electron apps from AI agents via MCP - click, type, drag, screenshot, eval JS, and more.3919 npm3MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to visually interact with frontend apps by taking screenshots, clicking elements, reading console logs, and performing visual diffs.12 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to autonomously interact with and test web applications in a real browser, providing DOM/Accessibility tree extraction, runtime telemetry, screenshot capture, and Markdown test reports.264 npm1MIT
TDQS
C2.4/5.0
Scored across 48 tools
Disambiguation2/5
Several tools have overlapping purposes: screenshot and take_screenshot both capture the current page, get_accessibility_tree and get_accessibility_snapshot both retrieve accessibility data, and interact_accessible_node overlaps with click/fill/select. This creates multiple unclear boundaries that could easily cause misselection.
Naming Consistency3/5
Most names use snake_case and are readable, but the conventions are mixed: some are verb_noun (take_screenshot, capture_element_screenshot), some are bare nouns or adjectives (screenshot), and some are simple verbs without objects (execute, click). This is not chaotic but is inconsistent enough to be notable.
Tool Count2/5
48 tools is very heavy for an Electron testing MCP server, exceeding the 25-tool threshold where count becomes a problem. Many tools are duplicates or near-duplicates (e.g., screenshot variants, accessibility variants), indicating the surface is over-expanded rather than tightly scoped.
Completeness4/5
The server covers a wide lifecycle: launching/connecting sessions, page interaction, screenshots, accessibility, network/geolocation emulation, recording, navigation, performance, and debug logging. Some minor gaps remain, such as keyboard actions, drag-and-drop, or built-in assertions, but core Electron testing workflows are well represented.
Maintenance
ActivityInactive
ResponsivenessNo issues