dev-browser MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

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

Live-Demo

In der Praxis

bereit

Installieren

Wählen Sie Ihren Client

~/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
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.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 nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

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

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "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
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

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

Continue nutzt ein Array von Serverobjekten statt einer 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"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: dev-browser

Do quick web research without setting up an MCP

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

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

Voraussetzungen

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

Ablauf

Spin up

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

→ Headings extracted with anchor URLs
Drill in

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

→ Three paragraphs with citations to URL fragments
Capture

Screenshot the pricing section for my notes.✓ Kopiert

→ Screenshot saved locally

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

Fallstricke

Chromium binary missing — Run npx playwright install chromium once

Kombinieren mit: filesystem

Sanity check a login flow on a staging env

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

Wann einsetzen: Before deploying, you want to click through the critical happy path once.

Ablauf

Open

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

→ Landing page screenshot
Sign in

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

→ Post-login dashboard captured
Confirm

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

→ Yes/no + screenshot

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

Fallstricke

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

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

dev-browser-skill + filesystem

Save screenshots alongside notes

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

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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen
open_url	url	Navigate
click	selector\|text	Interact
type	selector, text	Enter text
snapshot	none	Ground in current state

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: N/A
Tokens pro Aufruf: DOM snapshots size-gated; screenshots base64
Kosten in €: Free
Tipp: Skip snapshots when not needed — the screenshot alone is often enough

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: None

Datenabfluss: Direct to sites you navigate to

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

Fehlerbehebung

Häufige Fehler und Lösungen

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

Alternativen

dev-browser vs. andere

Alternative	Wann stattdessen	Kompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen