Skip to main content
Glama
PremierStudio

BrowserAgent

Official
by PremierStudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to BrowserAgent

No user-submitted related servers found.

    Related Servers

    • Web Bridge

      JohnXu22786
      A
      license
      A
      quality
      B
      maintenance
      Browser automation MCP server that uses a real browser to give agents eyes and hands—open pages, click, fill, screenshot, and run scripts via accessibility-tree snapshots.
      22
      20 npm
      MIT

    • SnapRef

      nstranquist
      A
      license
      Not graded
      quality
      B
      maintenance
      Policy-gated MCP server for local-first browser automation, enabling agents to drive isolated Chromium sessions via snapshots, revision-bound refs, typed actuation, scripts, and telemetry receipts.
      Apache 2.0

    • MCP Master Puppeteer

      flrngel
      F
      license
      Not graded
      quality
      D
      maintenance
      An advanced MCP server for browser automation using Puppeteer, specifically optimized for token efficiency through minimal data returns and progressive enhancement. It enables agents to navigate pages, capture LLM-optimized screenshots, extract structured content, and perform batch interactions.
      3
      -

    • 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
      -

    • nexus-browser-mcp

      paipaipai666
      A
      license
      B
      quality
      B
      maintenance
      A browser-automation MCP server built on Playwright that provides deterministic snapshots via MutationObserver/requestAnimationFrame, HITL governance, multi-task isolation, and self-healing browser sessions for LLM-driven browsing.
      25
      29 PyPI
      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.2/5.0

    Scored across 26 tools

    Disambiguation5/5

    Each tool targets a distinct function: lifecycle, tabs, page interactions, flows, verification, and task management. Even similar operations like observe and watch_until differ in immediate read vs. polling. No overlapping purposes that would cause misselection.

    Naming Consistency3/5

    Naming follows a mixed convention: browser_ prefix for lifecycle/tab tools, single verbs for actions (observe, click, type), and verb_noun for flows/tasks (compile_flow, get_task). While readable, the inconsistency is noticeable and could be more uniform (e.g., all verb_noun).

    Tool Count3/5

    At 26 tools, the set is on the heavier side, slightly exceeding the typical well-scoped range. The breadth is justified by the broad scope of browser automation, but it could benefit from consolidation (e.g., merging task fallback tools) to stay under 25.

    Completeness4/5

    The surface covers lifecycle, tab management, element interaction, navigation, flow execution, verification, and task handling. Minor gaps like explicit page reload or download handling exist, but most workflows are supported without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources