Skip to main content
Glama
aj47

Electron Native MCP Server

by aj47
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
electron_executeA

Execute JavaScript in an Electron app's renderer process via CDP.

Returns the last expression's value. Use state object to persist data between calls.

Key patterns:

  • Click: document.querySelector('#btn').click(); 'done'

  • Fill input: el.value='text'; el.dispatchEvent(new Event('input',{bubbles:true}))

  • Read DOM: Array.from(document.querySelectorAll('a')).map(a=>({text:a.textContent,href:a.href}))

Best practices:

  • Use multiple calls: find element → interact → verify result

  • Always return a value to confirm what happened

  • Check page state after actions (don't assume)

Error "No Electron targets found" = app needs --inspect flag or CDP_PORT env var mismatch.

electron_resetA

Reset CDP connection. Use when execute times out or returns connectivity errors. Clears the state object.

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

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
ResponsivenessNo issues

Resources