feat: mcp browser #94
Open
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.
This pull request introduces Docker support for the
browser-mcppackage, providing Dockerfiles for both standard and HTTP server variants, along with a.dockerignorefile to optimize build context. The Dockerfiles are designed to run the MCP browser server in a secure, production-ready environment with all necessary dependencies, including Chrome and Puppeteer.Docker support and configuration:
.dockerignorefile to excludenode_modules, build artifacts, and system files from Docker build context, reducing image size and build time.New Dockerfiles for deployment:
Dockerfileto build a production-ready image forbrowser-mcpusing Node.js 22, installing Chrome, necessary fonts, Puppeteer, and the MCP server, and running as a non-root user for security.Dockerfile.httpfor an HTTP server variant, exposing port 8088 and configuring the entrypoint to run the MCP browser server on that port.