Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion .claude-plugin/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,19 @@
"name": "chrome-devtools-mcp",
"version": "0.21.0",
"description": "Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer",
"userConfig": {
"browserUrl": {
"description": "Optional URL of a running debuggable Chrome instance, for example http://127.0.0.1:9222. Leave blank to launch Chrome automatically.",
"sensitive": false
}
},
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["chrome-devtools-mcp@latest"]
"args": [
"chrome-devtools-mcp@latest",
"--browser-url=${user_config.browserUrl}"
]
}
}
}
16 changes: 16 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -165,6 +165,22 @@ Then, install the plugin:

Restart Claude Code to have the MCP server and skills load (check with `/skills`).

To connect the plugin to a Chrome instance that is already running with remote debugging, set the plugin's `browserUrl` option in your Claude Code settings:

```json
{
"pluginConfigs": {
"chrome-devtools-mcp@claude-plugins-official": {
"options": {
"browserUrl": "http://127.0.0.1:9222"
}
}
}
}
```

Leave `browserUrl` blank to use the default behavior where Chrome DevTools MCP launches Chrome automatically.

> [!TIP]
> If the plugin installation fails with a `Failed to clone repository` error (e.g., HTTPS connectivity issues behind a corporate firewall), see the [troubleshooting guide](./docs/troubleshooting.md#claude-code-plugin-installation-fails-with-failed-to-clone-repository) for workarounds, or use the CLI installation method above instead.

Expand Down