RepoPilot

chromedevtools / chrome-devtools-mcp

Search chromedevtools/chrome-devtools-mcp

GitHub

Get started

Taken from the repository's own files on 24 Oct 2026. RepoPilot has not run these commands.

Prerequisites

Commands

No scripts found at the top level of the repository. Check package.json .

Install and use

README.md

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", "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.

Open README.md

Developing

CONTRIBUTING.md

Code reviews

All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult GitHub Help for more information on using pull requests.

Conventional commits

Please follow conventional commits for PR and commit titles.

Feature release checklist

Use chore: for commits containing incomplete features that are not available to users yet. Once the feature is ready to be released, create a PR with a feat: prefix that enables the feature. The following criteria need to be completed:

  • Documentation for the feature is up to date. For example, README.md and tools reference are updated.
  • The feature can be used with Chrome stable or version restrictions are documented otherwise.
  • Corresponding skills are updated or new skills are added if needed.
  • The feature fulfills the use case by its own or in conjunction with existing features (we want to avoid features that offer some tools but cannot be used successfully to debug things).

Release process

Releasing chrome-devtools-mcp is automated by GitHub Actions. To release a new version, search for a PR titled chore(main): release chrome-devtools-mcp and review, test, and land it. The release PR is automatically opened if there are any changes on the main branch that show up in the changelog.

Read the rest of CONTRIBUTING.md