Electron Viewer MCP Server

What the code does

We read the source, 1 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const proc = spawn(process.execPath, [path.join(pkgDir, 'install.js')], { cwd: pkgDir, stdio: ['ignore', 'pipe', 'pipe'] });

  const full = rel && path.join(pkgDir, 'dist', rel);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add electron-viewer -- npx -y @acertijosapps/electron-viewer

{
  "mcpServers": {
    "electron-viewer": {
      "command": "npx",
      "args": [
        "-y",
        "@acertijosapps/electron-viewer"
      ]
    }
  }
}

[mcp_servers.electron-viewer]
command = "npx"
args = ["-y", "@acertijosapps/electron-viewer"]

{
  "mcpServers": {
    "electron-viewer": {
      "command": "npx",
      "args": [
        "-y",
        "@acertijosapps/electron-viewer"
      ]
    }
  }
}

{
  "servers": {
    "electron-viewer": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@acertijosapps/electron-viewer"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: ELECTRON_VIEWER_URL (Viewer to show actions live (default http://localhost:8094); without it, CDP is used directly), ELECTRON_VIEWER_PROJECT (Electron project folder that launch_app starts with `electron .` (default: the current folder)).