Skip to content

Deployment Guide

Learn how to deploy Puppeteer MCP in various environments, from local development to production scale.

Deploy using npm for Node.js applications:

  • Global installation guide
  • Local project integration
  • Publishing to npm registry
  • Version management
  • Package maintenance

Container-based deployment:

  • Official Docker images
  • Custom Dockerfile creation
  • Docker Compose setup
  • Container orchestration
  • Security considerations

Enterprise production deployment:

  • Infrastructure requirements
  • Security hardening
  • SSL/TLS configuration
  • Monitoring setup
  • Backup strategies

Scale Puppeteer MCP for high load:

  • Horizontal scaling patterns
  • Load balancing strategies
  • Session distribution
  • Resource optimization
  • Performance tuning
Terminal window
# Using npx (no installation)
npx puppeteer-mcp
# Or global install
npm install -g puppeteer-mcp
puppeteer-mcp
Terminal window
# Run with Docker
docker run -d \
-p 3000:3000 \
-e PUPPETEER_MCP_AUTH_TOKEN=your-token \
williamzujkowski/puppeteer-mcp:latest
docker-compose.yml
version: '3.8'
services:
puppeteer-mcp:
image: williamzujkowski/puppeteer-mcp:latest
environment:
- PUPPETEER_MCP_AUTH_TOKEN=${AUTH_TOKEN}
- NODE_ENV=production
ports:
- '3000:3000'
deploy:
replicas: 3
resources:
limits:
memory: 2G
  • Generate secure authentication tokens
  • Review resource requirements
  • Plan monitoring strategy
  • Configure backups
  • Test deployment process
  • Enable HTTPS/TLS
  • Configure firewalls
  • Set up rate limiting
  • Review authentication
  • Enable audit logging
  • Configure resource limits
  • Set up load balancing
  • Enable caching
  • Configure CDN (if applicable)
  • Optimize browser pool
  • Set up health checks
  • Configure logging
  • Enable metrics collection
  • Set up alerts
  • Plan incident response
  • CPU: 2 cores
  • RAM: 4GB
  • Disk: 10GB
  • Network: 100Mbps
  • CPU: 4+ cores
  • RAM: 8GB+
  • Disk: 50GB SSD
  • Network: 1Gbps
  • Node.js: 20.0.0+
  • Chrome/Chromium: Latest
  • Docker: 20.10+ (if using containers)

Best for development and small teams:

[Client] → [Puppeteer MCP Server] → [Chrome]

For medium traffic with redundancy:

[Clients] → [Load Balancer] → [MCP Servers] → [Chrome Pool]

For large scale deployments:

[API Gateway] → [MCP Services] → [Session Manager] → [Chrome Cluster]

Deploy for internal team use:

  • Single Docker container
  • Basic authentication
  • Shared browser pool
  • Internal network only

Deploy as part of a SaaS platform:

  • Kubernetes deployment
  • Multi-tenant isolation
  • API rate limiting
  • Usage monitoring

Deploy for enterprise use:

  • High availability setup
  • Security compliance
  • Audit logging
  • Disaster recovery
Terminal window
# Check service health
curl http://localhost:8443/health
# Check detailed status
curl -H "Authorization: Bearer $TOKEN" \
http://localhost:8443/api/status
Terminal window
# Load test with k6
k6 run load-test.js
# Monitor resource usage
docker stats puppeteer-mcp
  • Check logs for errors
  • Verify network connectivity
  • Ensure Chrome dependencies
  • Review resource limits
  • Test authentication
  1. Use Environment Variables for configuration
  2. Enable Monitoring from day one
  3. Plan for Scaling even if starting small
  4. Automate Deployments with CI/CD
  5. Regular Backups of configuration
  6. Security First approach
  7. Document Everything for your team

Choose your deployment method: