Electron Debug MCP Server

The Electron Debug MCP Server is a specialized bridge that connects the Model Context Protocol (MCP) ecosystem to Electron applications, providing developers with a unified API for launching, monitoring, and deeply debugging Electron processes. By exposing process‑management endpoints and integrating the Chrome DevTools Protocol (CDP) under MCP, it eliminates the need for separate tooling or manual command‑line interactions. Instead of juggling multiple debugging sessions, developers can programmatically start an Electron app with the endpoint, inspect its runtime state, and then drill into any page or renderer through CDP commands exposed via .

At its core, the server offers a clean set of resource endpoints that mirror the lifecycle of an Electron application. Clients can retrieve a global overview (), query detailed information for a specific process (), stream logs (), and enumerate all CDP targets (). Each endpoint is designed to be stateless from the MCP perspective, allowing multiple assistants or tools to query and act concurrently without side effects. The integration with CDP is particularly powerful: once a target is discovered, the server forwards arbitrary CDP commands, enabling script evaluation, page reloads, or even pausing JavaScript execution—all through the familiar MCP message format.

For real‑world scenarios, this server shines in automated testing pipelines where an AI assistant orchestrates end‑to‑end test runs. The assistant can start a build, attach to the renderer process via CDP, inject test scripts, capture console output, and report failures back through MCP prompts. In continuous integration workflows, it can monitor resource usage or detect memory leaks by pulling logs and metrics from the process endpoints. Even in development environments, a human developer can use an MCP‑enabled IDE extension to launch the app, step through code, and inspect network traffic without leaving their editor.

Unique advantages stem from its tight coupling to MCP’s declarative style. Because the server operates over stdio, it can be launched as a child process from any MCP‑compliant client—be it Claude, GPT‑4o, or a custom tool. The explicit resource schema ensures that clients always know what operations are possible, reducing guesswork and improving reliability. Moreover, by exposing CDP under MCP, developers gain a single point of entry for all debugging features, simplifying authentication, target discovery, and command routing. This unified approach not only streamlines workflows but also paves the way for advanced AI‑driven debugging assistants that can reason about Electron internals, suggest fixes, or automate routine maintenance tasks.