What is the Electron Debug MCP Server?
It is an MCP server that provides a bridge between the Model Context Protocol and Electron applications, integrating Chrome DevTools Protocol for advanced debugging.
@amafjarkasi
Basic information
π A powerful MCP server for debugging Electron applications with deep Chrome DevTools Protocol integration. Control, monitor, and debug Electron apps through a standardized API.
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
A Model Context Protocol (MCP) server that bridges MCP and Electron applications, enabling advanced debugging capabilities through the Chrome DevTools Protocol (CDP). It allows developers to start, monitor, debug, and control Electron apps programmatically.
Clone the repository, install dependencies with npm install, build with npm run build, then start the server using npm run start. Connect via stdio using an MCP client library or tool.
It is an MCP server that provides a bridge between the Model Context Protocol and Electron applications, integrating Chrome DevTools Protocol for advanced debugging.
Clone the repository, run `npm install`, then `npm run build`. Start the server with `npm run start`.
The server uses stdio for communication. Clients connect using the Model Context Protocol via an MCP client library, stdin/stdout, or a tool that supports MCP.
Operations include start, stop, list, reload, evaluate, pause, and resume. They are accessed via the `electron://operation/{operation}` resource endpoint.
Resources include `electron://info` (overview), `electron://process/{id}` (process details), `electron://logs/{id}` (process logs), `electron://targets` (debug targets), and `electron://cdp/{processId}/{targetId}` (CDP access).

See and control a real Windows PC you own β from any MCP client, locally or remotely. Observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH: your machine, your key.
π The fast, Pythonic way to build MCP servers and clients.
Painless E2E Automation for Mobile and Web

A free remote MCP server for The Living Bread. Bible passages read word for word from a stored public domain text with an evidence label, keyword search and cross references, real churches, gatherings and prayer groups w

Model Context Protocol Servers
Comments