MCP server that lets AI agents drive Electron apps — click, type, drag, screenshot, eval JS in the renderer or main process, capture console logs
Electron Driver MCP server exists for a simple reason — assistants are far more useful when they can act on Electron Driver directly instead of describing what you should do. MCP server that lets AI agents drive Electron apps — click, type, drag, screenshot, eval JS in the renderer or main process, capture console logs, handle multi-window apps, and more.
Built on Playwright's experimental _electron API. Works with any Electron app — React, Vue, Svelte, vanilla — as long as you can point it at a compiled main-process entry.
The server ships on npm as electron-driver, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Once Electron Driver is connected, these are the calls the assistant has available:
Lifecycle — The Lifecycle tool exposed by this serverCapturing — The Capturing tool exposed by this serverInteraction — If the primary strategy does not move the detect target, the driver automatically falls back to invoking the React handler directly via fiber-propWaiting — The Waiting tool exposed by this serverDialogs — The Dialogs tool exposed by this serverThis sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Electron Driver's toolset — Lifecycle, Capturing, Interaction and 2 more — is a fair guide to whether it matches your workflow. It is maintained by mesomya; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Electron Driver's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Lifecycle | The Lifecycle tool exposed by this server. |
| Capturing | The Capturing tool exposed by this server. |
| Interaction | If the primary strategy does not move the detect target, the driver automatically falls back to invoking the React handler directly via fiber-prop access and dispatching move/up events on both document and window — cover |
| Waiting | The Waiting tool exposed by this server. |
| Dialogs | The Dialogs tool exposed by this server. |
{
"mcpServers": {
"electron-driver": {
"command": "npx",
"args": ["-y", "electron-driver"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.