Glance
Related Servers
Alternatives to Glance
No user-submitted related servers found.
Related Servers
- 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
- 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 gradedqualityAmaintenanceAn MCP server that gives Claude Code a real browser to navigate, click, type, screenshot, and inspect pages via accessibility snapshots. It also runs multi-step test scenarios with assertions, session recording, visual regression, and console/network monitoring from the terminal.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 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
- AlicenseAqualityBmaintenanceAn MCP server that gives Claude direct control of a real browser via Playwright, enabling AI-driven web testing, autonomous test execution, and live failure analysis through natural language.83,485 npm3MIT
TDQS
Scored across 32 tools
Tool names are mostly distinct, with browser_* and test_* prefixes clearly separating categories. However, some potential overlap exists between browser_screenshot and browser_snapshot, and test_fill_form could be confused with browser_type. Overall, the names are specific enough for an agent to differentiate.
All tools follow a consistent pattern of prefix_object_action (e.g., browser_navigate, test_scenario_run, session_start). This uniformity makes the set predictable and easy to navigate.
With 32 tools, the count is high but appropriate for a comprehensive browser automation and testing server. Each tool seems justified given the domain (browser control, testing, sessions, visual checks), though a slight reduction could improve simplicity.
The tool surface covers major browser interactions, testing scenarios, session management, and visual comparisons. Missing elements like network mocking or cookie management are notable, but core workflows appear well-supported.