
by YawLabs
Electron MCP is an MCP server from Yaw Labs that gives AI coding assistants structured knowledge about Electron: IPC scaffolding, security audits, build-error diagnosis and version migration. It is for developers building Electron apps with an assistant.
PluginContact for pricing
Step 1: Add an electron server entry to .mcp.json in your project root, using npx with -y @yawlabs/electron-mcp@latest.
Step 2: On Windows, wrap the call as cmd with args /c npx -y @yawlabs/electron-mcp@latest.
Step 3: Restart Claude Code or your MCP client and approve the server when prompted.
Step 4: Ask your assistant to audit your BrowserWindow config or add a file picker with a secure IPC bridge.
Step 5: Paste build output or your Electron version change to get a diagnosis or migration checklist.
No. There are no API keys or environment variables to set up. You only add the server entry to your MCP client config.
No. It gives your assistant structured answers about Electron and checks code you pass in. It does not run code or touch your filesystem.
The maker lists Claude Code, Claude Desktop, Cursor, Windsurf and VS Code. The same server entry is used in each, with a different config file.
Yes, with a small config change. On Windows the npx call is wrapped in cmd /c, while macOS, Linux and WSL use the plain npx entry.
Requirements
CtxLint MCPctxlint checks AI agent context files and MCP server configs against your real codebase and flags drift before your agent acts on it. It runs as a CLI, CI step, pre-commit hook or MCP server.
YawLabs AWS MCP@yawlabs/aws-mcp is a small MCP server that calls AWS through your local aws CLI, with built-in SSO re-login, generic resource CRUD and live docs lookup. It is presented as an alternative to AWS's own MCP server.
Caddy MCPAn MCP server from Yaw Labs for managing Caddy web servers through Caddy's admin API. It provides 18 tools and 4 resources for config, routes, reverse proxies, TLS, PKI and metrics.