Skip to main content
Glama
Nirmalraj10567

agent-browser

by Nirmalraj10567
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to agent-browser

No user-submitted related servers found.

    Related Servers

    • openmcp

      openmcp-pro
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to automate web tasks such as browsing, clicking, typing, and taking screenshots via the Model Context Protocol.
      1
      MIT

    • Playwright Automation MCP

      devqa07
      F
      license
      A
      quality
      D
      maintenance
      Enables AI-powered browser automation controlled through natural language, integrating Playwright with the Model Context Protocol to perform web interactions like navigation, form filling, and screenshots.
      10
      -

    • stealthy-auto-browse MCP

      psyb0t
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control a stealthy browser via the Model Context Protocol, supporting navigation, screenshots, clicking, typing, and more.
      78
      Do What The F*ck You Want To Public
    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

    C2.4/5.0

    Scored across 39 tools

    Disambiguation5/5

    Each tool targets a distinct browser operation (e.g., click, fill, hover, scroll) with no overlapping responsibilities. Even similar tools like get and read are differentiated by specific data returning or page fetching, and snapshot is distinct from screenshot.

    Naming Consistency5/5

    All tools follow a consistent 'browser_<verb>' pattern (e.g., open, click, fill, type, press), with no mixed conventions or vague names. The naming is predictable and clearly conveys each tool's action.

    Tool Count2/5

    With 39 tools, the count exceeds the typical range and feels heavy for most workflows. While the browser automation domain is broad, many tools are granular (e.g., browser_console, browser_trace), leading to potential selection overhead.

    Completeness4/5

    The tool set covers a comprehensive range of browser interactions: navigation, element actions, state management, debugging, performance monitoring, and network control. Minor gaps exist (e.g., file upload, form submission explicit handling), but most core workflows are well-supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources