Electron MCP Server

Electron MCP server enabling AI agents to interact with Electron desktop applications — controlling Electron app windows and UI, executing browser context operations, accessing Electron's main and renderer processes, automating Electron-based desktop apps (VS Code, Slack, Discord, etc.), and integrating Electron app automation into agent-driven desktop workflow automation.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Developer Tools electron desktop mcp-server cross-platform nodejs chromium desktop-automation
⚙ Agent Friendliness
68
/ 100
Can an agent use this?
🔒 Security
74
/ 100
Is it safe for agents?
⚡ Reliability
60
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
60
Documentation
62
Error Messages
60
Auth Simplicity
88
Rate Limits
85

🔒 Security

TLS Enforcement
80
Auth Strength
75
Scope Granularity
65
Dep. Hygiene
65
Secret Handling
80

Local Electron. DevTools exposed — restrict access. Check app ToS. No MCP credentials. Community MCP.

⚡ Reliability

Uptime/SLA
62
Version Stability
58
Breaking Changes
58
Error Recovery
60
AF Security Reliability

Best When

An agent needs to automate or control an Electron-based desktop application — Electron's Chromium foundation enables automation via similar techniques to browser automation.

Avoid When

Your target apps are native (Swift, .NET WinForms, Qt) rather than Electron-based.

Use Cases

  • Automating Electron-based desktop apps (VS Code, Slack, Figma) from productivity agents
  • Testing Electron app UI without manual interaction from QA agents
  • Controlling Electron app state and configuration from automation agents
  • Building AI assistants for specific Electron apps from application agents
  • Automating repetitive tasks in Electron desktop apps from efficiency agents
  • Cross-platform desktop automation for Electron apps from DevOps agents

Not For

  • Native Windows/macOS apps not built with Electron (use platform-specific UIAutomation MCPs)
  • Web browser automation (use Playwright or Puppeteer MCPs for browsers)
  • Electron apps without DevTools or debug access

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: none
OAuth: No Scopes: No

No authentication — communicates with Electron app via DevTools protocol or app-specific IPC. Target Electron app must be running.

Pricing

Model: free
Free tier: Yes
Requires CC: No

Free, open source community MCP.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • Target Electron app must be running with DevTools remote debugging enabled
  • App-specific automation logic may require app-specific knowledge (UI selectors, event names)
  • Electron version and app internals affect what automation is possible
  • Community MCP with limited documentation — significant setup exploration required
  • Automating apps like Slack/Discord may violate their ToS — check before automating
  • UI element selectors can change with app updates — fragile automation a common issue

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Electron MCP Server.

$99

Scores are editorial opinions as of 2026-03-06.

5215
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered