electron
🚀 A powerful MCP server for debugging Electron applications with deep Chrome DevTools Protocol integration. Control, monitor, and debug Electron apps through a standardized API.
claude mcp add --transport stdio amafjarkasi-electron-mcp-server node build/index.js
How to use
This MCP server exposes debugging and control capabilities for Electron applications by bridging MCP with the Chrome DevTools Protocol. It lets you start and monitor Electron processes, connect to debugging targets, issue CDP commands, evaluate JavaScript in page contexts, and manage logs and targets across running Electron instances. Clients communicate over stdio using MCP messages, enabling scripted or programmatic debugging workflows against Electron apps.
To use it, clone or install the server, install dependencies, and start the server in Node.js mode. Once running, connect an MCP client to the server via standard input/output. You can list running Electron processes, start new apps with debugging enabled, retrieve detailed process information, and issue CDP commands (e.g., reload pages, pause/resume scripts, or evaluate code) against specific targets. The server also provides resource endpoints to fetch logs, targets, and process details, making it easier to orchestrate complex debugging sessions across multiple Electron instances.
How to install
Prerequisites:
- Node.js (v14+ recommended) and npm
- Git
Install steps:
-
Clone the repository git clone https://github.com/yourusername/electron-mcp-server.git
-
Navigate to the project directory cd electron-mcp-server
-
Install dependencies npm install
-
Build the project (transpile TS to JS if using TypeScript) npm run build
-
Start the MCP server npm run start
Note: The server communicates over stdio using MCP, so ensure your client is prepared to speak MCP messages over stdin/stdout.
Additional notes
Tips:
- Ensure Node.js version compatibility with the project’s TypeScript configuration and Electron debugging integration.
- If you modify code, re-run the build step before starting the server to generate updated JS bundles.
- The server uses stdio for MCP communication; if you need to integrate with a different transport, you may need to adapt the server or your client accordingly.
- Common issues include port conflicts or missing dependencies—check npm install logs and Electron binary paths if you customize the app startup.
- Review the available MCP operations and endpoints to understand what you can start, stop, list, reload, evaluate, pause, or resume for Electron processes.
Related MCP Servers
iterm
A Model Context Protocol server that executes commands in the current iTerm session - useful for REPL and CLI assistance
mcp
Octopus Deploy Official MCP Server
furi
CLI & API for MCP management
editor
MCP Server for Phaser Editor
DoorDash
MCP server from JordanDalton/DoorDash-MCP-Server
mcp
MCP сервер для автоматического создания и развертывания приложений в Timeweb Cloud