@yawlabs/electron-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Electron development knowledge. Every tool is read-only and pure over its arguments: it reads no project file, runs nothing and makes no network call, so pass the code, config or error text to analyze as a string argument.
Routing:
Reviewing existing code: electron_audit_security, electron_lint_security, electron_audit_ipc_security, electron_audit_performance.
Writing new code or config: electron_scaffold_project, electron_scaffold_ipc_channel, electron_generate_preload_bridge, electron_generate_window_manager, electron_configure_csp, electron_configure_fuses, electron_configure_auto_update, electron_configure_deep_linking.
Upgrading Electron: electron_migrate_version for a version-to-version checklist, electron_check_deprecated_apis to scan code for removed or deprecated APIs.
Build or packaging failures: electron_diagnose_build_error with the error output.
Concepts: electron_explain_process_model, electron_explain_concept.
electron_knowledge_version reports which Electron releases the embedded knowledge covers.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| electron_scaffold_ipc_channelA | 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. |
| electron_generate_preload_bridgeA | 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. |
| electron_audit_ipc_securityB | 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. |
| electron_generate_window_managerB | 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. |
| electron_explain_process_modelA | 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. |
| electron_audit_securityA | 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, 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. |
| electron_configure_fusesA | 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. |
| electron_configure_cspA | 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. |
| electron_lint_securityA | 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. |
| electron_diagnose_build_errorA | 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. |
| electron_configure_auto_updateB | 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. |
| electron_configure_deep_linkingA | 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. |
| electron_scaffold_projectB | 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. |
| electron_migrate_versionA | 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. |
| electron_check_deprecated_apisA | 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. |
| electron_audit_performanceA | 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. |
| electron_explain_conceptA | 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. |
| electron_knowledge_versionA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Most tools have a clearly distinct action and resource, and the security tools are separated by scope (general checklist, lint patterns, IPC-specific, performance). However, electron_explain_concept overlaps with electron_explain_process_model, and the multiple audit/lint tools could still cause some hesitation.
All tools use a consistent electron_ prefix and snake_case, and nearly all follow a verb_noun pattern (explain, scaffold, generate, audit, configure, lint, diagnose, migrate, check). The main deviation is electron_knowledge_version, which is noun-based rather than verb-based.
18 tools is slightly above the typical 3-15 range, but the broad Electron development domain justifies the surface. Each tool maps to a distinct workflow area such as scaffolding, security, configuration, migration, or diagnosis, so the count is reasonable rather than bloated.
The tool set covers a wide Electron lifecycle: concepts, scaffolding, IPC/preload generation, security audits, performance auditing, build diagnosis, auto-update, deep linking, migration, and deprecation checks. Minor gaps remain around explicit packaging/code-signing configuration generation and testing support, but agents can work around them.