Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

attach_by_pid

Attach to a running Electron app by PID, resolving its remote-debugging port from process arguments; the app must be started with --remote-debugging-port.

Instructions

Attach to a running Electron app by PID. Resolves the remote-debugging port from process arguments. App must have been started with --remote-debugging-port.

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": {
      "pid": "<pid>"
    },
    "name": "attach_by_pid"
  }
}

Input Schema

NameRequiredDescriptionDefault
pidYesOS process ID of the Electron app
nameNoOptional friendly name for this attached session

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate an open-world, non-destructive operation. The description adds useful context by explaining that the remote-debugging port is resolved from process arguments, but it does not cover failure behavior, permissions, or what session creation implies.

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

Conciseness5/5

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

Three short sentences, front-loaded with the core action, followed by mechanism and prerequisite. Every sentence contributes without repetition or filler.

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

Completeness4/5

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

For a two-parameter attach tool with no output schema, the description covers the action, target, port-resolution mechanism, and startup prerequisite. It is nearly complete, with only minor gaps around failure modes or post-attach session semantics.

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?

Input schema coverage is 100%, with both pid and name fully documented. The description reinforces that PID identifies the target process but adds no further meaning beyond the schema, so baseline 3 is appropriate.

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: attaching to a running Electron app by PID. The 'by PID' phrasing distinguishes it from a generic attach sibling, but it does not explicitly name or contrast with that alternative.

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

Usage Guidelines4/5

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

Gives a clear prerequisite: the app must have been started with --remote-debugging-port. This tells the agent when the tool is usable, but it does not state when to prefer another attach method or what to do if the flag is absent.

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