Frontend Bug Investigator MCP
Related Servers
Alternatives to Frontend Bug Investigator MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding agents to open and exercise web applications in an isolated Chromium browser, capture screenshots and runtime/network diagnostics, and run deterministic page checks with linked evidence.121MIT
- FlicenseAqualityCmaintenanceReproduces and verifies website bug tickets in a real browser, returning annotated video, Playwright trace, screenshots, logs, and a verdict per acceptance criterion.18-

QualityMax QA MCPofficial
AlicenseAqualityAmaintenanceEnables coding agents to independently verify web changes by scanning pages, inspecting UI structure, generating Playwright reproductions, and executing tests with structured QA evidence.404MIT- AlicenseAqualityBmaintenanceGives AI agents a real Chromium browser via Playwright to QA-test web apps, with pass/fail assertions, network mocking, recorded traces and reports, and safety guards that block live payment traffic. Test outcomes come back as explained verdicts suitable for review or email delivery.18MIT
- AlicenseAqualityAmaintenanceEnables AI agents to run, debug, and inspect Playwright end-to-end tests, returning structured pass/fail stats, failure diagnostics with actionable fix hints, live DOM inspection, selector validation, visual diffs, and flakiness verdicts instead of raw test output.111,348 npmMIT
- AlicenseAqualityCmaintenanceEnables AI coding agents to diagnose and repair Python Selenium UI automation using real evidence from live DOM and test runs, with enforced safety boundaries and verifiable fixes.2MIT
TDQS
Scored across 7 tools
Each tool maps to a distinct stage in the investigation lifecycle: start, reproduce, collect, analyze, report, regression test, and close. Although start_investigation, reproduce_issue, and collect_evidence all touch evidence, their boundaries are clearly described and operationally separate.
All tools use a consistent snake_case verb_noun pattern, such as start_investigation, collect_evidence, and generate_bug_report. The naming is predictable across the entire set.
Seven tools is well-scoped for a single-investigation workflow and each tool has a clear role. There are no redundant or filler tools.
The surface covers the full lifecycle from opening a target and reproducing actions through evidence collection, deterministic analysis, report generation, regression test generation, and cleanup. No obvious operation is missing for the stated purpose.