MCP.so
Sign In

Electron Driver

@mesomya

RepositoryHomepage

About Electron Driver

MCP server that lets AI agents drive Electron apps — click, type, drag, screenshot, eval JS in the renderer or main process, capture console logs. 38 tools, Playwright-powered, works with any Electron app.

Basic information

Category

Browser Automation

License

MIT

Runtime

node

Transports

stdio

Publisher

mesomya

Submitted by

Somya Sharma

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "electron-driver": {
      "command": "node",
      "args": [
        "index.mjs",
        "#",
        "stdio",
        "MCP",
        "server"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Electron Driver?

Electron Driver is an MCP (Model Context Protocol) server that lets AI agents automate Electron desktop apps. It provides tools for clicking, typing, dragging, taking screenshots, evaluating JavaScript in both renderer and main processes, reading console logs, managing multi-window apps, and capturing accessibility snapshots. Built on Playwright’s experimental _electron API, it works with any Electron app—React, Vue, Svelte, or vanilla—as long as you can point it at a compiled main-process entry. It is designed for agent hosts like Claude Code, Claude Desktop, and Cursor.

How to use Electron Driver?

Install the package via npm (npm install electron-driver), then register the MCP server with your agent host. For Claude Code, create a .mcp.json file or use claude mcp add. For other hosts, add the server configuration pointing at npx electron-driver or the absolute path to the module. Once configured, launch your Electron app with the start_app tool, interact using any of the 38 tools, and close the session with stop_app. All tool calls are logged to <project>/.electron-driver/driver.log during a session.

Key features of Electron Driver

  • 38 tools covering lifecycle, interaction, capturing, and evaluation.
  • Full Playwright selector engine (CSS, text=, role=, and more).
  • Evaluate JavaScript in renderer or main process.
  • Multi-window support: list and switch between windows.
  • Accessibility snapshot capture (ARIA tree).
  • Drag with real Chromium input events and React fallback.

Use cases of Electron Driver

  • An agent verifies a feature by running the app and checking the visible result.
  • Visual regression testing during a refactor.
  • Accessibility audits via ARIA tree snapshots.
  • Reproducing bugs from a natural-language description.
  • Teaching a subagent to iterate on UI until a spec passes.

FAQ from Electron Driver

What dependencies are required to run Electron Driver?

Node 18+ and an already-built Electron app. You do not need to install Playwright browsers separately—the _electron API drives the Electron binary directly.

How does the server handle multiple sessions?

The server owns exactly one Electron session at a time. start_app launches it, stop_app closes it. Calling start_app while a session exists returns an ALREADY_RUNNING error.

Where are screenshots stored and how are they

Comments

More Browser Automation MCP servers

Fetch MCP Server

zcaceres

A flexible HTTP fetching Model Context Protocol server.

797

Slack Slack

microsoft

Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.

92.5K

Fastcrw

us

Fast, lightweight Firecrawl/Tavily alternative in Rust. Web scraper, crawler & search API with MCP server for AI agents. Drop-in Firecrawl-compatible API (/scrape, /crawl, /search). 2.3x faster than Tavily, 1.5x faster than Firecrawl in 1K-URL benchmarks. 6 MB RAM, single binary.

286

mcp-browser-use: MCP server for browser-use

vinayak-mehta

MCP server for browser-use

81

MCP Browser Kit

ndthanhdev

An MCP Server that enables AI assistants to interact with your local browsers.

54