Skip to main content
Glama
huaka1

browser-mcp

by huaka1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to browser-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-server-agent-browser

      codeChap
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that wraps agent-browser to let LLMs control a real browser, providing tools for navigation, interaction, reading page content, accessibility snapshots, screenshots, and session management.
      1
      -

    • Web Bridge

      JohnXu22786
      A
      license
      A
      quality
      B
      maintenance
      Browser automation MCP server that uses a real browser to give agents eyes and hands—open pages, click, fill, screenshot, and run scripts via accessibility-tree snapshots.
      22
      24 npm
      MIT

    • Echo

      krishngohel
      A
      license
      Not graded
      quality
      A
      maintenance
      Local browser MCP server that lets AI assistants control a real desktop browser via tools like navigate, snapshot, and search_web.
      MIT

    • stealth-agent-browser-mcp

      ykshah1309
      A
      license
      A
      quality
      D
      maintenance
      An MCP server providing AI agents with a stealth Chromium browser that uses hybrid accessibility-object-model and set-of-mark vision for token-lean snapshots and reliable action via ref ids.
      13
      58 npm
      1
      Apache 2.0

    • a11ydriver-mcp

      idugeni
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to control Chrome via DevTools CDP and accessibility trees, providing 21 tools for browser automation including tab management, navigation, interactions, and page capture.
      -
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A4.1/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool has a unique and clear purpose: navigate, click, type, scroll, press keys, snapshot, console, images, network logs, intercept, export steps, list steps, and vision. No two tools overlap in function.

    Naming Consistency5/5

    All tools follow the consistent pattern 'browser_verb[_noun]' in snake_case (e.g., browser_navigate, browser_get_network_logs). No mixing of conventions.

    Tool Count5/5

    15 tools cover the core browser automation domain without being excessive. The count is well-scoped for navigation, interaction, debugging, and recording.

    Completeness5/5

    The tool surface covers navigation, DOM interaction, snapshot, screenshot, console, network logging, request interception, and step recording/exporting. No obvious gaps for standard browser automation tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources