dev-browser MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

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

Démo en direct

Aperçu en pratique

prêt

Installer

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

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.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 utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la 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
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "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
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

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

Continue utilise un tableau d'objets serveur plutôt qu'une 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"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : dev-browser

Do quick web research without setting up an MCP

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

Quand l'utiliser : You want your Claude Code session to browse something once without committing to a persistent browser server.

Prérequis

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

Déroulement

Spin up

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

→ Headings extracted with anchor URLs
Drill in

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

→ Three paragraphs with citations to URL fragments
Capture

Screenshot the pricing section for my notes.✓ Copié

→ Screenshot saved locally

Résultat : Research done with a browser when you needed one, without ongoing infrastructure.

Pièges

Chromium binary missing — Run npx playwright install chromium once

Combiner avec : filesystem

Sanity check a login flow on a staging env

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

Quand l'utiliser : Before deploying, you want to click through the critical happy path once.

Déroulement

Open

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

→ Landing page screenshot
Sign in

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

→ Post-login dashboard captured
Confirm

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

→ Yes/no + screenshot

Résultat : A 60-second smoke test before clicking Deploy.

Pièges

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

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

dev-browser-skill + filesystem

Save screenshots alongside notes

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

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.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler
open_url	url	Navigate
click	selector\|text	Interact
type	selector, text	Enter text
snapshot	none	Ground in current state

Coût et limites

Coût d'exécution

Quota d'API: N/A
Tokens par appel: DOM snapshots size-gated; screenshots base64
Monétaire: Free
Astuce: Skip snapshots when not needed — the screenshot alone is often enough

Sécurité

Permissions, secrets, portée

Stockage des identifiants : None

Sortie de données : Direct to sites you navigate to

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

Dépannage

Erreurs courantes et correctifs

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

Alternatives

dev-browser vs autres

Alternative	Quand l'utiliser	Compromis
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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills