Skip to main content
Glama
agent-browser-mcp
by Azheyc

Related Servers

Alternatives to agent-browser-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Lets AI agents control the real, already-logged-in Chrome browser: reading pages, clicking, typing, navigating tabs, taking screenshots, and inspecting cookies, network traffic, console output, and storage. It connects as a local extension over Native Messaging, so no remote-debugging port or headless profile is needed.
      1 npm
      ISC
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to directly operate a user's local Chrome browser with full login state and cookies, supporting 23 tools such as tab management, clicking, typing, screenshots, file upload, and network inspection through natural language.
      19 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI agents drive the user's real Chromium browser, including opening and controlling tabs, taking screenshots, capturing network traffic, recording screen activity, and handing control back for logins or payments while using the user's existing sessions, logins, and extensions.
      29,600 npm
      28
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to control your installed Google Chrome through MCP or HTTP using compact text snapshots, exact pixel coordinates, and a visible cursor. It provides browser tools for navigation, clicking, typing, scrolling, tabs, forms, waiting, recording, and human handoff.
      35
      160 npm
      3
      MIT

    TDQS

    B3.4/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have distinct purposes, but some overlap exists: 'capture_desktop_screenshot' and 'capture_page_screenshot' could be confused for similar screenshot tasks, and 'cdp_batch' and 'cdp_command' both handle CDP commands with subtle differences. The descriptions help clarify, but an agent might occasionally misselect between these pairs.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern, such as 'capture_desktop_screenshot', 'list_tabs', and 'open_new_tab'. This predictability makes it easy for agents to understand and use the tools without confusion from mixed naming conventions.

    Tool Count4/5

    With 20 tools, the count is slightly high but reasonable for a browser automation server that covers desktop interaction, CDP commands, and page management. It feels comprehensive without being overly bloated, though it borders on the upper limit of typical scoping.

    Completeness5/5

    The tool set provides complete coverage for browser automation, including navigation, tab management, input simulation, screenshot capture, CDP access, and diagnostics. There are no obvious gaps; agents can perform core workflows like opening URLs, interacting with pages, and debugging without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data