chromium-arm64
Related Servers
Alternatives to chromium-arm64
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceAn MCP server that gives Claude Code real browser control for web automation, testing, and screenshots.3281 npm157MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that gives Claude Code a real browser for navigation, interaction, screenshots, and end-to-end testing, including assertions, session recording, visual regression, and console/network monitoring.106 npmMIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that gives Claude Code a real browser, enabling it to navigate, click, type, screenshot, and inspect web pages during development. It also supports multi-step JSON test scenarios, assertions, session recording, and visual regression testing against web apps.106 npmMIT
- AlicenseNot gradedqualityAmaintenanceThis MCP server gives Claude Code a real browser to navigate, click, type, screenshot, and test web applications from the terminal. It supports multi-step scenarios, assertions, session recording, visual regression, and console/network monitoring.106 npmMIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that gives Claude Code a real browser, enabling navigation, clicking, form filling, screenshots, and accessibility snapshots directly from the terminal. It also supports multi-step JSON test scenarios, assertions, session recording, and visual regression testing with network and console monitoring.106 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that gives Claude Code control of a real browser, letting it navigate pages, click and type, capture screenshots, read accessibility snapshots, and run multi-step test scenarios with assertions. It also supports session recording, visual regression comparison, and network/console monitoring with configurable security profiles.106 npmMIT
TDQS
Scored across 22 tools
Most tools have distinct purposes, such as click, fill, navigate, and screenshot, with clear boundaries. However, some overlap exists between the various audit tools (e.g., run_accessibility_audit, run_best_practices_audit, run_performance_audit, run_seo_audit, run_nextjs_audit, run_audit_mode), which could cause confusion as their specific scopes might not be immediately clear from the names alone, though descriptions help differentiate them.
The tool names follow a highly consistent snake_case pattern with clear verb_noun structures, such as click, close_browser, evaluate, fill, get_console_errors, navigate, run_accessibility_audit, and screenshot. There are no deviations in naming conventions, making the set predictable and easy to understand.
With 22 tools, the count is borderline high for a browser automation and auditing server, as it might feel heavy and potentially overwhelming. While it covers many aspects, some tools could be consolidated (e.g., multiple audit tools), suggesting a slight over-scoping that could impact usability.
The tool set provides comprehensive coverage for browser automation and auditing, including navigation, interaction (click, fill, select), content retrieval (get_content, get_console_logs), debugging (run_debugger_mode, get_network_errors), audits (performance, SEO, accessibility), and maintenance (close_browser, wipe_logs). There are no obvious gaps, and agents can handle full workflows from setup to analysis.