A
licenseNot graded
qualityC
maintenanceMCP server for extracting UI components, design tokens, and patterns from websites and generating production-ready React, Vue, and HTML components.
MIT
browser-mcp
by hupeng9995
Related Servers
Alternatives to browser-mcp
No user-submitted related servers found.
Related Servers
- -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
- AlicenseNot gradedqualityBmaintenanceAn open-source MCP server that lets AI agents investigate existing websites or applications with a real browser and static analysis, then rebuild functional alternatives through a dependency-ordered, test-driven loop. It provides persistent project state, task-scoped build context, runner execution, and browser-based validation that scores the rebuild's fidelity against the original.MIT
- FlicenseNot gradedqualityBmaintenanceThis MCP server enables users to convert web page DOM structures into accessibility trees, filter non-interactive elements, generate robust CSS/XPath locators, and compile goal-driven multi-step browser automation plans with verification.7-
- 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
TDQS
A3.5/5.0
Scored across 11 tools
Disambiguation4/5
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.
Naming Consistency5/5
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.
Tool Count5/5
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.
Completeness3/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues