{
  "markdown": "# Selenix MCP Server\n\n[![npm version](https://img.shields.io/npm/v/@selenix/mcp-server.svg)](https://www.npmjs.com/package/@selenix/mcp-server)\n\nConnect [Claude Desktop](https://claude.ai/download) to [Selenix](https://selenix.io) via 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.\n\n[![Selenix-MCP MCP server](https://glama.ai/mcp/servers/markmircea/Selenix-MCP-Server/badges/card.svg)](https://glama.ai/mcp/servers/markmircea/Selenix-MCP-Server)\n\n## Prerequisites\n\n- [Selenix](https://selenix.io) desktop app installed\n- [Claude Desktop](https://claude.ai/download) installed\n- [Node.js](https://nodejs.org/) 18 or later\n\n## Enable the Bridge in Selenix\n\nBefore using any setup method below, enable the bridge inside Selenix:\n\n1. Open Selenix\n2. Go to **System Settings** (gear icon in the sidebar)\n3. Scroll to the **MCP Server** section\n4. Set **Enable MCP Server** to **Yes**\n\nThis starts a local bridge server that the MCP server connects to.\n\n## Setup\n\nChoose one of the following methods:\n\n### Option A: Install via npm (recommended)\n\n```bash\nnpm install -g @selenix/mcp-server\n```\n\nThen find your global npm path:\n\n```bash\nnpm root -g\n```\n\nOpen your Claude Desktop config file:\n\n- **Windows**: Press `Win+R`, paste `%APPDATA%\\Claude\\claude_desktop_config.json`, press Enter\n- **macOS**: Open `~/Library/Application Support/Claude/claude_desktop_config.json`\n\nAdd the Selenix MCP server, replacing the path with the output from `npm root -g`:\n\n```json\n{\n  \"mcpServers\": {\n    \"selenix\": {\n      \"command\": \"node\",\n      \"args\": [\"<npm-root-path>/@selenix/mcp-server/dist/bundle.js\"]\n    }\n  }\n}\n```\n\n**Example (Windows with nvm):**\n```json\n{\n  \"mcpServers\": {\n    \"selenix\": {\n      \"command\": \"node\",\n      \"args\": [\"C:/Users/YourName/AppData/Local/nvm/v18.20.8/node_modules/@selenix/mcp-server/dist/bundle.js\"]\n    }\n  }\n}\n```\n\n**Example (macOS/Linux):**\n```json\n{\n  \"mcpServers\": {\n    \"selenix\": {\n      \"command\": \"node\",\n      \"args\": [\"/usr/local/lib/node_modules/@selenix/mcp-server/dist/bundle.js\"]\n    }\n  }\n}\n```\n\nIf you already have other MCP servers configured, add `\"selenix\"` alongside them inside the existing `\"mcpServers\"` object.\n\n### Option B: Use the bundled version (no npm required)\n\nIf 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.\n\nFind your Selenix install folder and look for `resources/mcp-server/index.js`, then add to your Claude Desktop config:\n\n```json\n{\n  \"mcpServers\": {\n    \"selenix\": {\n      \"command\": \"node\",\n      \"args\": [\"C:/path/to/Selenix/resources/mcp-server/index.js\"]\n    }\n  }\n}\n```\n\n**Typical Windows path:**\n```\nC:/Users/YourName/AppData/Local/Programs/Selenix/resources/mcp-server/index.js\n```\n\n### Option C: Manual download\n\n1. Download `bundle.js` from the [npm package page](https://www.npmjs.com/package/@selenix/mcp-server) or from the [releases page](https://github.com/AiBrainOrg/selenix/releases)\n2. Save it somewhere on your machine (e.g., `C:/selenix-mcp/bundle.js`)\n3. Add to your Claude Desktop config:\n\n```json\n{\n  \"mcpServers\": {\n    \"selenix\": {\n      \"command\": \"node\",\n      \"args\": [\"C:/selenix-mcp/bundle.js\"]\n    }\n  }\n}\n```\n\nNode.js is still required — the MCP server is a single JavaScript file with no other dependencies.\n\n## Verify\n\nRestart Claude Desktop after editing the config. You should see the Selenix tools icon (hammer) in the chat input area.\n\nTry asking Claude:\n\n- \"What tests are in my Selenix project?\"\n- \"Create a test that opens google.com and searches for 'selenium automation'\"\n- \"Run the current test and fix any failures\"\n- \"Take a screenshot of the browser\"\n\n## How It Works\n\n```\nClaude Desktop <--stdio--> MCP Server <--HTTP--> Bridge Server (inside Selenix)\n```\n\nThe 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.\n\n- The bridge only listens on `127.0.0.1` (localhost) — no network exposure\n- Auth is handled via a bearer token auto-generated each time Selenix starts\n- Connection config is stored at `~/.selenix/bridge.json` and re-read on every call, so restarting Selenix does not require restarting Claude Desktop\n\n## Available Tools\n\n### Reading & Inspection\n\n| Tool | Description |\n|------|-------------|\n| `get_screenshot` | Capture a screenshot of the browser window |\n| `get_page_html` | Get the page HTML with interactive elements annotated |\n| `get_search_html` | Search page HTML by regex pattern |\n| `get_selected_command_info` | Get DOM context for a command's target element |\n| `get_current_test` | Get all commands in the current test |\n| `get_test_list` | List all tests in the project |\n| `get_test_by_name` | Get a test by its name |\n| `get_command_list` | List all available Selenix commands |\n| `get_command_info` | Get detailed docs for a specific command |\n| `get_project_info` | Get project metadata |\n| `get_active_suite` | Get the active test suite |\n| `get_step_results` | Get pass/fail results from the last test run |\n| `get_logs` | Get recent logs (all types), 20 per page, most recent first. Optional `page` param for pagination. |\n| `get_workspace_context` | Get a summary of the current workspace |\n\n### Writing & Execution\n\n| Tool | Description |\n|------|-------------|\n| `add_commands` | Add commands to a test at a specific position |\n| `run_test` | Run a test and wait for results (up to 2 minutes) |\n| `clear_and_replace_commands` | Replace all commands in a test |\n| `fix_commands` | Apply targeted fixes — update, remove, or insert commands |\n\n## Troubleshooting\n\n**\"Cannot read Selenix bridge config\"**\nSelenix isn't running or the MCP Server isn't enabled. Open Selenix → System Settings → set Enable MCP Server to Yes.\n\n**\"Cannot connect to Selenix bridge\"**\nSelenix may have just restarted. Try the request again — the MCP server will automatically pick up the new connection details.\n\n**Tools not appearing in Claude Desktop**\nMake sure you restarted Claude Desktop after editing the config file. Verify the config JSON is valid (no trailing commas, correct brackets).\n\n**Claude Desktop won't open after config change**\nThe 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.\n\n## Uninstall\n\n```bash\nnpm uninstall -g @selenix/mcp-server\n```\n\nThen remove the `\"selenix\"` entry from your Claude Desktop config file and restart Claude Desktop.",
  "bytes": 6716,
  "sha": "882024d047e6aafbe4f2aadd70907f1d33cc58e441981903dc2b23138da6f828",
  "repo_slug": "markmircea/selenix-mcp-server",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_markmircea_selenix_mcp_server_e3e62764/readme"
}