chromedevtools/chrome-devtools-mcp

inspect-in-devtools

Use this skill to connect to the Chrome DevTools UI for interactive debugging, UI/UX review, Q&A, showing elements/network requests/panels to the user, inspecting the user's current DevTools selection, and addressing or polling for DevTools UI comment threads.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/chromedevtools/chrome-devtools-mcp --skill inspect-in-devtools

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Debug, Review, and Q&A in DevTools

Use this skill to:

  1. Show a target to the user: Open DevTools and reveal a panel, a DOM element, or a network request.
  2. Inspect the user's selection: Read the element or network request that the user selected in DevTools.
  3. Address DevTools comments: Fetch comment threads, answer questions or apply fixes, and resolve the threads.

Prerequisites

  • Chrome version: Chrome M159 or later.
  • Required flag: --devtools-comments in the MCP server config. Without it, open_devtools, reveal_in_devtools, get_devtools_comments, and resolve_devtools_comment are not available.
  • Headed browser: Chrome must not run in --headless mode.
  • Page targeting: All tools require a pageId from list_pages or new_page.

Workflows

1. Open DevTools

Call open_devtools with pageId. Do this before you call reveal_in_devtools, get_devtools_comments, or resolve_devtools_comment.

2. Reveal a panel, element, or network request

Call reveal_in_devtools with pageId and these optional parameters:

  • panelName: "elements", "network", "sources", or "console". Pass it alone to switch panels.
  • uid: Element uid from take_snapshot. Reveals the element in the Elements panel.
  • reqid: Request reqid from list_network_requests. Reveals the request in the Network panel.

uid and reqid are mutually exclusive.

3. Inspect the user's selection

  • DOM element: Call take_snapshot. The snapshot marks the element selected in the Elements panel. Pass its uid to get_css_styles, take_screenshot, or evaluate_script.
  • Network request: Call get_network_request and omit reqid. It returns the request selected in the Network panel.

4. Handle comment threads

Select the mode from the user's request.

Mode A: One-shot (comments already exist)

Use this mode when the user says the comments are already in DevTools, or asks you not to poll.

  1. Call get_devtools_comments once.
  2. Process and resolve each returned thread.
  3. Summarize your changes and answers in chat, then end your turn. Do not poll.

Mode B: Watch (wait for user feedback)

Use this mode when the user asks you to wait while they debug, review, or add comments.

  1. Call get_devtools_comments immediately.
  2. While the result is "No open DevTools comments found.", wait 10 seconds, then call it again. Call it immediately if a "DevTools comment threads updated" notification arrives.
  3. Stop after 12 consecutive empty polls (about 2 minutes) or when the user asks you to stop.
  4. When threads appear, process and resolve them. Then reset the empty-poll counter and continue polling.

Rules for polling:

  • Use a background sub-agent when sub-agent tools are available, so the main thread stays responsive. The sub-agent returns the threads to the main agent, or resolves them itself if it has workspace and MCP tools.
  • Poll inline only when sub-agent tools are unavailable. Do not end your turn early.
  • Never call `get_devtools_comments` back-to-back without the 10-second delay.

Process and resolve a thread

For each ### Thread: <id>:

  1. Inspect the anchored target:
  • Related element uid: Use get_css_styles, take_snapshot, or take_screenshot with the uid.
  • Related network reqid: Use get_network_request with the reqid.
  • Optionally call reveal_in_devtools to show the target to the user.
  1. Address the comment:
  • For a code or styling request, apply the fix in the workspace. Reload and verify the page if needed.
  • For a question or root-cause investigation, collect diagnostic data. Do not make unnecessary code edits.
  1. Resolve: Call resolve_devtools_comment with pageId, threadId, and replyText:
  • For a question or root cause, write a detailed answer.
  • For a straightforward fix, write 1–2 sentences that state the change and the file.
같은 저장소의 Skills

더 많은 Skills

모든 Skills
chromedevtools
커뮤니티

chrome-devtools-cli

Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.

1시간 설치 수
2
GitHub Stars
5.9만
업데이트
11월 20일
chromedevtools
커뮤니티

chrome-devtools

Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).

1시간 설치 수
2
GitHub Stars
5.8만
업데이트
11월 18일
chromedevtools
커뮤니티

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions "largest contentful paint", "page load speed", "CWV", or wants to improve how fast their hero image or main content renders.

1시간 설치 수
2
GitHub Stars
5.7만
업데이트
11월 15일
chromedevtools
커뮤니티

memory-leak-debugging

Diagnoses and resolves memory leaks in JavaScript/Node.js applications. Use when a user reports high memory usage, OOM errors, or wants to capture, compare, or inspect heap snapshots with Chrome DevTools MCP memory tools.

1시간 설치 수
2
GitHub Stars
5.7만
업데이트
11월 15일