Launch Electron app (direct binary)
launch_appSpawns an Electron application with debugging ports enabled, allowing control of both the renderer and main process via CDP and Node inspector.
Instructions
Spawn an Electron application via the electron binary with --remote-debugging-port and --inspect flags set so the MCP can drive the renderer and main process. Use launch_via_npm instead for electron-forge projects; this tool is for apps that don't need the forge dev-server (or for packaged test builds).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| env | No | Environment variables overlaid on the MCP process env. | |
| name | No | Display name for the session (defaults to appPath's basename). | |
| appPath | Yes | Path to the Electron app. May be absolute or relative to the MCP process's cwd. Points at the folder that contains `package.json` in dev, or an unpackaged .app/.exe bundle in test. | |
| debugPort | No | CDP port for renderers (default: auto-pick in 9222-9999). | |
| inspectPort | No | Node inspector port for the main process (default: auto-pick). | |
| electronArgs | No | Extra args passed to Electron after the app path. | |
| waitTimeoutMs | No | How long to wait for both debug ports to become live (default 30000). | |
| electronBinary | No | Override the Electron executable (defaults to the project-local `node_modules/.bin/electron`, falling back to `electron` on PATH). |