Skip to main content
Glama
halilural

Electron MCP Server

by halilural
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_electron_window_infoB

Get information about running Electron applications and their windows. Automatically detects any Electron app with remote debugging enabled (port 9222).

take_screenshotA

Take a screenshot of any running Electron application window. Returns base64 image data for AI analysis. No files created unless outputPath is specified.

send_command_to_electronA

Send JavaScript commands to any running Electron application via Chrome DevTools Protocol.

Enhanced UI interaction commands:

  • 'find_elements': Analyze all interactive elements (buttons, inputs, selects) with their properties

  • 'click_by_text': Click elements by their visible text, aria-label, or title

  • 'click_by_selector': Securely click elements by CSS selector

  • 'fill_input': Fill input fields by selector, placeholder text, or associated label

  • 'select_option': Select dropdown options by value or text

  • 'send_keyboard_shortcut': Send keyboard shortcuts like 'Ctrl+N', 'Meta+N', 'Enter', 'Escape'

  • 'navigate_to_hash': Safely navigate to hash routes (e.g., '#create', '#settings')

  • 'get_page_structure': Get organized overview of page elements (buttons, inputs, selects, links)

  • 'debug_elements': Get debugging info about buttons and form elements on the page

  • 'verify_form_state': Check current form state and validation status

  • 'get_title', 'get_url', 'get_body_text': Basic page information

  • 'eval': Execute custom JavaScript code with enhanced error reporting

IMPORTANT: Arguments must be passed as an object with the correct properties:

Examples:

  • click_by_selector: {"selector": "button.submit-btn"}

  • click_by_text: {"text": "Submit"}

  • fill_input: {"placeholder": "Enter name", "value": "John Doe"}

  • fill_input: {"selector": "#email", "value": "user@example.com"}

  • send_keyboard_shortcut: {"text": "Enter"}

  • eval: {"code": "document.title"}

Use 'get_page_structure' or 'debug_elements' first to understand available elements, then use specific interaction commands.

read_electron_logsB

Read console logs and output from running Electron applications. Useful for debugging and monitoring app behavior.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

B3.4/5.0

Scored across 4 tools

Disambiguation2/5

The tool set has significant overlap and unclear boundaries. The first three tools (get_electron_window_info, read_electron_logs, send_command_to_electron) are distinct, but the 'Enhanced UI interaction commands' section contains 14 tools that are poorly differentiated. For example, 'debug_elements' and 'get_page_structure' seem to serve similar purposes, and 'click_by_text' vs 'click_by_selector' are just different targeting methods rather than distinct operations. This creates confusion about which tool to use for basic UI tasks.

Naming Consistency2/5

The naming conventions are inconsistent and chaotic. The first three tools use snake_case with clear verb_noun patterns, but the UI interaction tools mix styles: some use snake_case ('click_by_text'), others use camelCase ('getPageStructure' in the description but 'get_page_structure' as the tool name), and some are just verbs ('eval'). There's no discernible pattern across the entire set, making it difficult to predict tool names.

Tool Count3/5

With 17 total tools (3 core + 14 UI interaction), the count is borderline heavy for an Electron automation server. While Electron automation can justify many tools, the UI interaction section feels bloated with redundant or overly specific tools (e.g., separate tools for 'get_title', 'get_url', and 'get_body_text' instead of a unified 'get_page_info'). The count would be more appropriate if the UI tools were consolidated into fewer, more general-purpose tools.

Completeness4/5

For an Electron automation server, the tool surface is reasonably complete. It covers core areas: window detection, log reading, command execution, UI interaction (with extensive element targeting methods), and screenshots. The main gap is the lack of window management tools (resize, minimize, close windows) and application lifecycle control (launch/quit apps). However, the existing tools cover most common automation workflows, with the UI interaction section being particularly thorough despite its redundancy issues.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources