Skip to main content
Glama
nolanbaxter

Local Browser MCP

by nolanbaxter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Local Browser MCP

No user-submitted related servers found.

    Related Servers

    • Secure Browser MCP

      pranavgawasproject
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI clients controlled access to a real headless browser with domain allowlisting, SSRF protection, per-session isolation, audit logging, and persistent cookies/state across restarts.
      6 npm
      MIT

    • OpenBrowser

      dylansantwani
      A
      license
      Not graded
      quality
      A
      maintenance
      A zero-dependency MCP server that drives a real Chrome browser through a companion extension, enabling AI agents to automate real user sessions with trusted input events, compact accessibility-tree snapshots, and 14 tools for navigation, interaction, scripting, and inspection.
      302 npm
      1
      MIT

    • bwb-browser

      krshforever
      A
      license
      B
      quality
      A
      maintenance
      A lightweight 30KB MCP browser automation server that uses raw Chrome DevTools Protocol to enable AI agents to browse the web, take screenshots, interact with elements, and capture live page events like console logs and network requests.
      26
      7 npm
      15
      MIT

    • kilo-computer-use

      123itsfree
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      MCP server that connects AI agents to a real Chrome browser via a WebSocket extension bridge, enabling over 40 browser control tools without debug mode or profile isolation.
      -
    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 27 tools

    Disambiguation5/5

    Each tool targets a distinct browser action (navigation, interaction, inspection, tab management, dialogs, downloads, allowlist). No significant overlap; `snapshot` vs `get_text` and `fill` vs `type` are clearly differentiated.

    Naming Consistency5/5

    All tools use lowercase_with_underscores, with action-oriented verbs (e.g., `navigate`, `click`, `wait_for`, `new_tab`). Consistent pattern throughout.

    Tool Count2/5

    With 27 tools, the server exceeds the recommended range. While the breadth is comprehensive, it pushes into the 'too many' territory, risking agent confusion and maintenance overhead.

    Completeness4/5

    The tool set covers core browser operations well, but lacks explicit tools for URL retrieval, scrolling, and cookie management. However, `eval` can work around these gaps, so coverage is mostly complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources