Skip to main content
Glama
markmircea

Selenix-MCP

by markmircea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Selenix-MCP

No user-submitted related servers found.

    Related Servers

    • playwright-mcp

      ademdeniz
      F
      license
      A
      quality
      B
      maintenance
      An MCP server that gives Claude direct control of a real browser via Playwright, enabling AI-driven web testing, autonomous test execution, and live failure analysis through natural language.
      8
      4,622 npm
      3
      -

    • browser-mcp

      ruggieroromulo
      A
      license
      Not graded
      quality
      C
      maintenance
      Local browser automation MCP server for Claude Code, enabling navigation, clicking, typing, and inspecting real web pages via Google Chrome.
      17 npm
      1
      MIT

    • mare-browser-mcp

      emadklenka
      A
      license
      A
      quality
      C
      maintenance
      A lean, LLM-first browser automation MCP server that gives Claude (or any MCP client) a real Chromium browser to navigate, interact with, and debug web apps.
      14
      6 npm
      6
      MIT

    • se-mcp

      se-cli
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for se-cli that exposes 50+ Selenium browser automation tools for AI agents, enabling browser control through a thin wrapper around se-cli.
      8 npm
      Apache 2.0

    • Browser & File MCP Server

      Powellga
      A
      license
      Not graded
      quality
      D
      maintenance
      This MCP server enables browser automation (navigation, clicking, screenshots) and file reading (Excel, Word, PowerPoint, CSV, images) for Claude Code and any MCP client.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 18 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources