Skip to main content
Glama
TechyAditya

jev-browser-sidekick-mcp

by TechyAditya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to jev-browser-sidekick-mcp

No user-submitted related servers found.

    Related Servers

    • browserbash

      PramodDutta
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables plain-English browser automation via an MCP server, allowing agents to run objectives or test suites in a real browser without selectors or scripts.
      54 npm
      3
      Apache 2.0

    • jev-browser-mcp

      Emma76217
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to automate browser tasks by describing desired outcomes and candidate values, while Jev selects elements/actions and returns statuses, with direct tools for navigation, checks, reading, acting, snapshots, screenshots, and WebMCP calls.
      730 npm
      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.
      730 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.
      730 npm
      MIT

    • cursor-jev

      Pioneer113
      A
      license
      A
      quality
      B
      maintenance
      Enables Cursor to drive Google Chrome through the jev-browser-use click loop, with Cursor supplying tasks, typing text, and verifying results while Jev chooses the next click.
      5
      1
      MIT

    • jev-browser-mcp

      margauxbutler
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables an LLM client to drive a real browser by stating one outcome per step, while Jev (Typesafe System One) decides which element, action, and value to use and Playwright performs it. Also exposes tools for direct actions, page reading, screenshots, checks, choices, and calling a page's own WebMCP tools.
      730 npm
      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

    A3.6/5.0

    Scored across 2 tools

    Disambiguation4/5

    run_action drives a browser while use_jev_raw answers typed decision questions with no browser, so the core split is clear. There is mild overlap since run_action internally has 'Jev choose' on each page, which brushes against use_jev_raw's decision role, but the browser/no-browser boundary keeps them mostly distinct.

    Naming Consistency3/5

    Both names are snake_case, but run_action is a clean verb_noun while use_jev_raw embeds a product name plus an adjective, so the pattern is not predictable. Readable, but the two names follow different construction conventions.

    Tool Count3/5

    Two tools is thin for a browser sidekick, and the surface leans entirely on run_action to multiplex search, click, read, tabs, and groups. It is a defensible facade design, but the low count is borderline for the apparent scope.

    Completeness3/5

    run_action covers search, open, click, read, groups, multi-tab errands, and use_jev_raw covers decisions, which spans the main intent. However, there is no explicit surface for page extraction, screenshots, navigation history, or tab cleanup, so some lifecycle operations are unaddressed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources