$ loading_
Debug Electron apps via MCP with process control and deep inspection.
This MCP tool does not declare any required secrets or remote endpoints; its main risk comes from local debugging and process-management capabilities, making it more of a caution than a high-risk tool overall. Open-source availability is a positive factor, but the missing license declaration, zero-star adoption, and unknown maintenance reduce supply-chain confidence.
The material explicitly states that no keys or environment variables are required, and there is no indication of API tokens, account credentials, or other sensitive authentication data; based on the available material, credential exposure appears limited.
No remote host is declared, and the description focuses on local Electron debugging with Chrome DevTools Protocol integration; the provided material does not show user data being sent to external services.
The system flags executes-code, and the description mentions process management and advanced debugging capabilities, indicating standard high-privilege local debugging abilities to attach to or manage Electron processes. This is an inherent capability of the tool category, but it warrants caution because it can affect the runtime state of local applications.
As an Electron debugging tool, it would typically involve access to the target application's runtime state, console, page context, or process information; while the material does not show broad filesystem permissions, debugging inherently may expose local application data, so it should be used with least privilege.
A positive factor is that a public source repository exists, enabling code review; however, the source is only a third-party registry listing, the repo has 0 stars, maintenance is unknown, and no license is declared, so community validation and governance signals are weak. Review the code and dependencies before installation.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "Electron Debug MCP Server" yet — see the docs or source repo.
Connect to the Electron Debug MCP Server, inspect my Electron app's main process startup logs, exception stack traces, and child process states, then suggest likely causes and fixes.
A diagnosis of the startup failure, key log findings, and actionable fix steps.
Use the Electron Debug MCP Server to connect to the renderer process, inspect pre-crash console errors, network requests, and DevTools debugging data to identify the crash cause.
Likely root causes of the renderer crash, supporting evidence, and next debugging recommendations.
Through the Electron Debug MCP Server, list all processes related to the current Electron app, explain each process role, resource usage, and debugging connection status, and flag abnormal processes.
A process state overview highlighting abnormal processes and suggesting next investigation steps.
Debug and automate Electron apps with windows, IPC, logs, and process inspection.
Debug Electron main and renderer processes with automation and network capture.
Embed MCP in Electron apps to control windows and renderers via CDP.
Control and debug running Node.js processes through a CDP-to-DAP bridge.
Build, integrate, and debug MCP clients and related tooling.
Connect Chrome DevTools so AI can debug pages and inspect performance.