$ loading_
Embed MCP in Electron apps to control windows and renderers via CDP.
This is an open-source embedded MCP server for Electron with no declared secrets or remote endpoints, and no clear signs of high-risk exfiltration or credential abuse. Its main concerns stem from local control over Electron renderers via the DevTools Protocol, plus low community adoption and unknown maintenance status.
The materials state that no keys or environment variables are required, and there is no indication that API tokens, account credentials, or other sensitive authentication data must be provided, so credential exposure appears low.
No remote host is declared. The description indicates functionality centered on local Electron apps and Chrome DevTools Protocol control, with no explicit statement that user data is sent to external services.
The tool acts as an embedded MCP server, exposes BrowserWindow surfaces, and allows clients to drive renderers, which is a clear local control/execution capability. This is a normal high-privilege surface for an MCP tool, but the materials do not show abnormal system permissions beyond its stated purpose.
By controlling Electron renderers and window surfaces, the tool could theoretically access application UI content and whatever data is visible to the renderer process. The materials do not describe extra filesystem read/write or explicit over-privileged access, but its access to in-app data surfaces warrants caution.
Positive factors include auditable open-source code and an MIT license. However, the source is a third-party registry entry, community adoption is 0 stars, and maintenance status is unknown, so supply-chain trust is limited and code/dependency review is advisable before adoption.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "@nebula-agents/electron-mcp" yet — see the docs or source repo.
Use electron-mcp to connect to the current Electron app, list all BrowserWindows, open a DevTools Protocol session for the main window, capture a screenshot, and return a summary of visible UI elements.
A list of windows, a screenshot of the main window, and a summary of key visible UI elements and states.
Use electron-mcp to drive the target renderer, retrieve a summary of the current DOM structure, console logs, and network activity, and highlight any potential errors.
A page structure overview, log summary, request list, and notes on suspected errors.
Use electron-mcp to operate the app's main window: click the Settings button, switch to the Advanced tab, verify that the 'Enable Sync' toggle exists and is clickable, then generate a test result summary.
The execution results, verification outcome, and any failed steps or error notes.
Debug and automate Electron apps with windows, IPC, logs, and process inspection.
Debug Electron apps via MCP with process control and deep inspection.
Provides IPC scaffolding, security auditing, and build help for Electron projects.
Generate correct Electron code with security audits, migrations, and build diagnostics.
Control and debug running Node.js processes through a CDP-to-DAP bridge.
Debug Electron main and renderer processes with automation and network capture.