Skip to main content
Glama
zulfiqar90

Selenium MCP Server

by zulfiqar90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Selenium MCP Server

No user-submitted related servers found.

    Related Servers

    • Selenium MCP Server

      AbyvargheseMandapathel
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents and MCP clients to automate web browsers via Selenium WebDriver, supporting Chrome, Firefox, and Edge in headless or visible mode with tools for navigation, interaction, content extraction, screenshots, and scripting.
      21
      13 npm
      MIT

    • selenium-mcp

      masx200
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides browser automation using Selenium, supporting Chrome and Firefox, with tools for navigation, element interaction, screenshots, and more.
      1
      Mulan Permissive Software , Version 2

    • Browser MCP

      CypherPotato
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to control a real local browser window for web automation tasks such as clicking, typing, scrolling, and taking screenshots.
      11 npm
      -

    • Selenium MCP

      kubed-io
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to drive a persistent real browser on Selenium Grid through MCP or HTTP, performing multi-step actions like navigation, clicking, typing, scripting, and screenshots while retaining session state.
      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.5/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct action (click, navigate, type, screenshot, etc.) with no overlap. Even CSS-selector-based tools like click, get_text, type, and wait_for_element are clearly separated by their operation.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (e.g., close_browser, execute_script, wait_for_element). The naming is predictable and easy to understand.

    Tool Count5/5

    With 10 tools, the set covers essential browser automation actions without being bloated. Each tool earns its place, and the count is appropriate for the domain.

    Completeness4/5

    The tools cover core browsing tasks (navigation, interaction, script execution, screenshots, session control). Minor gaps exist, such as retrieving element attributes or handling alerts, but the surface is largely complete for common workflows.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources