Skip to content

feat: add Claude plugin executablePath user config #1981

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
maruen wants to merge 1 commit into
base: main
Choose a base branch
from
+24 −1
Open

feat: add Claude plugin executablePath user config #1981

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 8 additions & 1 deletion .claude-plugin/plugin.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,11 +2,18 @@
"name": "chrome-devtools-mcp",
"version": "0.23.0",
"description": "Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer",
"userConfig": {
"executablePath": {
"description": "Optional path to a custom Chrome executable. Useful when the system has multiple Chrome installations (e.g. point at the Chrome for Testing binary so the MCP-launched Chrome stays separate from the user's regular Chrome and can be scripted unambiguously by AppleScript / OS automation tools). Leave blank to use the auto-detected stable Chrome.",
"sensitive": false
}
},
Comment on lines +5 to +10
Copy link
Copy Markdown
Collaborator

@OrKoN OrKoN Apr 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we update it as part of npm run gen? so that it does not need to be manually maintained? perhaps a new script to update plugin configurations would be great.

cc @natorion

"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"chrome-devtools-mcp@latest"
"chrome-devtools-mcp@latest",
"--executablePath=${user_config.executablePath}"
]
}
}
Expand Down
16 changes: 16 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,6 +166,22 @@ Then, install the plugin:

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

To point the plugin at a custom Chrome binary (e.g. [Chrome for Testing](https://developer.chrome.com/blog/chrome-for-testing/) so the MCP-launched Chrome has a separate bundle ID from the user's regular Chrome and can be scripted unambiguously by macOS AppleScript), set the plugin's `executablePath` option in your Claude Code settings:

```json
{
"pluginConfigs": {
"chrome-devtools-mcp@claude-plugins-official": {
"options": {
"executablePath": "/Applications/Google Chrome for Testing.app/Contents/MacOS/Google Chrome for Testing"
}
}
}
}
```

Leave `executablePath` blank to use the default behavior where Chrome DevTools MCP auto-detects stable Chrome.

> [!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