Skip to main content
Glama
gaforov

selenium-mcp

by gaforov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to selenium-mcp

Related Servers

  • openmcp

    openmcp-pro
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI agents to automate web tasks such as browsing, clicking, typing, and taking screenshots via the Model Context Protocol.
    1
    MIT

  • stealthy-auto-browse MCP

    psyb0t
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents to control a stealthy browser via the Model Context Protocol, supporting navigation, screenshots, clicking, typing, and more.
    84
    Do What The F*ck You Want To Public

  • agent-browser

    Nirmalraj10567
    F
    license
    C
    quality
    C
    maintenance
    Provides browser automation tools for AI assistants via the Model Context Protocol, enabling tasks like navigation, clicking, filling forms, screenshots, and script execution through natural language.
    39
    -

  • Playwright Automation MCP

    devqa07
    F
    license
    A
    quality
    D
    maintenance
    Enables AI-powered browser automation controlled through natural language, integrating Playwright with the Model Context Protocol to perform web interactions like navigation, form filling, and screenshots.
    10
    -
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

A4.1/5.0

Scored across 41 tools

Disambiguation4/5

Almost every tool has a distinct purpose, and descriptions actively cross-reference alternatives (e.g. click vs interact vs retry_click, get_text vs assert_text vs get_attribute, wait_for_element vs assert_visible). There is mild overlap in the click/assert/wait families, but the descriptions consistently steer to the right choice, leaving little genuine ambiguity.

Naming Consistency3/5

Names are uniformly snake_case, but the verb placement is mixed: most are verb_noun (get_text, add_cookie, take_screenshot) while others are noun_verb (session_list, selector_hint_save) and several are bare nouns (window, frame, alert, history). Still readable but not a single predictable pattern.

Tool Count2/5

41 tools is well beyond the heavy range for a single server, even a broad browser-automation domain. Many assertion, wait, cookie, and session variants could be consolidated or parameterized rather than exposed as separate tools.

Completeness5/5

The surface covers the full browser-automation lifecycle: sessions, navigation, interaction, waits, assertions, cookies, windows/tabs, frames, native dialogs, file upload, JS execution, screenshots, and persisted selector hints. No obvious gaps or dead ends for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources