Skip to main content
Glama
Sign In
jev-reach

jev-reach

by rashedInt32
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to jev-reach

No user-submitted related servers found.

    Related Servers

    • chrome-in-harness

      hcfw007
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP client to drive the user's real Chrome profile through a Chrome extension bridge, with tools for navigation, accessibility snapshots, ref-based interactions, console/network reading, screenshots, tab management, and restricted script evaluation.
      1
      MIT

    • jev-browser-mcp

      Gregory78529
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables an MCP client to drive a real browser by stating one outcome at a time, with the Jev model deciding the element, action, and value for each round and pausing before irreversible actions. Also exposes tools to open and act on pages, snapshot or read page content, check yes/no questions, take screenshots, and list or call a page's own WebMCP tools.
      1,461 npm
      MIT

    • Chrome Live MCP

      wankaiyi
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects local stdio MCP servers to an existing Chrome 144+ session, preserving the user's signed-in sessions, cookies, tabs, and extension environment without launching a second browser. It provides tab control, semantic snapshots, screenshots, pointer, keyboard, form selection, scrolling, navigation, and waiting tools.
      MIT

    • jev-browser-mcp

      Barbara88985
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM-driven browser automation in which the caller states one outcome per step and Jev (Typesafe System One) decides the target element, action, value, and whether the step is done, blocked, erroring, or irreversible, while Playwright performs the action. Also exposes direct tools for navigation, element actions, page reading, screenshots, and invoking WebMCP tools that a page registers.
      1,461 npm
      MIT

    • jev-browser-mcp

      FrancoisMorales892
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to drive a real browser toward stated outcomes, where the calling model supplies goals and candidate values while Jev (Typesafe System One) resolves each step's target, action, value, and done/blocked/irreversible status. Exposes tools for navigation, acting, yes/no checks, choosing among options, page reading, snapshots, screenshots, and calling page-registered WebMCP tools.
      1,461 npm
      MIT

    • TabWeave MCP

      dhtfish-98
      A
      license
      D
      quality
      B
      maintenance
      Connects to an already-running Chrome/Chromium instance over CDP and exposes 75 browser-automation tools over newline-delimited MCP JSON-RPC on stdin/stdout, covering navigation, forms, keyboard/mouse input, screenshots, cookies, storage, tabs and frames, assertions, and retry/batch/step composition. It does not launch a browser itself, requiring a localhost debugging port on the existing instance.
      75
      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

    B3.3/5.0

    Scored across 30 tools

    Disambiguation3/5

    Most tools have distinct targets, but fill, fill_form, type_text, and press_key overlap significantly in the input/text-entry space. The tool descriptions help, especially fill_form's explicit preference note, but an agent could still easily misselect among them.

    Naming Consistency3/5

    Names are consistently lowercase snake_case, but they mix verb-first forms like list_pages and take_screenshot with domain-prefixed forms like performance_start_trace and lighthouse_audit, plus bare verbs like fill, hover, and reach. The naming is readable but not predictable enough to infer related tools consistently.

    Tool Count2/5

    At 30 tools, the surface is over the heavy threshold and likely larger than needed. The breadth is defensible for a DevTools-style browser automation server, but several tools could be consolidated, such as fill/fill_form and the list_network_requests/get_network_request pairs.

    Completeness5/5

    The set covers the full browser automation and debugging lifecycle: navigation, page management, element interaction, forms, uploads, dialogs, console/network inspection, screenshots/snapshots, and performance/memory auditing. There are no obvious dead ends or missing core operations for its apparent purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessLimited data

    Resources