Verify whether Electron advice is current by retrieving the embedded knowledge's last verification date, stable version, and supported migration range.
MIT
649,985 tools. Updated 2026-10-10 03:25
"electron-builder" matching MCP tools:
- Generate @electron/fuses configuration to disable dangerous runtime features, locking them against user re-enablement. Set recommended, strict, or custom security levels to harden your Electron app.MIT
- Scan Electron source code to detect dangerous patterns: shell.openExternal with user input, disabled webSecurity, missing navigation restrictions, and unrestricted window creation. Fix OWASP-style vulnerabilities before deployment.MIT
- Diagnose Electron build/packaging errors from electron-builder/forge/packager. Pinpoints code signing, native module, ASAR, platform config, and __dirname path issues.MIT
- Configure custom protocol deep linking in Electron apps: handles URL routing, single/multi-instance modes, and platform-specific settings for macOS, Windows, and Linux.MIT
- Run preflight checks on Node, Playwright, Electron, and environment settings without launching Electron. Inspect failures and warnings before starting a session.MIT
Matching MCP Servers
- AlicenseAqualityAmaintenanceDrive, inspect, and assert on real Electron desktop apps from an AI agent — agent-native, Playwright-style automation with accessibility refs, stable error codes, and retrying assertions559MIT
- AlicenseAqualityDmaintenanceMCP server for interacting with and debugging Electron apps, providing tools for window automation, IPC, logs, and main-process state via CDP and Node inspector.2010 npmMIT
Matching MCP Connectors
Turn an idea or meeting transcript into a working single-file AI agent, check it, use it right away.
Idea to buildable dApp spec
- Execute JavaScript code in the Electron main process to access system resources, invoke IPC handlers, and control application windows beyond renderer limitations.MIT
- Spawns an Electron application with debugging ports enabled, allowing control of both the renderer and main process via CDP and Node inspector.MIT
- Spawn an Electron application by running an npm script, forwarding debug ports for remote debugging. Designed for electron-forge projects where the dev server starts first.MIT
- Evaluate JavaScript expressions in an Electron app's main process via the inspector protocol, accessing APIs like require('electron').MIT
- Retrieve details about running Electron applications and their windows, including child windows, by leveraging remote debugging on port 9222. Ideal for automation and debugging workflows.MIT
- Shut down a launched Electron app after testing. Only works with launch mode, not CDP connection.MIT
- Retrieve all active Electron testing sessions to monitor running automated tests and identify available automation targets.MIT
- Simulate a mouse press on a specified element in an Electron app to trigger UI interactions during automated testing.MIT
- Minimize the Electron main window to reduce visual interference during automated testing.MIT
- Connect to a running Electron app via Chrome DevTools Protocol to enable automated testing.MIT
- Load a URL in an Electron app session to test page content and user interactions.MIT
- Execute JavaScript in the Electron main process to automate testing and control application lifecycle and interactions.MIT
- Starts an Electron application for automated testing by specifying its executable path, with options for arguments, headless mode, and slow-motion timing.MIT
- Run JavaScript in an Electron app session to automate testing and interact with UI elements.MIT
- Enlarges the Electron app's main window to its maximum size so automated UI tests can access all elements and controls.MIT