Skip to main content
Glama
browser-mcp-server

browser-mcp-server

by vicktor12

Related Servers

Alternatives to browser-mcp-server

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      Gives Claude control of a real, headed Chromium browser via Playwright, enabling web navigation, clicking, typing, screenshots, and JavaScript evaluation.
      8
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code to control a browser via Playwright for web scraping, automation, and research, with features like navigation, screenshots, form filling, and PDF export.
      24 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation and web interaction control through Playwright, allowing Claude Code to navigate, click, fill forms, take screenshots, and manage sessions.
      100 npm
      9
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets Claude Code drive the user's own Chrome window — opening pages, clicking, and capturing screenshots — over a local stdio native-messaging bridge. Also handles Chrome site-permission prompts automatically and ships diagnostic/doctor tooling for reconnecting the bridge.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to control a real Chromium browser through Playwright, allowing them to navigate pages, click elements, fill forms, extract text or HTML, and capture screenshots in a persistent session.
      6
      ISC
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to drive your everyday logged-in browser session — opening and closing tabs, navigating, clicking, typing, scrolling, filling forms, uploading files, taking screenshots, and reading page text, console output and network requests. It runs through a local native-messaging bridge, scoping each client session to its own window behind yours.
      260 npm
      2
      MIT

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool maps to a distinct browser action: navigation, clicking, form filling, screenshot capture, page reading, and waiting. There is no meaningful overlap between them, and the descriptions reinforce clear boundaries (e.g., navigate before acting, read_page before deciding).

    Naming Consistency5/5

    All six tools use a strict browser_<verb> or browser_<verb>_<noun> snake_case pattern (browser_navigate, browser_click, browser_fill, browser_read_page). The convention is uniform and immediately readable.

    Tool Count5/5

    Six tools is a tight, well-scoped set for browser automation, with each tool earning its place and no redundant entries. It covers the observe-act-wait loop without bloat.

    Completeness4/5

    The core loop of navigate, read, interact (click/fill), wait, and capture is fully covered for most web tasks. Minor gaps exist for actions like scrolling, keyboard presses, hover, or back/forward navigation, but agents can largely work around these via clicks and fills.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data