opción
HogarHogar Skill Herramientas MCP browser-devtools-mcp

Integra Chrome DevTools y la automatización del navegador a través de MCP para la inspección en tiempo real de la interfaz de usuario, flujos de trabajo de «captura de pantalla a código» y depuración visual. Tiende un puente entre el diseño y la implementación.

...Expandir todo
48
Tiempo actualizado 29 de junio de 2026

Acerca de browser-devtools-mcp

La habilidad « browser-devtools-mcp » permite la integración con la automatización del navegador y Chrome DevTools a través del Protocolo de Contexto de Modelo (MCP). Está diseñada para facilitar la inspección en tiempo real de la interfaz de usuario, el análisis basado en capturas de pantalla y la depuración visual, conectando modelos de lenguaje a entornos de navegador en ejecución. Este enfoque permite la observación directa de interfaces reales, lo que hace posible analizar diseños, estilos y el comportamiento de renderizado en contexto, en lugar de basarse únicamente en código estático.

La habilidad destaca capacidades como la captura de capturas de pantalla de páginas en tiempo real, la extracción de instantáneas de accesibilidad, la inspección de CSS y estilos calculados, la interacción con elementos de la página, la navegación entre páginas, el cambio de tamaño de la ventana de visualización del navegador y la realización de evaluaciones dentro del contexto del navegador. Admite flujos de trabajo como la conversión de capturas de pantalla a código, las pruebas de regresión visual, la extracción de tokens de diseño y la depuración de problemas de diseño con retroalimentación visual inmediata. A través de la interfaz estandarizada de MCP y las sesiones con estado, estas interacciones pueden gestionarse de forma coherente, manteniendo al mismo tiempo unos permisos controlados.

Esta skill está dirigida a desarrolladores, ingenieros, diseñadores y especialistas en automatización que trabajan en interfaces de usuario y necesitan herramientas fiables para tender un puente entre el diseño y la implementación. Resulta especialmente útil en escenarios que implican la validación de la interfaz de usuario, las pruebas visuales automatizadas, la creación rápida de prototipos y el desarrollo iterativo de interfaces, en los que la retroalimentación directa a nivel del navegador mejora la precisión y la eficiencia.

Preguntas frecuentes

¿Cuál es el objetivo principal de esta skill?

Conecta la automatización del navegador con las capacidades de Chrome DevTools a través de MCP para permitir la inspección en tiempo real de la interfaz de usuario, la captura de capturas de pantalla, la interacción y los flujos de trabajo de depuración visual.

¿Qué tipos de flujos de trabajo admite?

Admite procesos de conversión de capturas de pantalla a código, pruebas de regresión visual, depuración de maquetación, extracción de tokens de diseño y flujos de trabajo de desarrollo basados en la vista previa en tiempo real.

¿Esta habilidad requiere la integración con MCP?

Sí. Se basa en el Protocolo de Contexto de Modelo (MCP), que proporciona una interfaz estandarizada, comunicación bidireccional, sesiones con estado y límites de permisos para las interacciones entre herramientas.

¿A qué capacidades del navegador se puede acceder?

Permite la navegación, el cambio de tamaño, la captura de capturas de pantalla, las instantáneas de accesibilidad, la interacción con elementos, la inspección de estilos y la evaluación en el propio navegador a través de las herramientas de navegador compatibles con MCP.

Ver en GitHub

Browser DevTools MCP Integration

Leverage browser automation and DevTools through MCP (Model Context Protocol) for live UI inspection, screenshot-to-code workflows, and visual debugging. This skill enables direct observation and manipulation of running interfaces.

When to Use This Skill

  • Capturing screenshots of live UIs for analysis
  • Inspecting CSS and computed styles programmatically
  • Implementing screenshot-to-code workflows
  • Debugging layout issues with visual feedback
  • Extracting design tokens from existing sites
  • Automating visual regression testing
  • Building live preview workflows

MCP Architecture Overview

What is MCP?

Model Context Protocol (MCP) is Anthropic's standard for connecting LLMs to external tools. It provides:

  • Standardized tool interface - Consistent way to expose capabilities
  • Bidirectional communication - Tools can query the model
  • Stateful sessions - Maintain context across interactions
  • Permission boundaries - Control what tools can do

Browser MCP Landscape

+-------------------+     +-------------------+     +-------------------+|   Playwright MCP  |     |   Puppeteer MCP   |     | Chrome DevTools   ||   (Full browser)  |     |   (Headless)      |     | Protocol (CDP)    |+-------------------+     +-------------------+     +-------------------+         |                         |                         |         +-----------+-------------+-----------+-------------+                     |                         |              +------v------+           +------v------+              | Screenshot  |           |  Element    |              | Capture     |           |  Inspection |              +-------------+           +-------------+                     |                         |              +------v------+           +------v------+              | Visual      |           |  Style      |              | Comparison  |           |  Extraction |              +-------------+           +-------------+

Core MCP Tools for UI Work

Available Browser MCP Tools

When using Playwright MCP (common in Claude Code):

// Navigation and page controlmcp__playwright__browser_navigate({ url: string })mcp__playwright__browser_navigate_back()mcp__playwright__browser_close()mcp__playwright__browser_resize({ width: number, height: number })// Screenshots and visual capturemcp__playwright__browser_take_screenshot({  filename?: string,  fullPage?: boolean,  type?: "png" | "jpeg",  element?: string,  // Human-readable description  ref?: string       // Element reference from snapshot})// Accessibility snapshots (better than screenshots for structure)mcp__playwright__browser_snapshot({  filename?: string  // Optional: save to file})// Interactionsmcp__playwright__browser_click({ element: string, ref: string })mcp__playwright__browser_type({ element: string, ref: string, text: string })mcp__playwright__browser_hover({ element: string, ref: string })// Form handlingmcp__playwright__browser_fill_form({ fields: FormField[] })// Evaluationmcp__playwright__browser_evaluate({ function: string, element?: string, ref?: string })// Tab managementmcp__playwright__browser_tabs({ action: "list" | "new" | "close" | "select" })

Screenshot-to-Code Workflows

Workflow 1: Direct Screenshot Analysis

Capture and analyze a live UI for recreation:

class ScreenshotToCodeWorkflow:    """    Convert a screenshot of a UI into working code.    """    async def capture_and_analyze(self, url: str) -> CodeOutput:        # Step 1: Navigate to target        await mcp.browser_navigate(url=url)        # Step 2: Wait for full render        await mcp.browser_wait_for(time=2)        # Step 3: Take high-quality screenshot        screenshot = await mcp.browser_take_screenshot(            filename="capture.png",            fullPage=False,            type="png"        )        # Step 4: Get accessibility snapshot for structure        snapshot = await mcp.browser_snapshot()        # Step 5: Analyze with vision + structure        analysis = await self.analyze_screenshot(screenshot, snapshot)        # Step 6: Generate code        code = await self.generate_code(analysis)        return code    async def analyze_screenshot(self, screenshot: str, snapshot: str) -> UIAnalysis:        """        Combine visual and structural analysis.        """        prompt = f"""        Analyze this UI screenshot and accessibility snapshot.        ## Accessibility Snapshot (Structure)        {snapshot}        ## Analysis Tasks        1. **Layout Structure**           - Identify major sections (header, sidebar, main, footer)           - Determine grid/flexbox patterns           - Note responsive breakpoint hints        2. **Visual Elements**           - Extract color palette (background, text, accent)           - Identify typography (font family, sizes, weights)           - Note spacing patterns        3. **Components**           - List all UI components visible           - Describe their visual treatment           - Note interactive elements        4. **Design System Inference**           - What design system might this be based on?           - What are the governing principles?        Output as structured JSON.        """        return await self.llm.analyze_image(screenshot, prompt)

Workflow 2: Element-Specific Extraction

Extract and recreate specific elements:

class ElementExtractionWorkflow:    """    Extract and recreate specific UI elements.    """    async def extract_element(self, url: str, selector: str) -> ElementCode:        # Navigate to page        await mcp.browser_navigate(url=url)        # Get page snapshot to find element        snapshot = await mcp.browser_snapshot()        # Find element reference in snapshot        ref = self.find_element_ref(snapshot, selector)        # Take element-specific screenshot        element_screenshot = await mcp.browser_take_screenshot(            element=f"Target element: {selector}",            ref=ref        )        # Extract computed styles via evaluation        styles = await mcp.browser_evaluate(            function="""            (element) => {                const computed = window.getComputedStyle(element);                return {                    display: computed.display,                    flexDirection: computed.flexDirection,                    padding: computed.padding,                    margin: computed.margin,                    backgroundColor: computed.backgroundColor,                    color: computed.color,                    fontSize: computed.fontSize,                    fontWeight: computed.fontWeight,                    borderRadius: computed.borderRadius,                    boxShadow: computed.boxShadow,                };            }            """,            element=f"Target element: {selector}",            ref=ref        )        # Generate code from extracted data        return await self.generate_element_code(element_screenshot, styles)

Workflow 3: Design Token Extraction

Extract design tokens from a live site:

class TokenExtractionWorkflow:    """    Extract design tokens from a live website.    """    async def extract_tokens(self, url: str) -> DesignTokens:        await mcp.browser_navigate(url=url)        # Extract colors from key elements        colors = await mcp.browser_evaluate(            function="""            () => {                const elements = document.querySelectorAll(                    'button, a, h1, h2, h3, p, [class*="bg-"], [class*="text-"]'                );                const colors = new Set();                elements.forEach(el => {                    const style = window.getComputedStyle(el);                    colors.add(style.color);                    colors.add(style.backgroundColor);                    colors.add(style.borderColor);                });                return Array.from(colors).filter(c => c !== 'rgba(0, 0, 0, 0)');            }            """        )        # Extract typography        typography = await mcp.browser_evaluate(            function="""            () => {                const textElements = document.querySelectorAll('h1, h2, h3, h4, p, span, a');                const fonts = new Map();                textElements.forEach(el => {                    const style = window.getComputedStyle(el);                    const key = `${style.fontFamily}|${style.fontSize}|${style.fontWeight}`;                    if (!fonts.has(key)) {                        fonts.set(key, {                            fontFamily: style.fontFamily,                            fontSize: style.fontSize,                            fontWeight: style.fontWeight,                            lineHeight: style.lineHeight,                        });                    }                });                return Array.from(fonts.values());            }            """        )        # Extract spacing patterns        spacing = await mcp.browser_evaluate(            function="""            () => {                const elements = document.querySelectorAll('[class*="p-"], [class*="m-"], [class*="gap-"]');                const spacings = new Set();                elements.forEach(el => {                    const style = window.getComputedStyle(el);                    spacings.add(style.padding);                    spacings.add(style.margin);                    spacings.add(style.gap);                });                return Array.from(spacings);            }            """        )        return self.normalize_tokens(colors, typography, spacing)

Live Inspection Patterns

Pattern 1: Visual Debugging

Debug layout issues with visual feedback:

class VisualDebugger:    """    Debug UI issues using browser inspection.    """    async def debug_layout(self, url: str, issue_description: str) -> DebugReport:        await mcp.browser_navigate(url=url)        # Take initial screenshot        before = await mcp.browser_take_screenshot(filename="before.png")        # Get page snapshot        snapshot = await mcp.browser_snapshot()        # Inject debug styles via evaluation        await mcp.browser_evaluate(            function="""            () => {                // Add debug overlay to all elements                const style = document.createElement('style');                style.textContent = `                    * { outline: 1px solid rgba(255,0,0,0.2) !important; }                    *:hover { outline: 2px solid red !important; }                `;                document.head.appendChild(style);            }            """        )        # Take debug screenshot        debug_screenshot = await mcp.browser_take_screenshot(            filename="debug-overlay.png"        )        # Analyze the issue        analysis = await self.analyze_layout_issue(            before=before,            debug=debug_screenshot,            snapshot=snapshot,            issue=issue_description        )        return analysis    async def compare_with_design(        self,        live_url: str,        design_image_path: str    ) -> ComparisonReport:        """        Compare live implementation against design mockup.        """        await mcp.browser_navigate(url=live_url)        live_screenshot = await mcp.browser_take_screenshot(            filename="live.png",            fullPage=True        )        # Load and analyze both images        prompt = """        Compare these two images:        1. Design mockup (what it should look like)        2. Live implementation (what it actually looks like)        Identify:        - Color discrepancies (with specific values)        - Spacing differences (estimate pixels)        - Typography mismatches        - Layout structural differences        - Missing or extra elements        Provide specific, actionable fixes.        """        return await self.compare_images(design_image_path, live_screenshot, prompt)

Pattern 2: Responsive Testing

Test and capture across breakpoints:

class ResponsiveTester:    """    Test UI across responsive breakpoints.    """    BREAKPOINTS = {        "mobile": {"width": 375, "height": 812},        "tablet": {"width": 768, "height": 1024},        "desktop": {"width": 1440, "height": 900},        "wide": {"width": 1920, "height": 1080},    }    async def capture_all_breakpoints(self, url: str) -> dict[str, str]:        """        Capture screenshots at all standard breakpoints.        """        await mcp.browser_navigate(url=url)        captures = {}        for name, dimensions in self.BREAKPOINTS.items():            await mcp.browser_resize(**dimensions)            await mcp.browser_wait_for(time=0.5)  # Let layout settle            screenshot = await mcp.browser_take_screenshot(                filename=f"responsive-{name}.png"            )            captures[name] = screenshot        return captures    async def analyze_responsiveness(self, url: str) -> ResponsivenessReport:        """        Analyze how well the UI responds to different sizes.        """        captures = await self.capture_all_breakpoints(url)        prompt = """        Analyze these screenshots at different viewport sizes.        Check for:        1. Layout breaks or overflow        2. Touch target sizes on mobile (min 44x44px)        3. Text readability at each size        4. Navigation accessibility        5. Image scaling issues        6. Hidden content that shouldn't be        Provide specific recommendations for each breakpoint.        """        return await self.analyze_screenshots(captures, prompt)

MCP Tool Patterns

Pattern: Snapshot + Screenshot Combo

Use both tools for complete understanding:

async def comprehensive_capture(url: str) -> tuple[str, str]:    """    Capture both visual and structural representation.    The snapshot gives you:    - Element hierarchy    - Text content    - Interactive elements with refs    - Accessibility tree    The screenshot gives you:    - Visual appearance    - Colors, typography, spacing    - Layout as rendered    """    await mcp.browser_navigate(url=url)    # Snapshot for structure (better for understanding layout)    snapshot = await mcp.browser_snapshot()    # Screenshot for visual analysis    screenshot = await mcp.browser_take_screenshot()    return snapshot, screenshot

Pattern: Interactive Exploration

Navigate and inspect interactively:

async def explore_component(component_name: str):    """    Interactively explore a component's states.    """    # Get snapshot to find component    snapshot = await mcp.browser_snapshot()    # Find the component in snapshot    # Snapshot returns refs like [12] for elements    # Hover to see hover state    await mcp.browser_hover(        element=f"{component_name} component",        ref="[12]"  # From snapshot    )    hover_screenshot = await mcp.browser_take_screenshot(filename="hover.png")    # Click to see active/pressed state    await mcp.browser_click(        element=f"{component_name} component",        ref="[12]"    )    active_screenshot = await mcp.browser_take_screenshot(filename="active.png")    return {        "default": await mcp.browser_take_screenshot(filename="default.png"),        "hover": hover_screenshot,        "active": active_screenshot,    }

Live Preview Workflows

Pattern: Hot Reload Development

Combine code generation with live preview:

class LivePreviewWorkflow:    """    Generate code and preview changes live.    """    async def iterate_with_preview(        self,        component_spec: str,        preview_url: str    ) -> FinalComponent:        iterations = []        for i in range(3):  # Max 3 iterations            # Generate/refine component            code = await self.generate_component(component_spec, iterations)            # Write to file (triggers hot reload)            await self.write_component(code)            # Wait for hot reload            await mcp.browser_wait_for(time=1)            # Capture preview            await mcp.browser_navigate(url=preview_url)            screenshot = await mcp.browser_take_screenshot(                filename=f"iteration-{i}.png"            )            # Analyze against spec            feedback = await self.analyze_preview(screenshot, component_spec)            if feedback.meets_spec:                return code            iterations.append({                "code": code,                "feedback": feedback.issues,            })            # Update spec for next iteration            component_spec = self.refine_spec(component_spec, feedback)        return code  # Return best effort

DevTools Protocol Direct Access

Advanced: CDP for Deep Inspection

Access Chrome DevTools Protocol directly for advanced use:

async def advanced_style_extraction(url: str):    """    Use CDP for detailed style information.    """    # This would require CDP MCP or direct protocol access    cdp_evaluate = """    async function getDetailedStyles(selector) {        const element = document.querySelector(selector);        if (!element) return null;        // Get all applied CSS rules        const rules = [];        for (const sheet of document.styleSheets) {            try {                for (const rule of sheet.cssRules) {                    if (element.matches(rule.selectorText)) {                        rules.push({                            selector: rule.selectorText,                            styles: rule.style.cssText,                            specificity: calculateSpecificity(rule.selectorText),                        });                    }                }            } catch (e) {                // Cross-origin stylesheets            }        }        // Get computed styles        const computed = window.getComputedStyle(element);        // Get layout metrics        const rect = element.getBoundingClientRect();        return {            appliedRules: rules,            computedStyles: Object.fromEntries(                Array.from(computed).map(prop => [prop, computed.getPropertyValue(prop)])            ),            layout: {                x: rect.x,                y: rect.y,                width: rect.width,                height: rect.height,            },        };    }    """    return await mcp.browser_evaluate(function=cdp_evaluate)

Integration Patterns

With Agent Orchestration

class BrowserInspectionAgent:    """    Agent that uses browser MCP for UI analysis.    """    tools = [        "browser_navigate",        "browser_snapshot",        "browser_take_screenshot",        "browser_evaluate",    ]    permissions = ["read_web", "capture_screenshot"]    async def analyze_competitor(self, url: str) -> AnalysisReport:        """        Analyze competitor UI using browser tools.        """        # Navigate        await self.use_tool("browser_navigate", url=url)        # Multi-modal capture        snapshot = await self.use_tool("browser_snapshot")        screenshot = await self.use_tool("browser_take_screenshot")        # Extract tokens        tokens = await self.use_tool("browser_evaluate",            function="() => extractDesignTokens()"        )        return await self.synthesize_analysis(snapshot, screenshot, tokens)

Quick Reference

TaskMCP ToolNotes
Capture full pagebrowser_take_screenshot(fullPage=true)Good for documentation
Get page structurebrowser_snapshot()Better for understanding layout
Capture elementbrowser_take_screenshot(element, ref)Need ref from snapshot
Extract stylesbrowser_evaluate()Run getComputedStyle
Test responsivebrowser_resize() + screenshotLoop through breakpoints
Debug interactivitybrowser_hover(), browser_click()Capture state changes

Best Practices

  1. Snapshot first: Always get a snapshot before screenshots - it provides element refs
  2. Wait for render: Use browser_wait_for(time) after navigation
  3. Combine modalities: Visual + structural analysis yields best results
  4. Iterative capture: Multiple screenshots at different states
  5. Token extraction: Prefer evaluation over visual inference for exact values

Related Skills

This skill works with:

  • agent-orchestration/ui-agent-patterns - Browser agent in multi-agent workflows
  • llm-application-dev/prompt-engineering-ui - Prompts for screenshot analysis
  • context-management/design-system-context - Store extracted tokens

"The browser is not just a renderer - it is an oracle for the living interface."

Todos los archivos

1 archivos
SKILL.md 20.9k
Ver

Instalar browser-devtools-mcp

Descarga y descomprime los archivos de habilidades en tu directorio .claude/skills/.

Descargar ZIP

Clona el repositorio y copia los archivos de la habilidad a tu proyecto.

git clone https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/blob/main/plugins/mcp-integrations/skills/browser-devtools-mcp/SKILL.md # Copy SKILL.md to your .claude/skills/ directory

Copiar Copiar
Configuración rápida: Copia la carpeta de la habilidad en .claude/skills/. Claude la detectará automáticamente y la utilizará.

Habilidades relacionadas

office-mcp
Tiempo actualizado 13 de julio de 2026
mcpgraph
Tiempo actualizado 29 de junio de 2026
composio
Tiempo actualizado 29 de junio de 2026
connect-mcp-server
Tiempo actualizado 29 de junio de 2026
OR