Skip to main content
Glama
mesomya

mcp-electron-driver

by mesomya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-electron-driver

No user-submitted related servers found.

    Related Servers

    • da-mcp

      cioinside
      F
      license
      A
      quality
      A
      maintenance
      Cross-platform desktop automation MCP server that lets AI agents capture screenshots, run OCR with UI-element classification, control mouse/keyboard, and launch programs on Linux, macOS, and Windows.
      20
      1
      -

    • openowl

      mihir-kanzariya
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives any AI assistant eyes and hands on your desktop — screenshots, clicking, typing, OCR, window management, accessibility-tree queries, workflow recording.
      5
      Apache 2.0

    • OpenEyes

      yangpeng366
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing AI-friendly computer-use primitives (capture, detect, click) to let LLM agents drive desktop GUI applications on Windows, macOS, and Linux.
      MIT

    • native-devtools-mcp

      vectora-foundry
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI agents and MCP clients direct control over native desktop apps, Chrome/Electron browsers, and Android devices with screenshots, OCR, accessibility-based element lookup, input simulation, window management, CDP, and ADB in one local server.
      130
      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

    A3.8/5.0

    Scored across 39 tools

    Disambiguation4/5

    Most tools have distinct purposes, but some overlap exists, such as keyboard_type and press_sequence being aliases, and drag having a complex fallback that could confuse its boundary with other interaction tools. However, descriptions are detailed enough to clarify differences.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with clear verb_noun structures, such as click, get_text, wait_for_selector, and accessibility_snapshot. There are no deviations in naming conventions.

    Tool Count3/5

    With 39 tools, the count is high for an Electron driver, bordering on heavy. While it covers many scenarios, it may overwhelm agents with its breadth, suggesting some tools could be consolidated or omitted for better focus.

    Completeness5/5

    The toolset provides comprehensive coverage for Electron app testing, including app lifecycle (start_app, stop_app), window management, UI interaction, evaluation, waiting, and debugging. No obvious gaps are present; it supports full CRUD-like operations for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources