/ Diretório / Playground / dev-browser
● Comunidade SawyerHood ⚡ Instantâneo

dev-browser

por SawyerHood · SawyerHood/dev-browser

A Claude Skill that spins up a devtools-enabled browser your agent can drive — navigate, click, inspect, screenshot.

dev-browser gives your Claude agent a dev-oriented headless browser via skill prompts. It wraps a CDP-based browser with agent-friendly affordances: stable selectors, screenshot-on-every-action, and DOM snapshots ready to chunk. Ideal when you need a browser but don't want to set up playwright end-to-end.

Por que usar

Principais recursos

Demo ao vivo

Como fica na prática

pronto

Instalar

Escolha seu 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
    }
  }
}

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

~/.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 o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a 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
    }
  }
}

Clique no ícone MCP Servers na barra lateral do Cline, depois "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
    }
  }
}

Mesmo formato do Claude Desktop. Reinicie o 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"
      ]
    }
  ]
}

O Continue usa um array de objetos de servidor em vez de um map.

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

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

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

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do 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

Quando usar: You want your Claude Code session to browse something once without committing to a persistent browser server.

Pré-requisitos
  • Skill installed — git clone https://github.com/SawyerHood/dev-browser ~/.claude/skills/dev-browser
  • Chromium availablenpx playwright install chromium fetches the binary
Fluxo
  1. Spin up
    Use dev-browser. Open https://vercel.com/docs/functions. List the sidebar sections.✓ Copiado
    → Headings extracted with anchor URLs
  2. 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
  3. 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.

Armadilhas
  • Chromium binary missing — Run npx playwright install chromium once
Combine com: filesystem

Sanity check a login flow on a staging env

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

Quando usar: Before deploying, you want to click through the critical happy path once.

Fluxo
  1. Open
    Use dev-browser. Open https://staging.myapp.com, take a screenshot.✓ Copiado
    → Landing page screenshot
  2. Sign in
    Click "Sign in", enter [email protected] / Test1234, submit.✓ Copiado
    → Post-login dashboard captured
  3. Confirm
    Is the "Welcome, qa" string visible on the page?✓ Copiado
    → Yes/no + screenshot

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

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

Combinações

Combine com outros MCPs para 10× de alavancagem

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

Ferramentas

O que este MCP expõe

FerramentaEntradasQuando chamarCusto
open_url url Navigate 0
click selector|text Interact 0
type selector, text Enter text 0
snapshot none Ground in current state 0

Custo e limites

O que custa rodar

Cota de API
N/A
Tokens por chamada
DOM snapshots size-gated; screenshots base64
Monetário
Free
Dica
Skip snapshots when not needed — the screenshot alone is often enough

Segurança

Permissões, segredos, alcance

Armazenamento de credenciais: None
Saída de dados: Direct to sites you navigate to

Solução de problemas

Erros comuns e correções

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. outros

AlternativaQuando usarTroca
playwright MCPYou want a persistent, MCP-registered browserMore setup; skill is lighter
mcp-chromeYou need your real logged-in ChromeNot a headless test browser

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills