Skip to main content
Glama
kofanlabs

Jev Browser Bridge

by kofanlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Jev Browser Bridge

No user-submitted related servers found.

    Related Servers

    • browser-bridge

      jeffkit
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables remote agents to control a local Chrome/Edge browser via MCP, supporting navigation, snapshots, clicks, typing, screenshots, and script execution.
      152 npm
      ISC

    • chrome-mcp

      dawei008
      F
      license
      Not graded
      quality
      D
      maintenance
      Drive your real, signed-in Chrome browser from any MCP client, enabling browser automation such as navigation, clicking, typing, and screenshots through standard MCP tools.
      1
      -

    • Real Browser MCP

      ton-to-ton
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation over MCP using a real Chrome browser with existing profile, supporting real tabs, downloads, cookies, and RPA workflows.
      96 npm
      MIT

    • monkeysee

      juliocesar
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to drive a real, logged-in Chrome browser for web automation tasks like navigation, clicking, typing, and screenshotting.
      2 npm
      MIT

    • BrowserUse

      YisRime
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to control Chrome/Edge browsers via CDP, including page navigation, element interaction, snapshots, network debugging, script execution, and performance tracing.
      AGPL 3.0
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    B3.2/5.0

    Scored across 23 tools

    Disambiguation4/5

    Tools are largely distinct, with clear prefixes and domain-specific actions. Minor overlap exists between browser_type (focused element) and browser_fill (selector-based), and between browser_goto and browser_http_get, but descriptions mostly disambiguate them.

    Naming Consistency4/5

    All tools share the browser_ prefix and lowercase snake_case, creating a predictable style. A few names are noun-like rather than verb-first (browser_page_info, browser_current_tab, browser_js, browser_cdp), so it is not perfectly uniform.

    Tool Count3/5

    23 tools is on the heavier side and crosses into 'feels heavy' territory, though most operations are legitimate browser actions. The wait variants and raw CDP/JS escape hatches add some redundancy, making the set slightly larger than ideal.

    Completeness4/5

    The set covers core browser automation workflows: navigation, tabs, input, waiting, screenshots, uploads, recording, JS evaluation, and raw CDP. Missing conveniences like back/forward/reload and more advanced DOM inspection can be worked around via browser_js or browser_cdp.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources