chore: update playwright docker args #363
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
There was a problem hiding this comment.
Pull request overview
This PR updates the Docker arguments configuration for the Microsoft Playwright MCP server by expanding the single-line args array into a multi-line format and adding several server configuration arguments: --host 0.0.0.0, --port 8080, --allowed-hosts *, and --isolated.
Changes:
- Reformatted the Docker
argsarray from inline to multi-line format for better readability - Added network configuration arguments (
--host,--port,--allowed-hosts) - Added the
--isolatedflag to run in memory-only browser profile mode
| "--allowed-hosts", | ||
| "*", |
There was a problem hiding this comment.
The argument --allowed-hosts is not a valid option for the Playwright MCP server. According to the server's documentation in the readme field, the correct argument is --allowed-origins, which specifies a semicolon-separated list of origins to allow the browser to request. This argument should be either removed or changed to --allowed-origins with an appropriate value (e.g., semicolon-separated origins instead of "*").
| "--allowed-hosts", | |
| "*", | |
| "--allowed-origins", | |
| "http://localhost;https://localhost", |
| "--init", | ||
| "mcr.microsoft.com/playwright/mcp", | ||
| "--host", | ||
| "0.0.0.0", |
There was a problem hiding this comment.
Setting --host to 0.0.0.0 binds the server to all network interfaces, exposing it to external network access. This could be a security risk if the Playwright MCP server is not properly protected by network-level controls. Consider whether external access is necessary for this use case, or if binding to localhost (the default) would be more appropriate.
| "0.0.0.0", | |
| "127.0.0.1", |
| "--port", | ||
| "8080", |
There was a problem hiding this comment.
The --port 8080 argument configures the Playwright MCP server to listen on port 8080 for HTTP/SSE transport. However, the Docker configuration does not include port mapping (e.g., -p 8080:8080) to expose this port from the container to the host. Without port mapping, the server will be inaccessible from outside the container, making these network-related arguments ineffective.
1 participant
No description provided.