io.github.YawLabs/electron-mcp
NPM · @YAWLABS/ELECTRON-MCP · SCANNED AUG 5
Electron.js MCP server — IPC scaffolding, security auditing, build tooling for AI assistants
Available components
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. How we score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @yawlabs/electron-mcp
claude mcp add yawlabs-electron-mcp -- npx -y @yawlabs/electron-mcp
codex mcp add yawlabs-electron-mcp -- npx -y @yawlabs/electron-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yawlabs-electron-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@yawlabs/electron-mcp"
],
"enabled": true
}
}
} openclaw mcp add yawlabs-electron-mcp --command npx --arg -y --arg @yawlabs/electron-mcp
mcp_servers:
yawlabs-electron-mcp:
command: "npx"
args: ["-y", "@yawlabs/electron-mcp"] {
"mcpServers": {
"yawlabs-electron-mcp": {
"command": "npx",
"args": [
"-y",
"@yawlabs/electron-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Aug 26 +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.
- 3 Aug 26 +4
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Aug 26 −8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 +33
- 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 functional
- 26 Jul 26 41
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Aug 2026 · Analysed npm/@yawlabs/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 0 packages
0 packages in the resolved dependency tree.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
electron_audit_ipc_security ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
electron_audit_performance ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
electron_audit_security ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
electron_check_deprecated_apis ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Source code to scan for deprecated API usage |
| electronVersion | integer | — | Current Electron major version to determine what's deprecated (default: 41) |
No output schema declared.
No examples provided.
electron_configure_auto_update ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Update distribution method: 'github' (GitHub Releases), 's3' (AWS S3), 'generic' (any HTTP server) |
| s3Bucket | string | — | S3 bucket name (for 's3' provider) |
No output schema declared.
No examples provided.
electron_configure_csp ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
electron_configure_deep_linking ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| protocol | string | yes | 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) |
No output schema declared.
No examples provided.
electron_configure_fuses ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customFuses | object | — | Individual fuse settings (only for 'custom' level) |
| level | string | yes | 'recommended' for sensible defaults, 'strict' for maximum security, 'custom' to specify each fuse individually |
No output schema declared.
No examples provided.
electron_diagnose_build_error ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| buildTool | string | — | Which build tool produced the error. Defaults to 'unknown' (auto-detect). |
| errorOutput | string | yes | The build error output (stderr/stdout) to diagnose |
| platform | string | — | Target platform. Defaults to 'unknown' (auto-detect). |
No output schema declared.
No examples provided.
electron_explain_concept ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| concept | string | yes | The Electron concept to explain |
No output schema declared.
No examples provided.
electron_explain_process_model ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| electronVersion | string | — | Target Electron version for version-specific guidance (e.g. '28', '33', '41'). Defaults to latest. |
| topic | string | yes | Which aspect of the process model to explain |
No output schema declared.
No examples provided.
electron_generate_preload_bridge ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| methods | array | yes | Array of methods to expose through the preload bridge |
| namespace | string | — | The property name on window, e.g. 'electronAPI'. Defaults to 'electronAPI'. |
No output schema declared.
No examples provided.
electron_generate_window_manager ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| persistState | boolean | — | Whether to persist window positions/sizes across restarts (default true) |
| windows | array | yes | Windows to manage |
No output schema declared.
No examples provided.
electron_knowledge_version ~72
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
electron_lint_security ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Source code to analyze (main process, preload, or renderer) |
| fileType | string | — | Which process this code runs in. Helps scope the analysis. Defaults to 'main'. |
No output schema declared.
No examples provided.
electron_migrate_version ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currentVersion | integer | yes | Current Electron major version (e.g. 28) |
| targetVersion | integer | yes | Target Electron major version (e.g. 41) |
No output schema declared.
No examples provided.
electron_scaffold_ipc_channel ~232
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The IPC channel name, e.g. 'get-user-data', 'save-settings', 'open-file-dialog' |
| description | string | yes | What this IPC channel does, e.g. 'Fetches user profile from the database' |
| direction | string | yes | 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. |
No output schema declared.
No examples provided.
electron_scaffold_project ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| buildTool | string | — | Build tool. Defaults to 'electron-vite'. |
| features | array | — | Optional features to include |
| framework | string | — | Frontend framework. Defaults to 'react'. |
| name | string | yes | Project name (lowercase, hyphens ok), e.g. 'my-electron-app' |
No output schema declared.
No examples provided.