dev-browser MCP — 使用場景, 安裝 & 即時演示

為什麼要用

核心特性

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

即時演示

實際使用效果

就緒

安裝

選擇你的客戶端

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

開啟 Claude Desktop → Settings → Developer → Edit Config。儲存後重啟應用。

~/.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 使用與 Claude Desktop 相同的 mcpServers 格式。專案級設定優先於全域。

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

點擊 Cline 側欄中的 MCP Servers 圖示，然後選 "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
    }
  }
}

格式與 Claude Desktop 相同。重啟 Windsurf 生效。

~/.continue/config.json

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

Continue 使用伺服器物件陣列，而非映射。

~/.config/zed/settings.json

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

加入 context_servers。Zed 儲存後熱重載。

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

一行命令搞定。用 claude mcp list 驗證，claude mcp remove 移除。

使用場景

實戰用法： dev-browser

Do quick web research without setting up an MCP

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

何時使用： You want your Claude Code session to browse something once without committing to a persistent browser server.

前置條件

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

步驟

Spin up

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

→ Headings extracted with anchor URLs
Drill in

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

→ Three paragraphs with citations to URL fragments
Capture

Screenshot the pricing section for my notes.✓ 已複製

→ Screenshot saved locally

結果： Research done with a browser when you needed one, without ongoing infrastructure.

注意事項

Chromium binary missing — Run npx playwright install chromium once

搭配使用： filesystem

Sanity check a login flow on a staging env

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

何時使用： Before deploying, you want to click through the critical happy path once.

步驟

Open

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

→ Landing page screenshot
Sign in

Click "Sign in", enter [email protected] / Test1234, submit.✓ 已複製

→ Post-login dashboard captured
Confirm

Is the "Welcome, qa" string visible on the page?✓ 已複製

→ Yes/no + screenshot

結果： A 60-second smoke test before clicking Deploy.

注意事項

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

組合

與其他 MCP 搭配，撬動十倍槓桿

dev-browser-skill + filesystem

Save screenshots alongside notes

After every step, screenshot into /notes/web-research/.✓ 已複製

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.✓ 已複製

工具

此 MCP 暴露的能力

工具	輸入參數	何時呼叫
open_url	url	Navigate
click	selector\|text	Interact
type	selector, text	Enter text
snapshot	none	Ground in current state

成本與限制

運行它的成本

API 配額: N/A
每次呼叫 Token 數: DOM snapshots size-gated; screenshots base64
費用: Free
提示: Skip snapshots when not needed — the screenshot alone is often enough

安全

權限、密鑰、影響範圍

憑證儲存： None

資料出站： Direct to sites you navigate to

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

故障排查

常見錯誤與修復

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

替代方案

dev-browser 對比其他方案

替代方案	何時用它替代	權衡
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

dev-browser

為什麼要用

核心特性

即時演示

實際使用效果

安裝

選擇你的客戶端

使用場景

實戰用法： dev-browser

Do quick web research without setting up an MCP

前置條件

步驟

注意事項

組合

與其他 MCP 搭配，撬動十倍槓桿

工具

此 MCP 暴露的能力

成本與限制

運行它的成本

安全

權限、密鑰、影響範圍

故障排查

常見錯誤與修復

替代方案

dev-browser 對比其他方案

更多

資源