dev-browser MCP — Casos de uso, Instalar & Demo en vivo

Por qué usarlo

Características clave

CDP browser as a skill — no separate MCP setup
Screenshots between steps for visual grounding
DOM snapshots tuned for LLM consumption (size-aware)
Works with Chromium; local or containerized
MIT licensed

Demo en vivo

Cómo se ve en la práctica

listo

Instalar

Elige tu cliente

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "dev-browser-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SawyerHood/dev-browser",
        "~/.claude/skills/dev-browser"
      ],
      "_inferred": true
    }
  }
}

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "dev-browser-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SawyerHood/dev-browser",
        "~/.claude/skills/dev-browser"
      ],
      "_inferred": true
    }
  }
}

Cursor usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "dev-browser-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SawyerHood/dev-browser",
        "~/.claude/skills/dev-browser"
      ],
      "_inferred": true
    }
  }
}

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "dev-browser-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SawyerHood/dev-browser",
        "~/.claude/skills/dev-browser"
      ],
      "_inferred": true
    }
  }
}

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "dev-browser-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SawyerHood/dev-browser",
        "~/.claude/skills/dev-browser"
      ]
    }
  ]
}

Continue usa un array de objetos de servidor en lugar de un mapa.

~/.config/zed/settings.json

{
  "context_servers": {
    "dev-browser-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/SawyerHood/dev-browser",
          "~/.claude/skills/dev-browser"
        ]
      }
    }
  }
}

Añádelo a context_servers. Zed recarga en caliente al guardar.

claude mcp add dev-browser-skill -- git clone https://github.com/SawyerHood/dev-browser ~/.claude/skills/dev-browser

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: dev-browser

Do quick web research without setting up an MCP

👤 Devs who don't want Playwright in their MCP config ⏱ ~15 min beginner

Cuándo usarlo: You want your Claude Code session to browse something once without committing to a persistent browser server.

Requisitos previos

Skill installed — git clone https://github.com/SawyerHood/dev-browser ~/.claude/skills/dev-browser
Chromium available — npx playwright install chromium fetches the binary

Flujo

Spin up

Use dev-browser. Open https://vercel.com/docs/functions. List the sidebar sections.✓ Copiado

→ Headings extracted with anchor URLs
Drill in

Navigate to "Runtime" — read the page and summarize the three runtime options in one paragraph each.✓ Copiado

→ Three paragraphs with citations to URL fragments
Capture

Screenshot the pricing section for my notes.✓ Copiado

→ Screenshot saved locally

Resultado: Research done with a browser when you needed one, without ongoing infrastructure.

Errores comunes

Chromium binary missing — Run npx playwright install chromium once

Combinar con: filesystem

Sanity check a login flow on a staging env

👤 QA-minded devs pre-deploy ⏱ ~5 min beginner

Cuándo usarlo: Before deploying, you want to click through the critical happy path once.

Flujo

Open

Use dev-browser. Open https://staging.myapp.com, take a screenshot.✓ Copiado

→ Landing page screenshot
Sign in

Click "Sign in", enter [email protected] / Test1234, submit.✓ Copiado

→ Post-login dashboard captured
Confirm

Is the "Welcome, qa" string visible on the page?✓ Copiado

→ Yes/no + screenshot

Resultado: A 60-second smoke test before clicking Deploy.

Errores comunes

CAPTCHA on login — Add a test-only bypass in staging; dev-browser is not a captcha breaker

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

dev-browser-skill + filesystem

Save screenshots alongside notes

After every step, screenshot into /notes/web-research/.✓ Copiado

dev-browser-skill + chrome-devtools

When you need devtools-level depth, escalate to chrome-devtools MCP

dev-browser gave me the page — now use chrome-devtools to check the network waterfall.✓ Copiado

Herramientas

Lo que expone este MCP

Herramienta	Entradas	Cuándo llamar
open_url	url	Navigate
click	selector\|text	Interact
type	selector, text	Enter text
snapshot	none	Ground in current state

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API: N/A
Tokens por llamada: DOM snapshots size-gated; screenshots base64
Monetario: Free
Consejo: Skip snapshots when not needed — the screenshot alone is often enough

Seguridad

Permisos, secretos, alcance

Almacenamiento de credenciales: None

Salida de datos: Direct to sites you navigate to

Don't enter real credentials on sites in agent-driven sessions — use test accounts

Resolución de problemas

Errores comunes y soluciones

Error: Executable doesn't exist at chromium path

npx playwright install chromium — the skill assumes Playwright's binaries

Selector not found

Run snapshot first; pick selector from real DOM, not guessed

Page blocks automation

Site detected headless — try running with headless=false in skill config

Alternativas

dev-browser vs otros

Alternativa	Cuándo usarla	Contrapartida
playwright MCP	You want a persistent, MCP-registered browser	More setup; skill is lighter
mcp-chrome	You need your real logged-in Chrome	Not a headless test browser

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills