Skip to main content
Glama
soulxyz

BrowserPilot

by soulxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to BrowserPilot

No user-submitted related servers found.

    Related Servers

    • browser-mcp

      Tuanm
      F
      license
      Not graded
      quality
      B
      maintenance
      Exposes your Chrome/Edge browser as MCP tools for AI agents, enabling browser automation through a Chrome extension with 47 tools for navigation, interaction, page reading, and more.
      18 npm
      -

    • Chrome MCP Bridge

      randyrt
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control and interact with a Chrome browser via MCP, providing tools for navigation, screenshots, clicking, form filling, content extraction, and tab management.
      -

    • Browserbeam MCP Server

      nyku
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables real browser automation as tools in Cursor, Claude Desktop, Windsurf, and any MCP-compatible client, allowing AI agents to interact with web pages through natural language.
      5 npm
      MIT

    • BrowserPilot

      cxcboss
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to control a Chrome browser through natural language, supporting navigation, interaction, tab management, and data extraction.
      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 17 tools

    Disambiguation5/5

    Each tool targets a distinct browser action or data source: navigation, input, state capture, console/network inspection, tab management, and waiting. Even similar-looking tools like browser_snapshot and browser_take_screenshot are clearly separated by accessibility tree vs visual image.

    Naming Consistency4/5

    All tools share a consistent browser_ prefix and snake_case style, which makes the set feel uniform. However, naming mixes verb-phrases like browser_navigate and browser_click with noun-phrases like browser_console_messages, browser_snapshot, and browser_tabs.

    Tool Count4/5

    At 17 tools, the set is slightly above the typical 3-15 sweet spot, but the breadth is justified by browser automation needs: navigation, mouse/keyboard input, form handling, screenshots, network/console inspection, and tab management all require separate primitives.

    Completeness4/5

    The tool surface covers the core browser automation lifecycle well: navigate, interact, inspect, wait, and manage tabs. Obvious gaps like browser_reload, browser_close, or cookie management are minor because they can be worked around with browser_evaluate or the existing tab management tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources