A
licenseNot graded
qualityC
maintenanceEnables AI agents to perform end-to-end web testing by controlling a real browser through tools for navigation, interaction, state inspection, screenshots, and script evaluation.
MIT
QA Agent Pro
by samusilv
Related Servers
Alternatives to QA Agent Pro
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables 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,305,336 npmApache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a browser for web automation tasks like navigation, typing, clicking, and taking screenshots.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a browser for web automation tasks such as navigation, typing, clicking, and taking screenshots.-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser through Chrome DevTools. Provides browser automation, performance analysis, debugging capabilities, and network request monitoring.1,305,336 npm53,581Apache 2.0
- AlicenseBqualityDmaintenanceEnables AI coding assistants to control a persistent Chrome browser through DevTools Protocol. Supports web navigation, screenshots, element interaction, mobile testing, console logs, and network debugging in a stable Docker environment.108MIT
TDQS
A3.5/5.0
Scored across 7 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlap: click, get_console_logs, get_text, navigate, screenshot, set_viewport, and type all target specific, non-overlapping browser automation tasks. An agent can easily tell them apart based on their unique functions.
Naming Consistency5/5
All tool names follow a consistent verb_noun or verb pattern with snake_case: click, get_console_logs, get_text, navigate, screenshot, set_viewport, and type. This predictable naming scheme makes the set easy to understand and use.
Tool Count5/5
With 7 tools, the count is well-scoped for a QA/browser automation server. Each tool earns its place by covering essential actions like navigation, interaction, and debugging without being overwhelming or too sparse.
Completeness4/5
The toolset covers core QA workflows: navigation, interaction (click, type), content retrieval (get_text, get_console_logs), and configuration (set_viewport, screenshot). Minor gaps exist, such as missing tools for handling alerts or cookies, but agents can work around these with the provided tools.
Maintenance
ActivityInactive
ResponsivenessNo issues