chrome-devtools

zeulewan's avatarfrom zeulewan

Chrome DevTools MCP for browser automation. Five servers configured for parallel agents. Auto-select available server, cleanup when done.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 1, 2026
[Web Automation]

When & Why to Use This Skill

This Chrome DevTools MCP skill empowers Claude agents with robust browser automation capabilities. By configuring five parallel servers, it eliminates race conditions and allows multiple agents to work independently. It provides essential tools for page navigation, screenshot capture, and automated session cleanup, making it a powerful solution for complex web-based tasks, automated testing, and multi-agent workflows.

Use Cases

  • Parallel Agent Workflows: Execute multiple web-based tasks simultaneously by distributing them across five independent browser instances to avoid session conflicts and race conditions.
  • Automated Web Testing and QA: Utilize headless browser capabilities to navigate URLs, capture screenshots, and verify page states for UI/UX audits and functional testing.
  • Dynamic Web Data Extraction: Navigate and interact with modern, JavaScript-heavy web applications to extract data in an isolated and controlled environment.
  • Multi-Page Task Management: Efficiently manage multiple browser tabs and sessions, including automated server selection and manual resource cleanup for long-running research tasks.
namechrome-devtools
descriptionChrome DevTools MCP for browser automation. Five servers configured for parallel agents. Auto-select available server, cleanup when done.

Chrome DevTools MCP

Five MCP servers configured: chrome-devtools, chrome-devtools-2, chrome-devtools-3, chrome-devtools-4, chrome-devtools-5

Quick Start

  1. list_pages - Initialize browser, see open pages
  2. new_page(url) - Open URL (auto-selects new page)
  3. take_screenshot(filePath) - Capture to file
  4. close_page(pageIdx) - Close page by index

Multi-Agent: Auto-Select Available Server

Check availability - Server is available if list_pages returns only about:blank:

Check servers in order until one is available:
1. mcp__chrome-devtools__list_pages
2. mcp__chrome-devtools-2__list_pages
3. mcp__chrome-devtools-3__list_pages
4. mcp__chrome-devtools-4__list_pages
5. mcp__chrome-devtools-5__list_pages

→ Only "about:blank"? Use that server's tools
→ Has other pages? Check next server...
→ All busy? Cleanup one (close_page for index > 0), then use it

Why multiple servers? Parallel Task agents sharing ONE server race-condition on "selected page". Each server = own browser = no conflicts.

Cleanup After Use (No Auto-Timeout)

Chrome-devtools-mcp has NO idle timeout. Manually free servers:

# After completing work:
1. list_pages → note indices
2. close_page(pageIdx=N) for each page except about:blank (index 0)

Troubleshooting

"Browser already running" / stale locks:

rm -f ~/.cache/chrome-devtools-mcp/chrome-profile/Singleton*

Race condition with parallel agents:

  • Don't run parallel agents on SAME server
  • Use chrome-devtools for Agent 1, chrome-devtools-2 for Agent 2

Page not loading:

  • Check URL is valid
  • Try wait_for(text) after navigation

Server Configuration

Both servers use --headless --isolated:

  • --headless = No visible browser window
  • --isolated = Temp profile, auto-cleaned on close

Add more servers if needed:

claude mcp add chrome-devtools-3 --scope user -- npx chrome-devtools-mcp@latest --headless --isolated