Chrome DevTools MCP Server

Name: Chrome DevTools MCP Server
Availability: InStock
Author: Kata Team

Drive a real Chrome and read its DevTools — traces, network, console, DOM.

Software Development Debugging & Error Resolution @katateam

Before you connect: what this server would do

A preview derived from this server’s definition — not a live run. Nothing runs and no key is sent until you connect. You run this server on your own machine — FindAgent never runs it.

Tools it can use (10)

navigate_page
Navigate the browser to a URL.
take_snapshot
Capture the page accessibility-tree snapshot.
click
Click an element from the snapshot.
fill_form
Fill a form from structured field values.
take_screenshot
Capture a screenshot of the page.
evaluate_script
Evaluate a script in the page context.
list_console_messages
Read the console messages.
list_network_requests
List the network requests the page made.
performance_start_trace
Start a DevTools performance trace.
performance_analyze_insight
Analyze one insight from a recorded trace.

What FindAgent checked

It passed an automated security scan and a human review before it was published here.
Your client talks to this server directly, so FindAgent’s run-time protections — the secret and prompt-injection scan on every result, the credential-to-host binding, the approval gates — do not apply to what you send or receive here.

How FindAgent keeps servers safe

Run locally

This MCP server runs on your own machine — FindAgent only points you at it. Run the command below, then add it to your MCP client. Nothing is hosted or proxied on our side.

terminal

npx -y chrome-devtools-mcp@latest

Add it to your MCP client

Paste this into your client config (e.g. claude_desktop_config.json or a Cursor mcp.json), then restart the client.

mcp client config

{
  "mcpServers": {
    "chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp@latest"
      ]
    }
  }
}

View the source repository