Selenix MCP

ConnectClaude DesktoptoSelenixvia the Model Context Protocol. Chat with Claude to create, run, debug, and manage browser automation tests — just like using the built-in AI Assistant, but powered by Claude.

- Selenixdesktop app installed
- Claude Desktopinstalled
- Node.js18 or later

{ "mcpServers": { "selenix": { "command": "node", "args": ["<npm-root-path>/@selenix/mcp-server/dist/bundle.js"] } } }

{ "mcpServers": { "selenix": { "command": "node", "args": ["C:/Users/YourName/AppData/Local/nvm/v18.20.8/node_modules/@selenix/mcp-server/dist/bundle.js"] } } }

{ "mcpServers": { "selenix": { "command": "node", "args": ["/usr/local/lib/node_modules/@selenix/mcp-server/dist/bundle.js"] } } }

If you already have other MCP servers configured, add"selenix"alongside them inside the existing"mcpServers"object.

Option B: Use the bundled version (no npm required)

If you installed Selenix as a desktop app, the MCP server is already bundled. No need to install anything — just point Claude Desktop to the bundled file.

Find your Selenix install folder and look forresources/mcp-server/index.js, then add to your Claude Desktop config:

{ "mcpServers": { "selenix": { "command": "node", "args": ["C:/path/to/Selenix/resources/mcp-server/index.js"] } } }

C:/Users/YourName/AppData/Local/Programs/Selenix/resources/mcp-server/index.js

- Downloadbundle.jsfrom thenpm package pageor from thereleases page
- Save it somewhere on your machine (e.g.,C:/selenix-mcp/bundle.js)
- Add to your Claude Desktop config:

{ "mcpServers": { "selenix": { "command": "node", "args": ["C:/selenix-mcp/bundle.js"] } } }

Node.js is still required — the MCP server is a single JavaScript file with no other dependencies.

Restart Claude Desktop after editing the config. You should see the Selenix tools icon (hammer) in the chat input area.

- "What tests are in my Selenix project?"
- "Create a test that opens google.com and searches for 'selenium automation'"
- "Run the current test and fix any failures"
- "Take a screenshot of the browser"

Claude Desktop <--stdio--> MCP Server <--HTTP--> Bridge Server (inside Selenix)

The MCP server translates Claude's tool calls into HTTP requests to a bridge server running inside Selenix. The bridge has full access to Selenix internals — the same capabilities as the built-in AI Assistant.

- The bridge only listens on127.0.0.1(localhost) — no network exposure
- Auth is handled via a bearer token auto-generated each time Selenix starts
- Connection config is stored at~/.selenix/bridge.jsonand re-read on every call, so restarting Selenix does not require restarting Claude Desktop

"Cannot read Selenix bridge config"Selenix isn't running or the MCP Server isn't enabled. Open Selenix → System Settings → set Enable MCP Server to Yes.

"Cannot connect to Selenix bridge"Selenix may have just restarted. Try the request again — the MCP server will automatically pick up the new connection details.

Tools not appearing in Claude DesktopMake sure you restarted Claude Desktop after editing the config file. Verify the config JSON is valid (no trailing commas, correct brackets).

Claude Desktop won't open after config changeThe config JSON is likely malformed. Open the config file in a text editor, fix the JSON syntax, and try again. Common issues: missing comma between entries, trailing comma after the last entry.

Then remove the"selenix"entry from your Claude Desktop config file and restart Claude Desktop.

Official Playwright MCP server for browser automation, page inspection, screenshots, and web interaction from Claude, Cursor, and other AI agents.

Render website screenshots with ScreenshotOne

Attaches to existing browser sessions using the Chrome DevTools Protocol for automation and interaction.

Help your AI agent finish more browser tasks.

Automate remote browsers using the BrowserCat API.

Remote browser automation using the BrowserCat API.

Take screenshots and read console logs from web pages using Playwright.

Automate browser tasks using the Browser Use API.

A Node.js server that enables AI assistants to control the Chrome browser via WebSocket. Requires the CodingBaby Chrome Extension.

A configurable MCP server for browser automation using Puppeteer.