Skip to main content
Glama
ofershap

real-browser-mcp

by ofershap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to real-browser-mcp

No user-submitted related servers found.

    Related Servers

    • byob

      daikihunter
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that enables AI coding assistants to drive the real, already-logged-in Chrome browser — navigating pages, clicking, typing, reading content, taking screenshots, and inspecting tabs, cookies, and network traffic through natural language. It works as a Chrome extension, so no remote-debugging port needs to be opened and pages the user is already signed into are fully usable.
      1 npm
      ISC

    • byob

      Pavelj43
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive the user's actual, already-logged-in Chrome browser — snapshotting pages, clicking, typing, navigating, reading content, taking screenshots, and inspecting cookies, network traffic, and console output. Browser automation happens through a Chrome extension using Native Messaging, so no remote-debugging port is exposed and all communication stays on the local machine.
      1 npm
      ISC

    • byob

      melissa89018
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive your real, already-logged-in Chrome — navigating, reading, clicking, filling forms, screenshotting, inspecting network traffic and cookies. Because it runs through a browser extension instead of a debugging port, it works on authenticated pages and passes bot detection without extra setup.
      1 npm
      ISC

    • byob

      RafaelRoussel
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI assistants drive your real, already-logged-in Chrome through a browser extension, so agents can read, click, type, navigate, screenshot, inspect network traffic, and manage cookies or storage on pages that require existing sessions. It works without opening a remote-debugging port and keeps all communication on your machine.
      1 npm
      ISC

    • byob

      KohakuRamos65
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding assistants drive the user's real, already-logged-in Chrome through a companion extension, with tools for navigation, snapshots, clicking, typing, reading page content, screenshots, tabs, network inspection, and cookies. It works without a remote-debugging port, so sessions and bot-detection state of the everyday browser are preserved while everything stays on the user's machine.
      1 npm
      ISC

    • byob

      Nataliak9683
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding assistants drive the Chrome browser you already have open, using your existing logged-in sessions. It enables navigating and reading pages, clicking, typing, filling forms, taking screenshots, uploading files, and inspecting console, network, storage, and cookies — without headless browsers or opening a remote-debugging port.
      1 npm
      ISC
    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.4/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (click, type, snapshot, navigate, etc.), but there is overlap: browser_evaluate and browser_run_action both execute JavaScript, and browser_click, browser_click_text, and browser_find can be confused for locating and clicking elements. Descriptions mostly clarify these boundaries, but an agent may still hesitate between the JS execution tools and the click variants.

    Naming Consistency4/5

    All tool names use the browser_ prefix and snake_case, which is highly predictable. However, the second component mixes verbs (click, type, navigate) and nouns (console, network, tabs, screenshot, text), so it is not a strict verb_noun pattern.

    Tool Count4/5

    22 tools is on the heavy side of the ideal 3-15 range, but each tool maps to a distinct browser automation capability such as interaction, observation, navigation, or tab management. The breadth is justified for a full-featured browser control server, though some consolidation (e.g., click variants) would improve usability.

    Completeness4/5

    The surface covers navigation, element interaction, observation, waiting, dialogs, and tabs, leaving few dead ends. Minor gaps include browser history (back/forward), cookie/storage management, and download handling, but core automation workflows are well supported.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources