Selenix MCP Server

What markmircea/Selenix-MCP-Server MCP server does

The markmircea/Selenix-MCP-Server MCP server exposes Selenix browser automation and testing workflows to Claude Desktop. It supports inspecting the active workspace, browsing available tests and commands, viewing project and suite metadata, and examining the current test. Claude can also capture browser screenshots, retrieve page HTML with interactive elements annotated, search page HTML with a regular expression, and inspect DOM context for a command target.

The server also provides operations for changing and executing tests. An agent can append commands at a chosen position, replace a test's complete command set, or apply focused updates, removals, and insertions. The run_test tool waits for execution results for up to two minutes, while result and log tools help review what happened afterward.

How it works

The markmircea/Selenix-MCP-Server MCP server uses Claude Desktop's stdio transport on one side and Selenix's local HTTP bridge on the other:

Claude Desktop -> MCP server -> Selenix bridge

Selenix must be open with its MCP server bridge enabled. The bridge listens only on 127.0.0.1, so the documented setup does not expose it to the network. Selenix creates a bearer token when it starts. Connection details are stored in ~/.selenix/bridge.json, and the MCP server reads that configuration for each call, allowing Selenix to restart without requiring a Claude Desktop restart.

Setup and configuration

Install Selenix and Claude Desktop, and use Node.js 18 or newer. In Selenix, open System Settings, find the MCP Server section, and enable the MCP server. The README documents an npm installation using npm install -g @selenix/mcp-server, followed by a Claude Desktop configuration that runs the package's dist/bundle.js with Node. The Selenix desktop application may also include resources/mcp-server/index.js, which can be used directly, or the bundle can be downloaded manually.

After editing Claude Desktop's claude_desktop_config.json, restart Claude Desktop. The configuration must place the Selenix entry inside mcpServers. A tools icon should then appear in the chat input area. If the bridge cannot be read or reached, first check that Selenix is running and that its MCP server setting is enabled.

Tools and capabilities

Inspection tools cover screenshots, page HTML, regex-based HTML search, selected-element context, tests, commands, project data, active suites, workspace summaries, step results, and paginated recent logs. Command documentation can be queried before constructing or repairing a test.

Editing and execution tools support adding commands, replacing all commands, applying targeted fixes, and running tests synchronously until results are available or the two-minute limit is reached.

Limitations and notes

The markmircea/Selenix-MCP-Server MCP server depends on the Selenix desktop application and its local bridge; it is not described as a standalone browser driver. Claude Desktop must be restarted after configuration changes. The bridge configuration is local, and no remote endpoint or external API credential is documented. The README's example paths contain machine-specific placeholders, so they must be replaced with actual local paths when configuring the Node command.