Chrome DevTools MCP

● Active

io.github.secforge/chrome-devtools-mcp

MCP server for Chrome DevTools

Connect this server

One click to install, or copy the config below. Suits: Claude Desktop · Cursor.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@secforge/chrome-devtools-mcp@1.10.1004"
      ]
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add chrome-devtools-mcp -- npx -y @secforge/chrome-devtools-mcp@1.10.1004
OpenAI Codex CLI
codex mcp add chrome-devtools-mcp -- npx -y @secforge/chrome-devtools-mcp@1.10.1004
VS Code
code --add-mcp '{"name":"chrome-devtools-mcp","type":"stdio","command":"npx","args":["-y","@secforge/chrome-devtools-mcp@1.10.1004"]}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Search & Web
Version
1.10.1004
Registry
active
Published
10/10/2026

On GitHub

read Nov 17, 2026
Stars
58k
Forks
4.9k
Last push
Nov 17, 2026
License
Apache-2.0

TypeScriptbrowserchromechrome-devtoolsdebuggingdevtoolsmcpmcp-serverpuppeteer

From the README

Chrome DevTools for agents Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser. It is available as a Model-Context-Protocol (MCP) server and as a CLI. Both give your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in-depth debugging, and performance analysis. Tool reference | CLI | Skills | Changelog | Contributing | Troubleshooting | Design Principles Key features • Get performance insights: Uses Chrome DevTools to record traces and extract actionable performance insights. • Advanced browser debugging: Analyze network requests, take screenshots and check browser console messages (with source-mapped stack traces). • Reliable automation. Uses puppeteer to automate actions in Chrome and automatically wait for action results. Disclaimers chrome-devtools-mcp exposes content of the browser instance to the MCP clients allowing them to inspect, debug, and modify any data in the browser or DevTools. Avoid sharing sensitive or personal information that you don't want to share with MCP clients. chrome-devtools-mcp officially supports Google Chrome and Chrome for Testing only. Other Chromium-based browsers may work, but this is not guaranteed, and you may encounter unexpected behavior.…

Read the full README on GitHub →

Alternatives to Chrome DevTools MCP

Best Search & Web servers →

The most-starred Search & Web servers in the index, with their live-check result.

ServerStarsLast pushLive check
Browser Use120,955Nov 2026Working
Scrapling MCP Server102,926Nov 2026Local / not checked
Chrome DevTools MCP58,014Nov 2026Local / not checked
com.puter MCP Server44,182Nov 2026Needs sign-in
Playwright MCP39,799Nov 2026Local / not checked

Chrome DevTools MCP: questions people ask

Is Chrome DevTools MCP a remote or a local MCP server?
According to its entry in the official MCP registry, Chrome DevTools MCP ships as a local package (npm) that your client starts on your machine.
Is Chrome DevTools MCP still maintained?
Active: the repository's last commit today. Last push Nov 17, 2026, 58,028 GitHub stars, Apache-2.0 licence. Read from GitHub on Nov 17, 2026.
How do I add Chrome DevTools MCP to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Search & Web →

Add the badge to your site

Show visitors that Chrome DevTools MCP is listed here — it’s also the link we check for a free listing.

Chrome DevTools MCP — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-secforge-chrome-devtools-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Chrome DevTools MCP — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Chrome DevTools MCP — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-secforge-chrome-devtools-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.