Skip to main content
Glama
OMGEverdo

browser-pool-mcp

by OMGEverdo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to browser-pool-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-unified-automation

      gugosf114
      F
      license
      Not graded
      quality
      D
      maintenance
      A custom MCP server for Playwright browser automation and system control, providing 25 tools to enable Claude Code to perform web interactions and system tasks via natural language.
      -

    • mcp-browser-automation

      ritesh-jain
      F
      license
      B
      quality
      D
      maintenance
      An MCP server for generic browser automation using Playwright. Enables MCP clients to navigate pages, inspect elements, execute JavaScript, capture screenshots, and monitor console logs and network traffic via a headless Chromium instance.
      7
      -

    • playwright-mcp-server

      doucej
      A
      license
      A
      quality
      F
      maintenance
      Stateful MCP server wrapping Playwright for browser automation. Provides tools to navigate, interact, and extract data from web pages via a persistent browser session.
      19
      673 npm
      MIT
    • @browserview/mcp by browserview

      @browserview/mcpofficial

      browserview
      A
      license
      A
      quality
      C
      maintenance
      MCP server for browserview.io that lets agents create, inspect, share, and destroy disposable cloud Chromium sessions, and connect via CDP using Playwright or Puppeteer.
      6
      3 npm
      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

    C2.3/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific browser interactions like clicking, typing, navigating, or taking screenshots. However, 'browser_evaluate' (run JavaScript) and 'browser_snapshot' (page snapshot) could potentially overlap with other tools in functionality, creating minor ambiguity in certain scenarios.

    Naming Consistency5/5

    Tool names follow a highly consistent snake_case pattern with clear 'browser_' or 'pool_' prefixes, making them predictable and readable. The verb_noun structure is maintained throughout, such as 'browser_click', 'browser_navigate', and 'pool_status', ensuring no mixing of conventions.

    Tool Count3/5

    With 20 tools, the count is borderline heavy for a browser automation server, potentially overwhelming for agents. While it covers many interactions, some tools like 'browser_snapshot' and 'browser_screenshot' might be redundant, suggesting the set could be more streamlined without losing core functionality.

    Completeness4/5

    The toolset provides comprehensive coverage for browser automation, including navigation, interaction, debugging, and pool management. Minor gaps exist, such as no explicit tool for handling cookies or local storage, but agents can likely work around these using existing tools like 'browser_evaluate' for JavaScript execution.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources