# chrome-devtools-mcp mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für chrome-devtools-mcp in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:chrome-devtools-mcp
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install chrome-devtools-mcp
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:chrome-devtools-mcp
- **Paketmanager:** Homebrew
- **Version:** 1.6.0
- **Quellzusammenfassung:** Chrome DevTools for coding agents
- **Homepage:** <https://github.com/chromedevtools/chrome-devtools-mcp>
- **Zuletzt aktualisiert:** 2026-07-15T16:19:31Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- chrome-devtools (Alias)
- chrome-devtools-mcp (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 1.6.0
## Projektgeschichte und Nutzung

Chrome DevTools MCP is Google's official Model Context Protocol server for letting coding agents inspect and control a live Chrome browser through Chrome DevTools capabilities.

### Projektgeschichte

The public GitHub repository was created in September 2025 under the ChromeDevTools organization. Its README describes an MCP server plus a standalone CLI that expose browser automation, debugging, screenshots, console and network inspection, and performance tracing to AI coding assistants.

The project reached a 1.0.0 release in May 2026 and continued shipping frequent releases through June 2026, reflecting the fast-moving adoption of MCP tooling around coding agents.

### Adoptionsgeschichte

The README centers adoption on MCP client configuration, including npx-based setup for agent tools and a Homebrew formula in the supplied package facts. It explicitly recommends using the latest npm package so clients track current Chrome DevTools MCP behavior.

### Wie es verwendet wird

Users run the MCP server with npx or the packaged executables and add it to an MCP client configuration. It officially supports Google Chrome and Chrome for Testing, with options for slim mode, headless operation, disabling usage statistics, and disabling update checks.

### Warum Paket-Nerds sich dafür interessieren

For package-manager users, chrome-devtools-mcp is a snapshot of the 2025-2026 shift from browser automation as a test-only concern to browser introspection as a standard coding-agent dependency. It packages DevTools, Puppeteer-backed automation, and MCP conventions into a single installable developer tool.

### Zeitleiste

- 2025: GitHub repository created under ChromeDevTools.
- 2025: v0.1.0 tag published in September.
- 2026: v1.0.0 released in May.
- 2026: v1.4.0 released in June.

### Related projects

- Related projects include Chrome DevTools, Chrome for Testing, Puppeteer, the Model Context Protocol, and MCP clients such as Claude Code, Cursor, Copilot, Antigravity, and Amp as documented in the README.

### Quellen

- <https://github.com/ChromeDevTools/chrome-devtools-mcp#readme>
- <https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/tool-reference.md>
- <https://api.github.com/repos/ChromeDevTools/chrome-devtools-mcp>
- <https://api.github.com/repos/ChromeDevTools/chrome-devtools-mcp/releases>


## Sicherheitshinweise

Für chrome-devtools-mcp wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.



## Combined YAML source

View the package source record on GitHub. [combined/chrome-devtools-mcp.yml](https://github.com/mxcl/pkgdb/blob/main/combined/chrome-devtools-mcp.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph