Skip to main content
Glama
Sign In
browser-dvr-mcp

browser-dvr-mcp

by funkyfunc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to browser-dvr-mcp

No user-submitted related servers found.

    Related Servers

    • FlowLens MCP

      Sasaki2454
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to inspect recorded browser flows—including user actions, network activity, console output, storage, DOM events, and screen recordings—for debugging, bug reporting, and regression testing without reproducing the issue.
      -

    • FlowLens MCP

      YuqiDunn43592
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to inspect recorded browser flows—including user actions, network activity, console logs, storage, DOM events, and screen recordings—for in-depth debugging and regression testing without reproducing the issue.
      -

    • FlowLens MCP

      halvarez469
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to access recorded browser flows—including user actions, network activity, console logs, storage, DOM events, and screen recordings—for debugging, bug reporting, and regression testing without reproducing issues.
      -

    • FlowLens MCP Server

      timothys605
      F
      license
      Not graded
      quality
      A
      maintenance
      Gives coding agents full browser context from recorded user flows, including actions, network, console, storage, DOM events, and screen recordings. Enables in-depth debugging, bug reporting, regression testing, and Playwright test generation without reproducing issues.
      -
    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

    A3.8/5.0

    Scored across 62 tools

    Disambiguation4/5

    Most tools have distinct purposes, but the high number of tools (62) with overlapping categories like visual capture (stream_screencast, browser_screenshot, browser_dump_dvr) and analysis (browser_explain_last_action, browser_analyze_run) could cause occasional confusion. However, detailed descriptions mitigate ambiguity.

    Naming Consistency3/5

    Many tools follow the 'browser_' prefix, but several core tools (atomic_interact, get_semantic_surface, stream_screencast, etc.) lack this prefix, creating inconsistency. All use snake_case, but the pattern is mixed.

    Tool Count3/5

    With 62 tools, the server is on the heavy side. While the broad scope of browser automation (navigation, interaction, recording, time travel, learning) justifies many tools, the count is above typical MCP servers, potentially overwhelming agents.

    Completeness5/5

    The toolset covers an exhaustive range of browser automation needs: navigation, interaction, perception, recording, replay, time travel, human handoff, skill learning, storage, network simulation, accessibility, performance, and debugging. No obvious gaps are present.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources