electron-test-mcp
Allows testing Electron applications by connecting to a running app via CDP or launching a new instance, with tools for interaction (click, fill, type, hover, press, drag, selectOption), inspection (screenshot, snapshot, getText, getAttribute, isVisible, count), and advanced operations (wait, evaluate, evaluateMain in launch mode).
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@electron-test-mcpTake a screenshot of the Electron app and list all interactive elements"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Electron Test MCP
MCP (Model Context Protocol) server for testing Electron applications using Playwright. Enables AI models like Claude to interact with and test your Electron apps.
🚀 Quick Start
# Run directly with npx
npx electron-test-mcp
# Or install globally
npm install -g electron-test-mcp
electron-test-mcpRelated MCP server: electron-mcp-server
Features
Two Connection Modes
CDP Mode: Connect to a running Electron app via Chrome DevTools Protocol
Launch Mode: Launch a fresh Electron app instance for testing
Full Playwright API: screenshot, click, fill, type, hover, press, wait, evaluate, and more
Accessibility Snapshots: Get the accessibility tree for element discovery
Main Process Access: Execute code in Electron's main process (launch mode only)
How It Works
User <--> AI Model (Claude) <--> MCP Protocol <--> electron-test-mcp <--> Electron AppUser: "Click the login button and fill in the email field"
AI Model: Determines which MCP tools to use
MCP Protocol: Standardized communication
electron-test-mcp: Executes Playwright commands on the Electron app
Electron App: Actions are performed in the actual application
Configuration
Claude Desktop / MCP Clients
Add to your MCP configuration file:
{
"mcpServers": {
"electron-test": {
"command": "npx",
"args": ["electron-test-mcp"]
}
}
}OpenCode
{
"mcp": {
"electron-test": {
"type": "local",
"command": ["npx", "electron-test-mcp"],
"enabled": true
}
}
}Connection Modes
CDP Mode (Recommended for Development)
Connect to an already running Electron app with remote debugging enabled:
# Start your Electron app with debugging port
electron your-app --remote-debugging-port=9222
# Or with electron-vite
electron-vite dev -- --remote-debugging-port=9222Then use the connect tool:
connect({ port: 9222 })Advantages:
Works with your existing dev workflow
App state preserved between tests
Hot reload still works
Launch Mode
Launch a fresh Electron app instance:
launch({ appPath: "./out/main/index.js" })
# With headless mode for CI
launch({ appPath: "./out/main/index.js", headless: true })Advantages:
Clean state for each test
Access to main process via
evaluateMainCan pass custom environment variables
Supports headless mode for CI/automation
Headless Mode (CI/Automation)
Launch Mode
Pass headless: true to run without a visible window:
launch({ appPath: "./out/main/index.js", headless: true })CDP Mode
Start your Electron app with headless flags before connecting:
# Option 1: Electron headless flag (Electron 28+)
electron your-app --headless=new --remote-debugging-port=9222
# Option 2: xvfb (Linux) - virtual framebuffer
xvfb-run electron your-app --remote-debugging-port=9222
# Option 3: xvfb with specific display (CI environments)
Xvfb :99 -screen 0 1920x1080x24 &
DISPLAY=:99 electron your-app --remote-debugging-port=9222Then connect normally:
connect({ port: 9222 })Available Tools
Connection
Tool | Description |
| Connect to running app via CDP |
| Disconnect from CDP (app keeps running) |
| Launch new Electron app instance |
| Close launched app |
Interaction
Tool | Description |
| Click an element |
| Fill text into input (clears first) |
| Type text character by character |
| Hover over an element |
| Press keyboard key |
| Drag and drop |
| Select from dropdown |
Inspection
Tool | Description |
| Take screenshot (returns base64 image) |
| Get accessibility tree |
| Get element text content |
| Get element attribute |
| Check if element is visible |
| Count matching elements |
Advanced
Tool | Description |
| Wait for element state |
| Run JS in renderer process |
| Run code in main process (launch mode only) |
Selectors
Supports all Playwright selectors:
# CSS selectors
[data-testid="submit-btn"]
.my-class
#my-id
# Text selectors
text=Submit
text="Exact Match"
# Role selectors
role=button[name="Submit"]
# Combining
.form >> text=SubmitUsage Examples
Basic Test Flow
1. connect({ port: 9222 })
2. snapshot() // See the page structure
3. click('[data-testid="login-btn"]')
4. fill('[data-testid="email"]', 'test@example.com')
5. fill('[data-testid="password"]', 'password123')
6. click('text=Sign In')
7. wait({ selector: '[data-testid="dashboard"]' })
8. screenshot()Main Process Access (Launch Mode)
// Get app version
evaluateMain({
script: "({ app }) => app.getVersion()",
});
// Show dialog
evaluateMain({
script: "({ dialog }) => dialog.showMessageBox({ message: 'Hello!' })",
});With AI Assistant
You can ask Claude or other AI assistants to test your Electron app:
Connect to my Electron app running on port 9222 and:
1. Take a screenshot of the current state
2. Click the "Settings" button in the sidebar
3. Change the theme to dark mode
4. Verify the theme changed by checking the background colorTips for Testable Electron Apps
Add
data-testidattributes to important elementsEnable remote debugging in development:
--remote-debugging-port=9222Use semantic HTML for better accessibility snapshots
Keep selectors stable - prefer
data-testidover classes
Development
# Clone repository
git clone https://github.com/lazy-dinosaur/electron-test-mcp.git
cd electron-test-mcp
# Install dependencies
npm install
# Build
npm run build
# Run locally
node dist/index.js🤝 Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
📄 License
Distributed under the MIT License. See LICENSE file for more information.
❤️ Support
If you find this project useful, please consider giving it a ⭐️ on GitHub!
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lazy-dinosaur/electron-test-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server