A
licenseNot graded
qualityB
maintenanceRecords browser sessions and provides structured context (clicks, console, network, screenshots) for AI coding agents to understand and act upon.
2
MIT
browser-dvr-mcp
by funkyfunc
Related Servers
Alternatives to browser-dvr-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceGives AI coding agents eyes into running applications by recording browser activity and providing session investigation tools for debugging.7 npm3MIT
- AlicenseNot gradedqualityDmaintenanceEnables coding agents to access recorded browser flows (user actions, network, console, etc.) for debugging and regression testing without reproducing issues.108Apache 2.0
- AlicenseNot gradedqualityDmaintenanceRecords, replays, and correlates visual and API events in the browser, enabling AI assistants to understand which API calls feed which UI elements.MIT
- AlicenseAqualityBmaintenanceTurn screen recordings into automated Playwright E2E reproduction tests, structured GitHub bug reports with clickable video timestamps, and SOP walkthroughs.611 npmMIT
- FlicenseNot gradedqualityDmaintenanceRecords browser interactions (clicks, DOM mutations, console logs, JS errors) via Chrome DevTools Protocol while you manually navigate, and provides tools to retrieve and analyze recordings for test generation.-
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
ActivityStale
ResponsivenessNo issues