Skip to main content
Glama
IlGabbia998

Browser MCP

by IlGabbia998
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Browser MCP

No user-submitted related servers found.

    Related Servers

    • chrome-agent-browser

      oscs1024-pixel
      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.
      MIT

    • chrometools-mcp

      docentovich
      A
      license
      B
      quality
      D
      maintenance
      Enables AI-powered Chrome automation through natural language, providing 56+ specialized tools for browser interaction, page analysis, scenario recording, and visual testing.
      59
      24 npm
      9
      ISC

    • mcp-browser-agent

      yubao2000
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to control a browser with 30 tools for navigation, interaction, extraction, and tab management, supporting human-like browser automation.
      36
      3 npm
      MIT

    • agent-browser-mcp-server

      hughedward
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides complete browser automation capabilities for AI agents via 44 tools, including navigation, element interaction, state management, and session recording.
      583 npm
      1
      Apache 2.0

    • agent-browser-mcp

      335234131
      A
      license
      B
      quality
      F
      maintenance
      Enables AI agents to directly control your real Chrome browser with full context including login sessions, cookies, and open tabs. It provides tools for page scanning, JavaScript execution, CDP control, screenshots, and physical mouse/keyboard input for authentic browser automation.
      20
      243
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 39 tools

    Disambiguation4/5

    Most tools are clearly distinct, but browser_console_log and browser_get_console_logs are easily confused, and browser_wait/browser_wait_for could be ambiguous without reading descriptions. Overall, the purposes are well differentiated.

    Naming Consistency4/5

    All tools use a consistent browser_ prefix and snake_case naming. However, there is a mix of verb-first (navigate, click) and noun-like (console_log, network_log) patterns, and some tools use 'get_' while others don't, creating minor inconsistency.

    Tool Count2/5

    With 39 tools, the server exceeds the 25+ threshold for 'too many'. While the breadth reflects a comprehensive browser automation scope, the sheer number makes tool selection heavier and suggests possible consolidation.

    Completeness4/5

    The tool set covers navigation, interaction, waiting, extraction, cookies/storage, console/network monitoring, and tab management—nearly all core browser automation needs. Minor gaps exist (e.g., no explicit alert/dialog handling or dedicated URL/page title getter), but most can be worked around via execute_js or snapshot.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources