Skip to main content
Glama
funkyfunc

browser-dvr-mcp

by funkyfunc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to browser-dvr-mcp

No user-submitted related servers found.

    Related Servers

    • Krometrail

      nklisch
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI coding agents eyes into running applications by recording browser activity and providing session investigation tools for debugging.
      6 npm
      3
      MIT

    • FlowLens MCP Server

      magentic
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables coding agents to access recorded browser flows (user actions, network, console, etc.) for debugging and regression testing without reproducing issues.
      110
      Apache 2.0

    • browsertrack

      litepacks
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to access local browser diagnostics—runtime errors, console logs, network failures, breadcrumbs, DOM snapshots, and screenshots—and run closed-loop verification to debug and confirm fixes.
      13 npm
      -
    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources