feat: allow custom WebSocket port to support multiple instances#1
feat: allow custom WebSocket port to support multiple instances#1hasmcp-dev wants to merge 1 commit into
Conversation
Allows running multiple instances of the Browser MCP server by allowing a custom port to be specified via the `-p, --port` CLI option or the `PORT` environment variable. The port is passed down to `createWebSocketServer` to resolve the hardcoded port conflict. Co-authored-by: hasmcp-dev <259770388+hasmcp-dev@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
This PR resolves the hardcoded port conflict issue that prevents running two instances of the Browser MCP server on the same computer. It adds the ability to provide a custom port via the
-p, --portCLI flag orPORTenvironment variable, which overrides the default port and enables multiple instances to run concurrently without terminating each other.PR created automatically by Jules for task 4516839853153926512 started by @hasmcp-dev