A
licenseB
qualityC
maintenanceEnables AI agents to inspect and control a live Chromium browser for frontend debugging, providing console logs, network requests, DOM snapshots, and accessibility analysis.
19
8 npm
MIT
web-ui-tester
by hofmeister
Related Servers
Alternatives to web-ui-tester
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to autonomously interact with and test web applications in a real browser, providing DOM/Accessibility tree extraction, runtime telemetry, screenshot capture, and Markdown test reports.32 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to drive a real Chrome browser using text-only accessibility-tree snapshots, with tools for navigation, interaction, and persistent task-space management.MIT
- AlicenseCqualityAmaintenanceEnables AI agents and developers to automate real Chrome/Chromium browsers through the Chrome DevTools Protocol, with token-efficient snapshots, multi-action batching, shadow DOM traversal, system-page control, extension management, and network/WebSocket inspection.64MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to control and inspect a live Chrome browser for automated web debugging, performance analysis, and Lighthouse audits. It allows agents to capture screenshots, monitor network requests, and measure Core Web Vitals using plain-English prompts.1,516,489 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables LLM agents to drive a selector-free browser through natural language, so they can debug styling and console errors, map and document web apps, and generate or run end-to-end and exploratory tests without screenshots.197 npm103MIT
TDQS
A4/5.0
Scored across 23 tools
Disambiguation5/5
Every tool has a clearly distinct purpose: session management, navigation, interaction primitives, inspection methods, network/console diagnostics, and a delegation agent. Even overlapping ones like snapshot/query/read_text/inspect_element are well-differentiated by their descriptions (full tree vs. targeted search vs. text extraction vs. devtools-style detail).
Naming Consistency5/5
All browser_* tools follow a consistent verb_noun pattern (e.g., browser_click, browser_type, browser_network), and run_task follows the same convention. No mixed styles or unpredictable naming.
Tool Count4/5
23 tools is on the heavier side, but each tool addresses a distinct need for comprehensive browser automation—session, navigation, interaction, waiting, dialogs, inspection, diagnostics, and delegation. It is slightly above the ideal range but justified by the scope of the domain.
Completeness5/5
The tool surface covers the full lifecycle of UI testing: session management, navigation, interaction, asynchronous waits, dialog handling, multiple inspection modes, console/network diagnostics, JavaScript evaluation, and a delegated agent for high-level tasks. No obvious dead ends or missing critical operations.
Maintenance
ActivityMaintained
ResponsivenessNo issues