MCP server for debugging Electron apps via Chrome DevTools Protocol. Start/attach processes, capture screenshots, rea...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Cursor AI
Model
Multiple
Fastest way to find out if electron-mcp-server belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add electron-mcp-server -- npx electron-mcp-serverRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove electron-mcp-serverNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ electron-mcp-server ← registers here
MCP server for debugging Electron apps via Chrome DevTools Protocol. Start/attach processes, capture screenshots, read console errors & network logs, inspect DOM, evaluate JS, and automate UI — built for Cursor and other MCP clients.
Source: GitHub repository
Source check: October 16, 2026
Upstream commit: October 16, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.