Skip to main content
Glama
Sign In
Electron Native MCP Server

Electron Native MCP Server

by aj47
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Electron Native MCP Server

No user-submitted related servers found.

    Related Servers

    • electron-viewer

      acertijosapps
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets an AI agent launch or attach to a running Electron app and control it directly over the Chrome DevTools Protocol: capture screenshots (optionally with the native window frame), click, drag, hover, scroll, type, press keys, resize and reload. It also exposes JavaScript execution in both the renderer and main process, an accessibility tree with click-ready coordinates, and console logs, so an agent can inspect and operate the app without adding any code to it.
      553 npm
      MIT

    • Electron Debug MCP Server

      amafjarkasi
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables debugging of Electron applications through the Model Context Protocol, with deep integration of Chrome DevTools Protocol for process management and advanced debugging capabilities.
      80 npm
      93
      ISC

    • 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
      110 npm
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: electron_execute is for executing JavaScript in an Electron app, while electron_reset is for resetting the CDP connection. There is no overlap in functionality, making them easy to differentiate.

    Naming Consistency5/5

    Both tools follow a consistent naming pattern with the prefix 'electron_' followed by a verb (execute, reset). This makes the tool set predictable and easy to understand.

    Tool Count2/5

    With only two tools, the server feels under-scoped for automating Electron apps. Key operations like launching apps, managing windows, or handling events are missing, limiting its utility for comprehensive automation tasks.

    Completeness2/5

    The tool set is severely incomplete for Electron automation. It lacks essential operations such as launching or quitting apps, managing multiple windows, handling IPC, or accessing Node.js modules, which are core to Electron's functionality.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources