# io.github.YawLabs/electron-mcp (npm · @yawlabs/electron-mcp)

Electron.js MCP server — IPC scaffolding, security auditing, build tooling for AI assistants

- Trust score: 68/100 (medium)
- Change this week: −6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-05

## Components

- npm · `@yawlabs/electron-mcp`: 68/100 (this document), [markdown](https://verifymcp.io/servers/yawlabs-electron-mcp/yawlabs-electron-mcp.md), [page](https://verifymcp.io/servers/yawlabs-electron-mcp/yawlabs-electron-mcp)

## Channel facts

- Registry: `npm`
- Package: `@yawlabs/electron-mcp`
- Version: `1.2.15`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 14 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2307 tokens (~128/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add yawlabs-electron-mcp -- npx -y @yawlabs/electron-mcp
```

### Codex

```bash
codex mcp add yawlabs-electron-mcp -- npx -y @yawlabs/electron-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yawlabs-electron-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@yawlabs/electron-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yawlabs-electron-mcp --command npx --arg -y --arg @yawlabs/electron-mcp
```

### Hermes

```yaml
mcp_servers:
  yawlabs-electron-mcp:
    command: "npx"
    args: ["-y", "@yawlabs/electron-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "yawlabs-electron-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@yawlabs/electron-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-05 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-03 (score 67, +4)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-02 (score 63, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-08-01 (score 48, −8)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 56, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 74, +33)

- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent

### 2026-07-26 (score 41)

First indexed and scored.

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (18)

### `electron_scaffold_ipc_channel` (~232 tokens)

Generate complete IPC boilerplate for a new feature: ipcMain handler in the main process, preload bridge function with contextBridge, TypeScript type declarations, and renderer-side usage example. Produces all the files needed for a secure, type-safe IPC channel.

Input parameters:

- `apiNamespace` (string): The namespace on window.electronAPI to group this under, e.g. 'users', 'settings'. Defaults to 'api'.
- `args` (string): TypeScript type for the arguments, e.g. '{ userId: string }' or 'string'. Omit for no arguments.
- `channelName` (string, required): The IPC channel name, e.g. 'get-user-data', 'save-settings', 'open-file-dialog'
- `description` (string, required): What this IPC channel does, e.g. 'Fetches user profile from the database'
- `direction` (string, required): Communication direction for the channel
- `returnType` (string): TypeScript type for the return value (renderer-to-main only), e.g. '{ name: string; email: string }'. Omit for void.

### `electron_generate_preload_bridge` (~109 tokens)

Generate a complete, secure preload.ts with contextBridge.exposeInMainWorld for multiple API methods. Produces the preload script, TypeScript declarations for window.electronAPI, and security best practices. Use this when you need to expose several main-process APIs to the renderer at once.

Input parameters:

- `methods` (array, required): Array of methods to expose through the preload bridge
- `namespace` (string): The property name on window, e.g. 'electronAPI'. Defaults to 'electronAPI'.

### `electron_audit_ipc_security` (~124 tokens)

Analyze preload script and main process IPC code for security issues. Checks for: raw ipcRenderer exposure, missing sender validation, synchronous IPC usage, listener memory leaks, prototype pollution via contextBridge, and insecure channel patterns. Provide the actual code content to analyze.

Input parameters:

- `mainCode` (string): Content of the main process IPC handler code to analyze
- `preloadCode` (string): Content of the preload script (preload.ts/js) to analyze
- `rendererCode` (string): Content of renderer code that uses IPC, to check for anti-patterns

### `electron_generate_window_manager` (~89 tokens)

Generate multi-window management boilerplate for Electron apps. Creates a WindowManager class that handles window lifecycle, inter-window communication, window state persistence, and proper cleanup. Supports common patterns like main + child windows, modal dialogs, and detached panels.

Input parameters:

- `persistState` (boolean): Whether to persist window positions/sizes across restarts (default true)
- `windows` (array, required): Windows to manage

### `electron_explain_process_model` (~103 tokens)

Get a clear, version-aware explanation of Electron's multi-process architecture. Covers the main process, renderer processes, preload scripts, utility processes, contextBridge, and how they interact. Useful for understanding the mental model before building features.

Input parameters:

- `electronVersion` (string): Target Electron version for version-specific guidance (e.g. '28', '33', '41'). Defaults to latest.
- `topic` (string, required): Which aspect of the process model to explain

### `electron_audit_security` (~269 tokens)

Audit an Electron app against the official security checklist. Covers 19 of the items that can be detected from static inputs (BrowserWindow configuration, main process code, package.json, preload, HTML): HTTPS-only content, nodeIntegration, contextIsolation, sandbox, webSecurity, CSP, allowRunningInsecureContent, experimentalFeatures, enableBlinkFeatures, raw ipcRenderer exposure, direct window assignment, @electron/remote, supported Electron version, shell.openExternal validation, file:// usage, <webview> tag, will-navigate handler, setWindowOpenHandler, and IPC sender validation. The remaining checklist items (session permissions, fuse configuration) require runtime / packaging context and are flagged in the report's footer.

Input parameters:

- `browserWindowConfig` (string): BrowserWindow constructor options as a JSON string or code snippet
- `electronVersion` (string): Electron major version if not in package.json (e.g. '41')
- `htmlContent` (string): Content of the main HTML file to check CSP meta tags
- `mainCode` (string): Main process code -- used to detect non-HTTPS URLs in loadURL/loadFile calls
- `packageJson` (string): Content of package.json to check Electron version and dependencies
- `preloadCode` (string): Content of the preload script

### `electron_configure_fuses` (~109 tokens)

Generate @electron/fuses configuration to harden your Electron app. Fuses are compile-time toggles that disable dangerous Electron features (like ELECTRON_RUN_AS_NODE, NODE_OPTIONS) and cannot be re-enabled by end users. Essential for production apps.

Input parameters:

- `customFuses` (object): Individual fuse settings (only for 'custom' level)
- `level` (string, required): 'recommended' for sensible defaults, 'strict' for maximum security, 'custom' to specify each fuse individually

### `electron_configure_csp` (~188 tokens)

Generate a Content Security Policy for an Electron app. Accounts for the bundler (Vite, webpack), framework (React, Vue, Svelte), and whether dev-mode exceptions are needed. Returns both meta-tag and session.webRequest approaches.

Input parameters:

- `bundler` (string): Bundler used (affects script-src for HMR in dev mode). Defaults to 'vite'.
- `externalConnections` (array): External origins the app connects to, e.g. ['https://api.example.com', 'wss://ws.example.com']
- `externalImages` (array): External origins for images, e.g. ['https://cdn.example.com']
- `needsEval` (boolean): Whether eval() is needed (some template compilers). Defaults to false.
- `needsInlineStyles` (boolean): Whether inline styles are required (e.g. CSS-in-JS). Defaults to false.

### `electron_lint_security` (~97 tokens)

Static analysis of Electron code for dangerous patterns: shell.openExternal with user input, @electron/remote usage, disabled webSecurity, missing navigation restrictions, unrestricted window creation, and other OWASP-style vulnerabilities specific to Electron.

Input parameters:

- `code` (string, required): Source code to analyze (main process, preload, or renderer)
- `fileType` (string): Which process this code runs in. Helps scope the analysis. Defaults to 'main'.

### `electron_diagnose_build_error` (~126 tokens)

Diagnose Electron build/packaging errors from electron-builder, electron-forge, or electron-packager output. Identifies common failures: code signing errors, native module rebuild issues, ASAR packaging problems, missing platform-specific configuration, and __dirname path resolution bugs.

Input parameters:

- `buildTool` (string): Which build tool produced the error. Defaults to 'unknown' (auto-detect).
- `errorOutput` (string, required): The build error output (stderr/stdout) to diagnose
- `platform` (string): Target platform. Defaults to 'unknown' (auto-detect).

### `electron_configure_auto_update` (~196 tokens)

Generate complete auto-update configuration using electron-updater. Produces main process setup, update event handling, renderer notification UI code, and platform-specific signing requirements. Supports GitHub releases, S3, and generic HTTP update servers.

Input parameters:

- `autoDownload` (boolean): Automatically download updates (default true)
- `autoInstallOnQuit` (boolean): Install update on app quit (default true)
- `genericUrl` (string): Base URL for updates (for 'generic' provider)
- `githubOwner` (string): GitHub owner (for 'github' provider)
- `githubRepo` (string): GitHub repo name (for 'github' provider)
- `provider` (string, required): Update distribution method: 'github' (GitHub Releases), 's3' (AWS S3), 'generic' (any HTTP server)
- `s3Bucket` (string): S3 bucket name (for 's3' provider)

### `electron_configure_deep_linking` (~124 tokens)

Generate complete custom protocol / deep linking setup for Electron. Produces protocol registration, URL handling in both single-instance and multi-instance modes, platform-specific configuration (macOS Info.plist, Windows registry, Linux .desktop), and electron-builder/forge config.

Input parameters:

- `protocol` (string, required): Custom protocol scheme, e.g. 'myapp' (will handle myapp:// URLs)
- `routes` (array): Routes to handle within the protocol
- `singleInstance` (boolean): Enforce single instance -- new URLs focus the existing window (default true)

### `electron_scaffold_project` (~124 tokens)

Generate a complete, secure, modern Electron project scaffold. Includes proper process separation, TypeScript configuration, framework integration, build tooling, security defaults, and an example IPC channel. Produces a full project structure ready to develop.

Input parameters:

- `buildTool` (string): Build tool. Defaults to 'electron-vite'.
- `features` (array): Optional features to include
- `framework` (string): Frontend framework. Defaults to 'react'.
- `name` (string, required): Project name (lowercase, hyphens ok), e.g. 'my-electron-app'

### `electron_migrate_version` (~75 tokens)

Generate a migration checklist for upgrading between Electron versions. Lists all breaking changes, deprecated APIs, and required code modifications between the current and target versions.

Input parameters:

- `currentVersion` (integer, required): Current Electron major version (e.g. 28)
- `targetVersion` (integer, required): Target Electron major version (e.g. 41)

### `electron_check_deprecated_apis` (~79 tokens)

Scan code for usage of deprecated or removed Electron APIs. Returns a list of deprecated APIs found with their replacements and the version they were deprecated/removed in.

Input parameters:

- `code` (string, required): Source code to scan for deprecated API usage
- `electronVersion` (integer): Current Electron major version to determine what's deprecated (default: 41)

### `electron_audit_performance` (~119 tokens)

Analyze Electron app code for 7 official performance anti-patterns: eager module loading, synchronous main-process operations, excessive BrowserWindows at startup, unnecessary polyfills, CDN-loaded assets, heavy preload scripts, and unbundled dependencies. Returns specific fixes.

Input parameters:

- `mainCode` (string): Main process code to analyze
- `packageJson` (string): package.json content to check for bundling and dependencies
- `preloadCode` (string): Preload script code to analyze
- `rendererCode` (string): Renderer process code to analyze

### `electron_explain_concept` (~72 tokens)

Get a clear, authoritative explanation of an Electron concept. Counters outdated tutorial content with accurate, version-aware information. Covers: process model, context isolation, sandbox, IPC, ASAR, fuses, code signing, and build tool comparison.

Input parameters:

- `concept` (string, required): The Electron concept to explain

### `electron_knowledge_version` (~72 tokens)

Return metadata about the embedded Electron knowledge used by this MCP's analysis tools -- the date it was last verified against official Electron docs, the current Electron stable version at that time, and the supported version range for migration/deprecation checks. Call this when you need to know whether the advice from other tools is current.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/yawlabs-electron-mcp/yawlabs-electron-mcp#diagnostics

## Score history

- 2026-08-05: 68
- 2026-08-04: 67
- 2026-08-03: 67
- 2026-08-02: 63
- 2026-08-01: 48
- 2026-07-31: 56
- 2026-07-29: 74
- 2026-07-28: 74
- 2026-07-27: 74
- 2026-07-26: 41

## Links

- npm package: https://www.npmjs.com/package/@yawlabs/electron-mcp
- Socket report: https://socket.dev/npm/package/@yawlabs/electron-mcp
- Changelog RSS feed: https://verifymcp.io/servers/yawlabs-electron-mcp/yawlabs-electron-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/yawlabs-electron-mcp/yawlabs-electron-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/yawlabs-electron-mcp/yawlabs-electron-mcp