Chrome DevTools MCP

Local · stdio

Google's official Chrome DevTools MCP server gives an agent direct control over a real Chrome browser via CDP (built on Puppeteer): navigation, clicks, forms, screenshots, performance, network and memory. Around 52 tools — the most popular browser MCP (47.6k GitHub stars), replacing the outdated Puppeteer server. Runs via npx; no authentication needed.

Why this server

About 52 tools: from clicks and forms to performance traces and network data
47.6k stars — the most popular browser MCP, replacing the outdated Puppeteer server
A real Chrome via CDP, not headless emulation — sees exactly what a user sees
Launches with one npx command, no API keys or cloud accounts

Usage examples

Prompt: Open my site and tell me why the homepage takes over 5 seconds to load

Result: The agent called navigate_page, then performance_start_trace/performance_stop_trace, and returned the insight pointing to the heaviest resource.

Prompt: Check that the signup form at /signup actually sends a request to the server

Result: The agent filled the form with fill_form, clicked submit via click, and list_network_requests confirmed the successful POST request.

Local server

This MCP runs locally on the user's machine (stdio), so availability isn't tracked — rely on reviews and the rating instead.

Reviews

No reviews yet.