Skip to main content
Glama
emadklenka

mare-browser-mcp

by emadklenka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mare-browser-mcp

No user-submitted related servers found.

    Related Servers

    • browser-mcp

      ruggieroromulo
      A
      license
      Not graded
      quality
      D
      maintenance
      Local browser automation MCP server for Claude Code, enabling navigation, clicking, typing, and inspecting real web pages via Google Chrome.
      22 npm
      1
      MIT

    • Pagerunner

      Enreign
      F
      license
      Not graded
      quality
      C
      maintenance
      A Chrome browser automation MCP server. Connect Claude (or any MCP client) to a real Chrome session — using your existing profiles with their cookies, saved passwords, and history.
      3
      -

    • deeporax-browser-mcp

      imfaisii
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server to control a real Chrome browser from Claude, enabling navigation, DOM snapshots, clicks, typing, screenshots, and JS execution via a Chrome extension bridge.
      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
    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

    A4.4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: navigation, action execution, debugging, DOM querying, snapshotting, waiting, screenshotting, JS eval, scrolling, restarting, uploading, network waiting, and device emulation. Even the inspection tools (debug, query, snapshot, eval) are well separated by what they return and when to use them.

    Naming Consistency5/5

    All 14 tools follow the consistent pattern of 'browser_' prefix followed by a lowercase verb (navigate, act, debug, query, fetch, snapshot, wait_for_url, screenshot, eval, scroll, restart, upload, wait_for_network, emulate_device). No mixing of camelCase or inconsistent verb styles.

    Tool Count5/5

    14 tools is within the ideal 3-15 range and each tool serves a distinct aspect of browser automation—navigation, interaction, inspection, waiting, debugging, device emulation, and file upload. The count is well-scoped for a comprehensive browser control server without being bloated.

    Completeness4/5

    The server covers the full lifecycle of browser interaction: navigate, act, inspect, wait, debug, screenshot, and emulate. Minor gaps exist such as no explicit dialog acceptance (alert/confirm/prompt) or tab management, but agents can work around these with browser_eval in most cases, so they are not critical dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources