Electron is a framework for building desktop applications using JavaScript, HTML, and CSS. It allows developers to create cross-platform desktop apps using web technologies.
Enables detection of Electron/WebView2 apps with sparse accessibility trees and can relaunch an Electron app with a Chrome DevTools Protocol debug port, allowing its web content to be automated through the browser tools.
The local MCP server that gives any AI agent safe desktop control. Provides 6 compact tools (computer, accessibility, window, system, browser, task) for cross-platform GUI automation with ground-truth verification.
2
7
671 npm
406
MIT
Why this server?
Provides tools for Electron app development: IPC scaffolding, security auditing, migration guidance, performance analysis, and more.
Provides 18 tools for Electron development, including secure IPC scaffolding, security audits, migration assistance, and build error diagnosis, enabling AI assistants to generate correct Electron code.
18
261 npm
2
MIT
Why this server?
Allows cleaning of shared Electron framework cache.
MCP server for macOS disk cache management. Enables AI agents to free disk space on demand by scanning and clearing developer caches.
13
22 PyPI
1
Sustainable Use v1.0
Why this server?
Allows AI agents to control real Electron desktop applications: launch apps, inspect the accessibility tree, click, type, select elements, read state, take screenshots, handle dialogs, and assert UI state using stable refs or selectors.
Drive, 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 assertions
57
12
MIT
Why this server?
Provides tools for discovering Electron apps, connecting to renderer and main processes, automating renderer via CSS selectors, managing breakpoints, stepping, call stack, evaluating JavaScript in both processes, capturing network requests, and taking screenshots.
Electron debugging MCP server for both renderer (via Chrome DevTools Protocol) and main process (via V8 Inspector Protocol), enabling automation, debugging, and network capture.
31
4 npm
MIT
Why this server?
Statically compares two Electron app builds to identify changes in IPC channels, preload bridge members, window settings, runtime/fuses, network endpoints, and storage keys, with file and line references. Supports ASAR archives and packaged Electron app inputs, plus policy checks, SARIF output, source-map lookups, bundle recovery, and bounded analysis tools for release review.
Static security review of Electron apps and binaries: compares two builds and reports changed IPC channels, preload bridge members, window settings, fuses and network hosts with file and line, plus a CI policy gate, without executing the target.
16
10
MIT
Why this server?
Enables automated testing of Electron applications, including renderer testing through Playwright, native Electron menu inspection, and launching apps by executable or connecting via a CDP endpoint.
This server enables unified testing of web, Electron, and Windows desktop applications by connecting AI clients to application controls. It supports creating requirement-traced test plans, executing automated suites, and generating evidence-rich, auditable reports.
24
MIT
Why this server?
Scaffolds cross-platform Electron apps with code signing.
Scaffold and audit Starter Series projects — MCP server, Claude Code skill, and CLI in one package.
9
36 npm
2
MIT
Why this server?
Enables automation of Electron applications by launching with the renderer accessibility flag enabled and using a guest debug port for DOM snapshots, fill, and click actions.
Enables AI coding agents to work inside a disposable Windows guest desktop, where they can run shell commands, launch applications, inspect and operate native GUI controls, perform browser DOM actions, and transfer files. Fresh observations, PNG screenshots, and hashed artifacts let agents verify results without touching the host desktop.
