Selenix-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_screenshotA | Capture a screenshot of the active browser window in Selenix playback. Returns a base64-encoded JPEG image. |
| get_page_htmlA | Get the HTML of the web page in the active playback window, with interactive elements annotated. Scripts and styles are removed. |
| get_search_htmlC | Search page HTML by regex pattern and return surrounding HTML context for matches. |
| get_selected_command_infoA | Get comprehensive context about a command target element: DOM hierarchy, accessibility info, surrounding HTML, interactive properties. |
| get_current_testB | Get the commands of the current test (or a specific test by ID). Returns test name, ID, and all commands with their targets and values. |
| get_test_listB | List all tests in the current Selenix project with their IDs, names, and command counts. |
| get_test_by_nameB | Get a specific test by its name, including all commands. |
| get_command_listB | List all available Selenix commands (click, type, open, etc.) with descriptions. |
| get_command_infoB | Get detailed documentation for a specific Selenix command, including target and value parameter descriptions. |
| get_project_infoB | Get metadata about the current Selenix project: name, base URL, test count, suite count. |
| get_active_suiteB | Get information about the currently active test suite and its tests. |
| get_step_resultsC | Get pass/fail/error results for each command in the last test run. |
| get_logsA | Get recent logs from Selenix (all types). Returns 20 logs per page, most recent first. Use page parameter to paginate (0 = most recent, 1 = next 20, etc.). |
| get_workspace_contextA | Get a summary of the current Selenix workspace: project name, active test, test count, selected command count. |
| add_commandsC | Add one or more commands to a test at a specific index. Commands use camelCase names (e.g., "click", "type", "open", "executeScript"). |
| run_testA | Run a test and wait for it to complete. Returns the pass/fail result for each command. This operation may take up to 2 minutes. |
| clear_and_replace_commandsA | Replace ALL commands in a test with a new set. This removes all existing commands first. |
| fix_commandsB | Apply targeted fixes to commands in a test: update, remove, or insert at specific indexes. Indexes refer to the current command list BEFORE any fixes are applied. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Most tools have clearly distinct purposes, such as 'add_commands' for adding commands versus 'clear_and_replace_commands' for replacing all commands. However, some overlap exists between 'get_current_test' and 'get_test_by_name', as both retrieve test details, which could cause minor confusion. Overall, the descriptions help clarify boundaries, but the duplication in test retrieval tools slightly reduces clarity.
Tool names follow a highly consistent verb_noun pattern throughout, such as 'add_commands', 'get_active_suite', and 'run_test'. All tools use snake_case without deviation, making them predictable and easy to parse. This consistency enhances usability and reduces cognitive load for agents.
With 18 tools, the count is slightly high but reasonable for a Selenium automation domain, covering test management, command operations, and debugging. It provides comprehensive functionality without feeling overly bloated. A minor reduction could improve focus, but the scope justifies most tools.
The tool set offers complete coverage for Selenium test automation, including CRUD operations for commands (add, clear, fix), test retrieval and execution (get, run), and debugging features (logs, screenshots, HTML analysis). No obvious gaps exist; agents can manage the full test lifecycle from creation to analysis seamlessly.