Skip to main content
Glama
Sept-7-Qi

BrowserPilot MCP

by Sept-7-Qi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to BrowserPilot MCP

No user-submitted related servers found.

    Related Servers

    • Browser MCP Server

      Akioo77
      A
      license
      A
      quality
      C
      maintenance
      A browser automation tool using Playwright and MCP protocol, enabling agents like OpenClaw or Claude Desktop to control a browser for navigation, content extraction, and interaction.
      21
      6 npm
      MIT

    • MCP Browser Agent

      ashley-ha
      A
      license
      B
      quality
      D
      maintenance
      A browser automation agent that enables Claude to interact with web browsers through the Model Context Protocol, allowing for actions like navigating websites, manipulating elements, and managing browser state.
      2
      9
      MIT

    • browser-control

      kierandrewett
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control existing Chrome and Firefox browser sessions locally, including tab management, navigation, form filling, screenshots, and persistent scripts, without remote relays or debugging ports.
      9 npm
      -

    • Rod MCP Server

      aliwatters
      A
      license
      Not graded
      quality
      B
      maintenance
      Browser automation for AI agents via the Model Context Protocol, enabling web navigation, form filling, screenshots, and more using Chromium.
      MIT

    • 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
    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.4/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but close_page and close_managed_tabs overlap in function, and new_page vs ensure_active_tab could cause selection ambiguity. Descriptions help mitigate confusion.

    Naming Consistency4/5

    The majority follow a clear verb_noun pattern (list_pages, navigate_page, type_text). However, a few single-word verbs (click, hover, drag) and health_check break the pattern, creating minor inconsistency.

    Tool Count3/5

    At 22 tools, the surface is on the heavy side and includes some redundancy (close_page vs close_managed_tabs). The browser automation domain is broad, so most tools are justified, but a few could be consolidated.

    Completeness4/5

    Core browser automation operations are covered: navigation, tab management, interaction, screenshots, network/console inspection, and dialog handling. Minor gaps like direct content extraction exist but can be addressed via evaluate_script.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources