Is io.github.Async23/chrome-devtools-mcp safe to use?

io.github.Async23/chrome-devtools-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under Apache-2.0.

How do I install io.github.Async23/chrome-devtools-mcp?

io.github.Async23/chrome-devtools-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.Async23/chrome-devtools-mcp do?

io.github.Async23/chrome-devtools-mcp provides 10 tools: MCP, false, stable, true, webp and 5 more. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.Async23/chrome-devtools-mcp?

io.github.Async23/chrome-devtools-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.

Is io.github.Async23/chrome-devtools-mcp actively maintained?

io.github.Async23/chrome-devtools-mcp is actively maintained — last commit was 6 days ago.

io.github.Async23/chrome-devtools-mcp

@async23/chrome-devtools-mcp

MCP server for Chrome DevTools

10 tools GitHub npm

No known CVEs

Apache-2.0 license

Actively maintained

Last commit 6d ago

Works with most clients

Transport: stdio, sse, http

10 tools · ~316 tok

Grade A · 0.2% of 200K ctx

MCPpedia last refreshed this data 18h ago

Edit this pageView history

io.github.Async23/chrome-devtools-mcp is an MCP server that MCP server for Chrome DevTools. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "chrome-devtools": {
      "args": [
        "-y",
        "@async23/chrome-devtools-mcp@latest",
        "--browser-url=http://127.0.0.1:9222",
        "--no-emulate-focused-pages"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-async23-chrome-devtools-mcp)](https://mcppedia.org/s/io-github-async23-chrome-devtools-mcp)

Read me

What io.github.Async23/chrome-devtools-mcp does

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 acts as a Model-Context-Protocol (MCP) server, giving your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in-depth debugging, and performance analysis. A CLI is also provided for use without MCP.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y '@async23/chrome-devtools-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

87/100across 5 weighted dimensions

How we score →

0255075100

−13

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked @async23/chrome-devtools-mcp against OSV.dev.

Inventory

Tools (10)

Click any tool to inspect its schema.

~316 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.Async23/chrome-devtools-mcp safe to use?: io.github.Async23/chrome-devtools-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under Apache-2.0.
How do I install io.github.Async23/chrome-devtools-mcp?: io.github.Async23/chrome-devtools-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.Async23/chrome-devtools-mcp do?: io.github.Async23/chrome-devtools-mcp provides 10 tools: MCP, false, stable, true, webp and 5 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.Async23/chrome-devtools-mcp?: io.github.Async23/chrome-devtools-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.Async23/chrome-devtools-mcp actively maintained?: io.github.Async23/chrome-devtools-mcp is actively maintained — last commit was 6 days ago.

Similar servers

Others in other

View all →

Transport Stdio95

Transport for TMCP using STDIO

197 14

Flare95

The graph based agentic IDE

123 3

Headroom95

Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.

67.2k 3

app.fojin/fojin-mcp94

Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.

329 8

MCP Security Weekly

Get CVE alerts and security updates for io.github.Async23/chrome-devtools-mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "chrome-devtools": {
      "args": [
        "-y",
        "@async23/chrome-devtools-mcp@latest",
        "--browser-url=http://127.0.0.1:9222",
        "--no-emulate-focused-pages"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-async23-chrome-devtools-mcp)](https://mcppedia.org/s/io-github-async23-chrome-devtools-mcp)

Read me

What io.github.Async23/chrome-devtools-mcp does

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y '@async23/chrome-devtools-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

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 acts as a Model-Context-Protocol (MCP) server, giving your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in-depth debugging, and performance analysis. A CLI is also provided for use without MCP.

This repository publishes the Async23 fork as @async23/chrome-devtools-mcp. It includes the local visible-browser focus control and oversized full-page screenshot fixes while retaining the chrome-devtools-mcp executable name.

Tool reference | 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. Use at your own discretion. We are committed to providing fixes and support for the latest version of Extended Stable Chrome.

Performance tools may send trace URLs to the Google CrUX API to fetch real-user experience data. This helps provide a holistic performance picture by presenting field data alongside lab data. This data is collected by the Chrome User Experience Report (CrUX). To disable this, run with the --no-performance-crux flag.

Usage statistics

Google collects usage statistics (such as tool invocation success rates, latency, and environment information) to improve the reliability and performance of Chrome DevTools MCP.

Data collection is enabled by default. You can opt-out by passing the --no-usage-statistics flag when starting the server:

"args": ["-y", "@async23/chrome-devtools-mcp@latest", "--no-usage-statistics"]

Google handles this data in accordance with the Google Privacy Policy.

Google's collection of usage statistics for Chrome DevTools MCP is independent from the Chrome browser's usage statistics. Opting out of Chrome metrics does not automatically opt you out of this tool, and vice-versa.

Collection is disabled if CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI env variables are set.

Update checks

By default, the server periodically checks the npm registry for updates and logs a notification when a newer version is available. You can disable these update checks by setting the CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS environment variable.

Requirements

Node.js LTS version.
Chrome current stable version or newer.
npm

Getting started

Add the

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

87/100across 5 weighted dimensions

How we score →

0255075100

−13

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked @async23/chrome-devtools-mcp against OSV.dev.

Inventory

Tools (10)

Click any tool to inspect its schema.

~316 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.Async23/chrome-devtools-mcp safe to use?: io.github.Async23/chrome-devtools-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under Apache-2.0.
How do I install io.github.Async23/chrome-devtools-mcp?: io.github.Async23/chrome-devtools-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.Async23/chrome-devtools-mcp do?: io.github.Async23/chrome-devtools-mcp provides 10 tools: MCP, false, stable, true, webp and 5 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.Async23/chrome-devtools-mcp?: io.github.Async23/chrome-devtools-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.Async23/chrome-devtools-mcp actively maintained?: io.github.Async23/chrome-devtools-mcp is actively maintained — last commit was 6 days ago.