Skip to main content
Glama
seleniumbase

seleniumbase-mcp

Official
by seleniumbase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to seleniumbase-mcp

Related Servers

  • ultrastealth

    anusoft
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables Claude to perform stealth browser automation with anti-detection, including navigation, clicking, typing, screenshots, and network monitoring via an MCP server.
    MIT
  • AIHawk by feder-cr

    AIHawkofficial

    feder-cr
    A
    license
    A
    quality
    A
    maintenance
    Enables assistants such as Claude Code, Codex, and Gemini CLI to drive a real browser over MCP — navigating, clicking, typing, and reading live pages from plain-English instructions. Supports optional proxy routing, persistent profiles for surviving logins, and reproducible browser identities via seeds.
    16
    31,752
    MIT

  • gotham-browser

    gotham-os
    F
    license
    Not graded
    quality
    B
    maintenance
    Enables Claude Code to control a real browser using AI for web scraping, competitive intelligence, and UX auditing through the MCP protocol.
    -

  • Claude Chrome MCP

    nonsleepr
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables browser automation through the Claude Chrome Extension, allowing agents to navigate websites, fill forms, take screenshots, and debug web apps via standard MCP protocols.
    1
    MIT
Deploy Server
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

TDQS

A4.7/5.0

Scored across 24 tools

Disambiguation4/5

Most tools have clearly distinct purposes (click_element vs type_text vs select_option vs hover_action), and the descriptions include explicit 'Tool selection' guidance to disambiguate overlapping read/check/wait/assert tools. However, check_if_condition, wait_for_condition, and assert_condition form a closely related trio that could still cause misselection despite the guidance.

Naming Consistency4/5

Tool names mostly follow a consistent verb_noun pattern (start_browser, close_browser, click_element, type_text, find_elements, get_content, manage_cookies, manage_tabs, manage_window, manage_history, manage_storage, scroll_page, save_page, open_url, hover_action, select_option, focus_element, run_javascript, solve_captcha). Minor deviations: check_if_condition, wait_for_condition, and assert_condition use a different 'condition' suffix pattern, and get_page_info breaks the get_* noun pattern slightly.

Tool Count4/5

24 tools is on the higher end but appropriate for a full browser automation server covering lifecycle, navigation, element interaction, state inspection, storage, tabs, windows, and page saving. The count is justified by the breadth of the domain, though it is close to the threshold where it starts feeling heavy.

Completeness5/5

The tool surface covers the full browser automation lifecycle: browser start/close, navigation, history, tabs, windows, element finding/clicking/typing/selecting/hovering/focusing, content reading, attribute reading, condition checking/waiting/asserting, cookies, storage, JavaScript execution, captcha solving, and page saving. No obvious dead ends or missing core operations for the stated purpose.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources