Skip to main content
Glama
lazy-dinosaur

electron-test-mcp

by lazy-dinosaur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to electron-test-mcp

No user-submitted related servers found.

    Related Servers

    • Playwright MCP with Electron

      robertn702
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables Model Context Protocol tools for automating web browsers and Electron desktop applications using Playwright's accessibility tree snapshots. It supports window management and JavaScript execution in the main process, providing deterministic automation through structured data.
      224 npm
      17
      Apache 2.0

    • electron-mcp-server

      ohah
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Electron app automation via Chrome DevTools Protocol (CDP), allowing MCP clients like Cursor or Claude Desktop to interact with Electron apps.
      4
      MIT

    • electron-mcp-bridge

      rudraptpsingh
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to attach to an already-running Electron desktop app and inspect both the Node.js main process and Chromium renderer, invoking IPC channels, evaluating renderer scripts, capturing screenshots, and reading diagnostics. It also lets apps expose custom verification oracles so agents can confirm real business effects like database rows, file sidecars, and hash receipts instead of just UI changes.
      0
      MIT

    • mcp-cdp

      dockndevai
      A
      license
      A
      quality
      A
      maintenance
      Enables agents to inspect and drive Electron or Chrome/Chromium apps via the Chrome DevTools Protocol, exposing DOM snapshots, console logs, network requests, and gated interactions like clicking, typing, and navigating.
      6
      252 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools target clearly distinct actions (click vs fill vs hover vs drag), and the lifecycle tools connect/launch/close/disconnect are well separated. However, there is real overlap among scroll, scrollTo, and scrollIntoView, and click vs mouseClick vs dblclick, which could cause misselection without careful reading.

    Naming Consistency2/5

    The set mixes snake_case-adjacent single words (connect, launch, screenshot, click, fill) with camelCase (getText, selectOption, getAttribute, isVisible, scrollIntoView, mouseMove, mouseClick) and an odd unseparated 'dblclick'. No single predictable verb_noun or verbNoun convention holds throughout.

    Tool Count3/5

    28 tools is heavy for the scope and includes highly granular primitives (mouseMove, mouseDown, mouseUp, mouseClick, scroll/scrollTo/scrollIntoView) that could be consolidated. It is defensible for a full automation harness but sits at the cumbersome end.

    Completeness4/5

    Covers the lifecycle (connect/launch/close/disconnect), inspection (screenshot, snapshot, getText, getAttribute, isVisible, count), and rich interaction plus JS evaluation in both renderer and main process. Minor gaps like file upload, navigation/wait-for-navigation, and iframe handling exist but are workaroundable.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources