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와 조합해 10배 효율

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
호출당 토큰: 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