Skip to main content
Glama

Related Servers

Alternatives to jev-reflex

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      A browser automation agent that enables Claude to interact with web browsers through the Model Context Protocol, allowing for actions like navigating websites, manipulating elements, and managing browser state.
      2
      9
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to directly control a persistent, real logged-in Chrome browser via 17 browser tools and 9 trading tools, with natural-language selectors, self-healing element resolution, and risk-limited trading operations.
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables browser automation for coding agents via MCP, allowing them to open pages, search, extract data, click, type, and complete multi-step tasks with fast single-round-trip decisions.
      14
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Fast Browser is an MCP server that lets Claude Code and Codex drive an existing Chrome browser with your real profile, logins, and tabs, using a macro library for multi-step flows in single tool calls and supporting concurrent agents with isolated tab groups.
      57 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol (MCP) integration that provides Claude Desktop with autonomous browser automation capabilities. This agent enables Claude to interact with web content, manipulate DOM elements, execute JavaScript, and perform API requests.
      13
      8 npm
      41
      TypeScript
      Mozilla Public 2.0

    TDQS

    B3.3/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools map cleanly to distinct browser actions, but browser_current_tab and browser_page_info overlap on basic tab metadata, and browser_type vs browser_fill both handle text input. The descriptions help disambiguate, but an agent could plausibly misselect between these pairs.

    Naming Consistency4/5

    All tools share the browser_ prefix and snake_case style, and the majority follow a clear verb_noun pattern (goto, click, close_tab, new_tab). However, a few names deviate with noun phrases or added prepositions like current_tab, page_info, ensure_real_tab, and wait_for_load, making the pattern mostly but not fully consistent.

    Tool Count4/5

    At 23 tools, this is on the heavier side, but each tool serves a distinct browser automation capability—navigation, tabs, wait conditions, input, JS/CDP, upload, and recording. The count is justified for a browser control surface, though it slightly exceeds the typical well-scoped range.

    Completeness4/5

    The tool set covers most standard browser automation needs: navigation, tab management, interaction, waiting, screenshots, JS evaluation, raw CDP, file upload, and session recording. Minor gaps like explicit back/forward/reload, hover, or direct text extraction exist, but these are workable via browser_js or browser_cdp.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues