[External Plugin]: adding Chrome Devtools plugin

[yulunz]

Plugin name

chrome-devtools-plugin

Short description

Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer.

GitHub repository

ChromeDevTools/chrome-devtools-mcp

Plugin path inside the repository

.github/plugin/plugin.json

Immutable ref to review

chrome-devtools-mcp-v1.0.1

Version

1.0.1

License identifier

Apache-2.0

Author name

Chrome DevTools Team

Author URL

No response

Homepage URL

No response

Keywords

chrome
devtools
mcp
automation
puppeteer
debugging
performance
browser

Additional notes for reviewers

Hello! This follows the newly published process at #1726. We previously tried to land this in #1274. Hope everything looks allright!

Also, we do frequently update the version field in our .github/plugin/plugin.json. Will that be reflected here?

Thanks!

Submission checklist

• The plugin lives in a public GitHub repository.
• The ref I provided is an immutable release tag or full 40-character commit SHA, not a branch.
• This submission follows this repository's contribution, security, and responsible AI policies.
• This plugin is not already listed in the Awesome Copilot marketplace.

[github-actions]

✅ External plugin intake passed

This submission passed automated intake validation and is ready for maintainer review.

• Plugin: chrome-devtools-plugin
• Repository: https://github.com/ChromeDevTools/chrome-devtools-mcp
• Ref: chrome-devtools-mcp-v1.0.1
• Keywords: chrome, devtools, mcp, automation, puppeteer, debugging, performance, browser

Canonical external.json payload

{
  "name": "chrome-devtools-plugin",
  "description": "Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer.",
  "version": "1.0.1",
  "author": {
    "name": "Chrome DevTools Team"
  },
  "repository": "https://github.com/ChromeDevTools/chrome-devtools-mcp",
  "license": "Apache-2.0",
  "keywords": [
    "chrome",
    "devtools",
    "mcp",
    "automation",
    "puppeteer",
    "debugging",
    "performance",
    "browser"
  ],
  "source": {
    "source": "github",
    "repo": "ChromeDevTools/chrome-devtools-mcp",
    "path": ".github/plugin/plugin.json",
    "ref": "chrome-devtools-mcp-v1.0.1"
  }
}

Reviewer notes

Hello! This follows the newly published process at #1726. We previously tried to land this in #1274. Hope everything looks allright!

Also, we do frequently update the version field in our .github/plugin/plugin.json. Will that be reflected here?

Thanks!

[aaronpowell]

/approve

[github-actions]

✅ External plugin approved

A maintainer approved chrome-devtools-plugin, and the submission issue has been closed.

• Catalog action: added
• Source repository: ChromeDevTools/chrome-devtools-mcp
• PR against staged: [external-plugin] Add chrome-devtools-plugin #1755

[mathiasbynens]

Thanks for the swift review and approval!

This remains an open question:

Also, we do frequently update the version field in our .github/plugin/plugin.json. Will that be reflected here?

Any guidance on this?

Update: I suppose this answers it:

if there are changes to the upstream, we'll expect a version bump to the external plugin to be submitted as a PR.

[aaronpowell]

@mathiasbynens yeah, if you version bump upstream, send a PR here (no need for a new issue) with the new ref and version on the external.json and marketplace.json otherwise the marketplace won't know to surface the update to CLI or VS Code

[yulunz]

thanks! Seems the plugin is showing up in the marketplace now 😃

However, I cannot install the plugin. After clicking the install button, the button stays on the UI (it should show "disallow" and "uninstall" if it's successfully installed). Also, the link appears to be "github/awesome-pilot" and we'd expect it to be pointing to ChromeDevTools/chrome-devtools-mcp instead.

See this screenshot: