@yawlabs/electron-mcp
OfficialRelated Servers
Alternatives to @yawlabs/electron-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with 28 developer tools across file, git, code analysis, HTTP, and system domains, enabling tasks like file editing, repository management, code analysis, and shell command execution.2MIT
- AlicenseCqualityDmaintenanceEquips AI coding agents with 62 production-grade tools across 28 modules for persistent memory, live GitHub scouting, UI/UX design, DevOps, security, performance auditing, and SEO/AEO/GEO optimization, enabling automated, development workflows.631MIT
- AlicenseNot gradedqualityNot gradedmaintenanceProvides unified development tools including code analysis, debugging, refactoring, documentation, testing, and project automation through multiple LLM providers (KIMI, GLM, OpenRouter). Features agentic audit capabilities with multi-model consensus for finding issues and generating direct fixes.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with 25 security analysis tools including vulnerability scanning, package hallucination detection, prompt injection firewall, and CI/CD integration.1MIT
- AlicenseAqualityDmaintenanceProvides AI assistants with frontend development tools including component scaffolding, bundle analysis, accessibility checks, and responsive design guidance. Enables automated generation of React components with tests and stories, bundle optimization recommendations, and WCAG compliance fixes.6MIT
- AlicenseNot gradedqualityCmaintenanceProvides 13 MCP tools for codebase analysis, wiki generation, and knowledge mapping, enabling AI assistants to understand project structure and context efficiently.3,835 npm1,427MIT
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.