A
licenseNot graded
qualityB
maintenanceEnables AI assistants to inspect web pages, monitor network requests, extract HTML, analyze console output, and examine DOM elements in real-time through a Playwright-powered browser.
19
7
MIT
Web Inspector MCP
by antonzherdev
Related Servers
Alternatives to Web Inspector MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to control web browsers through Playwright automation, providing 50+ tools for navigation, interaction, testing, accessibility audits, and visual testing across Chromium, Firefox, and WebKit.8MIT
- FlicenseNot gradedqualityDmaintenanceEnables web browser automation and inspection using structured data instead of screenshots, allowing AI agents to interact with web pages programmatically through the Playwright framework.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to automate and debug real Chromium browsers with capabilities like screenshots, video recording, performance analysis, visual regression testing, and OCR text extraction.13-
- AlicenseAqualityDmaintenanceEnables AI assistants to perform browser automation using Playwright, including navigation, content extraction, screenshot analysis, and custom script execution.517MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to control browser automation through natural language prompts using Playwright, supporting visual element interaction, PDF generation, screenshots, and testing assertions.-
TDQS
A3.8/5.0
Scored across 34 tools
Disambiguation4/5
Tools are mostly distinct with clear purposes, but there are many inspection tools (inspect_dom, query_selector, get_html, get_text, find_by_text, element_exists) that could be confused without careful reading. Descriptions are detailed and differentiate them well, so only a slight risk of misselection.
Naming Consistency5/5
All 34 tools follow a consistent snake_case naming convention with verb-first patterns (e.g., navigate, scroll_by, get_console_logs, inspect_ancestors). There are no mixed styles or ambiguous verbs, making the naming predictable and clear.
Tool Count3/5
With 34 tools, the server is on the heavy side but justified by the broad domain (inspection, interaction, network, console, screenshots). It exceeds the 25-tool threshold for 'too many', but the comprehensiveness and token-efficient specialized tools make it borderline acceptable rather than excessive.
Completeness5/5
The tool surface covers the full lifecycle of web inspection: navigation, interaction (click, fill, scroll, hover, drag), DOM inspection (structure, text, HTML, styles, box model), waiting, network monitoring, console logs, screenshots, and custom JS. No major gaps; even obscure aspects like color scheme and test IDs are addressed.
Maintenance
ActivityInactive
ResponsivenessUnresponsive