Skip to main content
Glama
Sign In
bwb-browser

bwb-browser

by krshforever
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to bwb-browser

No user-submitted related servers found.

    Related Servers

    • kitewright

      kitewrightofficial

      kitewright
      A
      license
      Not graded
      quality
      B
      maintenance
      A lightweight MCP server for browser automation that gives AI agents navigate, screenshot, and extract tools via a single small binary, without needing Node.js or Playwright. It provides CDP-based browser control with efficient startup and resource usage.
      24
      MIT

    • Scout

      klarlabs-studio
      A
      license
      Not graded
      quality
      C
      maintenance
      single-binary MCP server that gives AI agents a browser. 66 tools for navigation, form filling, data extraction, screenshots, and DOM diffing — built on pure Chrome DevTools Protocol.
      14
      MIT

    • Mithwire MCP

      elendil-tech
      A
      license
      C
      quality
      B
      maintenance
      An MCP server that gives AI clients direct control over driverless Chromium browsers through the Chrome DevTools Protocol, enabling agents to navigate pages, click, type, inspect the DOM, capture console and network traces, and manage tabs, cookies, and storage. It supports persistent profiles, proxy and locale alignment, and a live VNC viewer so users can build, test, and debug web automations interactively.
      70
      MIT

    • Ghostlight

      sylin-org
      A
      license
      A
      quality
      B
      maintenance
      MCP server that lets AI agents drive your real Chromium browser with your existing signed-in sessions, providing visible, local, and inspectable automation for tasks like navigation, clicking, typing, and form filling.
      25
      1
      Apache 2.0

    • xfactor

      fveiraswww
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI agents to browser DevTools via CDP, enabling real-time access to console logs, network requests, and page state.
      -
    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.4/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: navigation, DOM extraction, tab management, cookies, sessions, and utility actions are clearly separated. Minor overlap exists between browser_status and browser_listTabs (both report on open tabs) and between browser_text and browser_html (both retrieve page content), but these are distinguishable by their output types.

    Naming Consistency3/5

    The browser_ prefix provides a consistent namespace, but the action portion mixes conventions: standalone verbs (click, fill, goto, watch), nouns (text, html, status), and camelCase compounds (setViewport, waitForSelector, listTabs, saveCookies). This is readable but lacks the uniform verb_noun pattern seen in the highest-coherence servers.

    Tool Count3/5

    At 26 tools, the server technically crosses the 25-tool 'too many' threshold, but the count is justified by the broad scope of browser automation (navigation, DOM, tabs, cookies, download/export, diagnostics). It feels heavy rather than bloated, with only a few niche tools like browser_fingerprint and browser_export being arguably optional.

    Completeness4/5

    The domain is well covered: navigation, interaction, DOM extraction, tab management, sessions, waiting, and diagnostics all have dedicated tools. Minor gaps exist—there is no explicit browser_forward, browser_reload, or browser_scroll—but these can be worked around with browser_eval or browser_act, so agents won't hit dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources