Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

start_app

Launch an Electron app with remote debugging enabled and optionally configure the DevTools port, extra CLI arguments, or main-process inspection for debugging.

Instructions

Start an Electron application with remote debugging enabled. Example: {"appPath":"D:/apps/my-electron-app","debugPort":9222}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "appPath": "<appPath>"
    },
    "name": "start_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appPathYesPath to the Electron app (directory or main script)
debugPortNoOptional Chrome DevTools debugging port (default: random 9222-9999)
extraArgsNoOptional extra Electron CLI args (e.g. ["--no-sandbox"] for CI/containers)
inspectMainNoIf true, open a pinned --inspect port for main-process tools: evaluate_main, main_state, ipc_tap, get_ipc_log, webcontents_topology, open_deep_link, focus_window, set_window_bounds, get_clipboard, set_clipboard, get_downloads, set_permission

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover safety (destructiveHint=false) and the open-world nature of launching an external process; the description adds that debugging is enabled and gives a concrete example. It does not disclose whether the call waits for the app to be ready, what happens on launch failure, or that the chosen debug port is returned to the caller — important since the port defaults to a random 9222-9999 and there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence stating the action and its debugging side effect, followed by a compact example — nothing wasted. The inline JSON example is slightly noisy but serves as a usable invocation template.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a process-launching tool with no output schema, the description leaves key facts unstated: what the response contains (port, pid), whether it blocks, and failure behavior. The parameter side is fully covered by the schema, so the remaining gaps are behavioral rather than structural.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters are already documented in structured form, including the debugPort range and the inspectMain tool list. The example reinforces the appPath+debugPort combination but adds no semantics beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Start an Electron application') plus the key side effect (remote debugging enabled), which distinguishes it from stop_app and from attach-style siblings. It does not explicitly say how it differs from attaching to an already-running app, so it falls short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus attach, attach_by_pid, or discover_apps, and no prerequisites (e.g., whether the app must not already be running, whether it blocks until ready). Usage is only implied by the verb itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools