browser-mcp
Related Servers
Alternatives to browser-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for extracting UI components, design tokens, and patterns from websites and generating production-ready React, Vue, and HTML components.-
- -licenseNot gradedqualityNot gradedmaintenanceMCP server that captures a website's full design and content, producing a downloadable Next.js clone package with tokens, components, and a rebuild guide.-
- AlicenseNot gradedqualityDmaintenanceMCP server that extracts accessibility tree, design tokens, screenshots, Claude DSL, and Figma JSON from any URL using a persistent Chromium browser with zero LLM cost.MIT
- AlicenseCqualityAmaintenanceMCP server for browser automation that drives Chrome via an extension, preserving login state and offering 45 tools for navigation, interaction, scraping, and screenshots.535MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that measures how faithfully one UI reproduces another, returning a score and actionable findings for improvement.1MIT
- AlicenseAqualityDmaintenanceAn MCP server that uses headless Chromium (Puppeteer) to capture pixel-perfect screenshots and extract DOM from URLs, with LLM-friendly step-based workflows.213 npm3MIT
TDQS
Scored across 11 tools
Most tools have distinct purposes, but there is minor overlap between get_element_by_selector and get_element_styles (both return style info) and between download_assets and get_fonts (both list fonts). Overall, the boundaries are clear enough for an agent.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., analyze_layout, download_assets, get_element_styles). Even single-word tools like 'navigate' and 'screenshot' fit the imperative style. No mixing of conventions.
With 11 tools, the server is well-scoped for browser inspection and debugging tasks. Each tool covers a clear aspect (navigation, HTML, CSS, layout, assets, scripts, screenshots) without redundancy or bloat.
The tools cover static analysis well but lack interactive capabilities such as clicking, form filling, cookie management, or network request interception. This may leave agents unable to perform dynamic browser automation tasks.