feat(browser_eval): add executablePath support for custom browser locations#115
Open
pwarnock wants to merge 1 commit intovercel:mainfrom
Open
feat(browser_eval): add executablePath support for custom browser locations#115pwarnock wants to merge 1 commit intovercel:mainfrom
pwarnock wants to merge 1 commit intovercel:mainfrom
Conversation
…ations Adds an `executablePath` parameter to the browser_eval tool's start action, allowing users to specify a custom browser binary location. This is useful for: - Homebrew-installed Playwright browsers at ~/Library/Caches/ms-playwright/ - CI/CD environments with browsers in non-standard locations - Systems without Chrome/Edge installed in default locations The parameter is passed through to playwright-mcp's --executable-path flag. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
executablePathparameter tobrowser_evaltool for specifying custom browser binary locations.Motivation
Users with Homebrew-installed Playwright browsers cannot use browser automation because browsers are installed at non-standard locations (
~/Library/Caches/ms-playwright/). This parameter passes through to playwright-mcp's--executable-pathflag.Use Case
Changes
executablePathtostartBrowserEvalMCP()options interfaceexecutablePathtobrowser_evaltool input schemaTesting
npm run test)npm run build)