Electron Mcp
Scaffold Electron IPC, run security audits, and use build helpers while your agent implements a desktop app.
Overview
io.github.YawLabs/electron-mcp is a Build-phase MCP server for Electron IPC scaffolding, security auditing, and build tooling.
What is this MCP server?
- Electron-focused MCP: IPC scaffolding, security auditing, and build tooling
- @yawlabs/electron-mcp v1.2.9 with stdio transport
- Helps agents follow safer preload and IPC boundaries
- Supports indie desktop SaaS, devtools, and internal utilities
- npm package @yawlabs/electron-mcp for standard MCP hosts
- Published server version 1.2.9
- stdio MCP transport per server schema
What problem does it solve?
Agents default to web-app patterns and miss Electron-specific IPC, preload safety, and packaging steps.
Who is it for?
Solo builders creating Electron desktop products who want agent assistance with IPC and security basics.
Skip if: Pure web or mobile-only stacks with no Electron dependency.
What do I get? / Deliverables
Your agent can generate safer Electron structure and run MCP-backed audits and build helpers aligned with desktop apps.
- IPC and project scaffolding suggestions via MCP tools
- Security audit signals for common Electron misconfigurations
- Build-oriented agent workflows for packaging iterations
Recommended MCP Servers
Journey fit
How it compares
Electron-specialized MCP tooling, not a generic browser automation or AWS integration server.
Common Questions / FAQ
Who is io.github.YawLabs/electron-mcp for?
Developers building Electron desktop apps with AI coding agents who need IPC scaffolding and security-aware guidance.
When should I use io.github.YawLabs/electron-mcp?
Use it during Electron feature build-out, when wiring main/renderer IPC, or before ship when you want security-oriented checks.
How do I add io.github.YawLabs/electron-mcp to my agent?
Install @yawlabs/electron-mcp from npm, register stdio MCP in your editor config, and open your Electron project so tools target the app’s structure.