BrowserLoop

BrowserLoop

mattiasw

Captures web page screenshots using Playwright with support for different formats, element targeting, and authentication. Also monitors browser console logs for debugging and testing workflows.

Captures web page screenshots using Playwright with support for full-page, element-specific, and viewport screenshots in PNG, JPEG, and WebP formats, featuring cookie authentication, domain filtering, and configurable quality settings for web testing and visual verification workflows.

22475 views2Local (stdio)

What it does

  • Take full-page screenshots
  • Capture specific element screenshots
  • Monitor browser console logs
  • Export in PNG, JPEG, and WebP formats
  • Authenticate with cookies
  • Configure image quality settings

Best for

Web developers testing visual changesQA engineers doing visual verificationDebugging browser console errorsAutomated screenshot workflows
Multiple image formats supportedDocker containerizedProject is archived

About BrowserLoop

BrowserLoop is a community-built MCP server published by mattiasw that provides AI assistants with tools and capabilities via the Model Context Protocol. BrowserLoop: Capture web screenshots on Chrome with advanced screenshot taker add-on for web testing, visual verificatio It is categorized under browser automation.

How to install

You can install BrowserLoop in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

License

BrowserLoop is released under the AGPL-3.0 license.

BrowserLoop

CI/CD Pipeline npm version npm downloads

⚠️ ARCHIVED: This project is archived and will not receive any further updates. With the release of Chrome DevTools MCP, a dedicated MCP server for browser automation is no longer necessary as that project provides more comprehensive browser interaction capabilities including screenshots, console monitoring, and much more.

A Model Context Protocol (MCP) server for taking screenshots and reading console logs from web pages using Playwright. This tool allows AI agents to automatically capture screenshots and monitor browser console output for debugging, testing, and development tasks.

NOTE: Almost all of the code in this repository has been auto-generated. That means you should probably not trust it too much. That being said, it does work and I'm using it myself.

NOTE: If the documentation is incorrect, please let me know or send a PR. If you too want to use a code generation tool to update the code for this project, PROJECT_CONTEXT.md has been used as context to give a good overview of the various parts of the project. It might be a bit messy now but it's a good starting point and you're welcome to update it.

Features

  • 📸 High-quality screenshot capture using Playwright
  • 📝 Console log monitoring and collection from web pages
  • 🌐 Support for localhost and remote URLs
  • 🍪 Cookie-based authentication for protected pages
  • 🐳 Docker containerization for consistent environments
  • ⚡ PNG, JPEG, and WebP format support with configurable quality
  • 🛡️ Secure non-root container execution
  • 🤖 Full MCP protocol integration with AI development tools
  • 🔧 Configurable viewport sizes and capture options
  • 📱 Full page and element-specific screenshot capture
  • ⚠️ Browser warning and error capture (Permissions-Policy, security warnings)
  • ⚡ TypeScript with Biome for fast development
  • 🧪 Comprehensive testing with Node.js built-in test runner

Quick Start

📦 NPX Usage (Recommended)

The easiest way to get started - no installation required!

# Install Chromium browser (one-time setup)
npx playwright install chromium

# Test that BrowserLoop works
npx browserloop@latest --version

That's it! The latest version of BrowserLoop will be downloaded and executed automatically. Perfect for MCP users who want zero-maintenance screenshots.

MCP Configuration

Add BrowserLoop to your MCP configuration file (e.g. ~/.cursor/mcp.json):

{
  "mcpServers": {
    "browserloop": {
      "command": "npx",
      "args": ["-y", "browserloop@latest"],
      "description": "Screenshot and console log capture server for web pages using Playwright"
    }
  }
}

💡 Using @latest ensures you always get the newest features and bug fixes automatically.

🚀 One-Click Install for Cursor

Add BrowserLoop to Cursor with a single click using this deeplink:

🔗 Add BrowserLoop to Cursor

This deeplink will automatically configure BrowserLoop in your Cursor MCP settings with the optimal configuration using npx and the latest version.

Prerequisites: Make sure you have Chromium installed first:

npx playwright install chromium

Browser Installation Requirements

🚨 Critical: BrowserLoop requires Chromium to be installed via Playwright before it can take screenshots.

First-Time Setup (All Users)

Install Chromium browser:

npx playwright install chromium

Verify installation:

# Check Playwright installation
npx playwright --version

# Test BrowserLoop (if using NPX)
npx browserloop@latest --version

🐳 Docker Alternative

For containerized environments:

# Pull and run with Docker
docker run --rm --network host browserloop

# Or use docker-compose for development
git clone <repository-url>
cd browserloop
docker-compose -f docker/docker-compose.yml up

💻 Development Installation

For contributors or advanced users who want to build from source:

# Clone the repository
git clone <repository-url>
cd browserloop

# Install dependencies
npm install

# Install Playwright browsers (required for screenshots)
npx playwright install chromium
# OR use the convenient script:
npm run install-browsers

# Build the project
npm run build

MCP Configuration for Development

{
  "mcpServers": {
    "browserloop": {
      "command": "node",
      "args": [
        "/absolute/path/to/browserloop/dist/src/index.js"
      ],
      "description": "Screenshot and console log capture server for web pages using Playwright"
    }
  }
}

Replace /absolute/path/to/browserloop/ with your actual project path.

Basic Usage

Once configured, you can use natural language commands in your AI tool:

Screenshots

Take a screenshot of https://example.com
Take a screenshot of https://example.com with width 1920 and height 1080
Take a screenshot of https://example.com in JPEG format with 95% quality
Take a full page screenshot of https://example.com
Take a screenshot of http://localhost:3000 to verify the UI changes

Console Log Reading

Read console logs from https://example.com
Check for console errors on https://example.com
Monitor console warnings from http://localhost:3000
Read only error and warning logs from https://example.com
Capture console output from https://example.com for debugging

🔐 Cookie Authentication

BrowserLoop supports cookie-based authentication for capturing screenshots of login-protected pages during development:

Take a screenshot of http://localhost:3000/admin/dashboard using these cookies: [{"name":"connect.sid","value":"s:session-id.signature","domain":"localhost"}]

📖 For cookie extraction methods and development workflows, see:

📖 Cookie Authentication Guide

Common development use cases:

  • Local development servers with authentication
  • Staging environment testing
  • API documentation tools (Swagger, GraphQL Playground)
  • Custom web applications during development
  • Admin panels and protected routes

Documentation

Key API Parameters

ParameterTypeDescriptionDefault
urlstringTarget URL to capture (required)-
widthnumberViewport width (200-4000)1280
heightnumberViewport height (200-4000)720
formatstringImage format (webp, png, jpeg)webp
qualitynumberImage quality (1-100)80
fullPagebooleanCapture full pagefalse
selectorstringCSS selector for element capture-

📖 See docs/API.md for complete parameter details, usage examples, and configuration options.

Configuration

BrowserLoop can be configured using environment variables:

Basic Configuration

VariableDefaultDescription
BROWSERLOOP_DEFAULT_WIDTH1280Default viewport width (200-4000)
BROWSERLOOP_DEFAULT_HEIGHT720Default viewport height (200-4000)
BROWSERLOOP_DEFAULT_FORMATwebpDefault image format (webp, png, jpeg)
BROWSERLOOP_DEFAULT_QUALITY80Default image quality (0-100)
BROWSERLOOP_DEFAULT_TIMEOUT30000Default timeout in milliseconds
BROWSERLOOP_USER_AGENT-Custom user agent string

Authentication Configuration

VariableDefaultDescription
BROWSERLOOP_DEFAULT_COOKIES-Default cookies as file path or JSON string (see Cookie Authentication Guide)

Console Log Configuration

VariableDefaultDescription
BROWSERLOOP_CONSOLE_LOG_LEVELSlog,info,warn,error,debugComma-separated list of log levels to capture
BROWSERLOOP_CONSOLE_TIMEOUT30000Page navigation timeout in milliseconds (not log collection time)
BROWSERLOOP_SANITIZE_LOGStrueEnable/disable sensitive data sanitization in logs
BROWSERLOOP_CONSOLE_WAIT_NETWORK_IDLEtrueWait for network idle before finishing collection
BROWSERLOOP_MAX_LOG_SIZE1048576Maximum total log size in bytes (1MB)

Note: Console log collection always waits exactly 3 seconds after page load to capture console messages. The timeout setting only affects how long the page has to initially load.

Log Sanitization

Console log sanitization is enabled by default (BROWSERLOOP_SANITIZE_LOGS=true) to protect sensitive information. When enabled, the following patterns are automatically masked:

Pattern TypeExample InputMasked Output
API Keyssk_live_1234567890abcdef...[API_KEY_MASKED]
Email Addresses[email protected][EMAIL_MASKED]
JWT TokenseyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...[JWT_TOKEN_MASKED]
Auth HeadersBearer abc123token...[AUTH_HEADER_MASKED]
URLs with Authhttps://api.com/data?token=secret123[URL_WITH_AUTH_MASKED]
**Secret Variabl

README truncated. View full README on GitHub.

Alternatives

Related Skills

Browse all skills
notebooklm

Query Google NotebookLM for source-grounded, citation-backed answers from uploaded documents. Reduces hallucinations through Gemini's document-only responses. Browser automation with library management and persistent authentication.

144
dev-browser

Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.

45
chrome-devtools

Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.

30
qa-tester

"Browser automation QA testing skill. Systematically tests web applications for functionality, security, and usability issues. Reports findings by severity (CRITICAL/HIGH/MEDIUM/LOW) with immediate alerts for critical failures."

25
browser-automation

Automate web browser interactions using natural language via CLI commands. Use when the user asks to browse websites, navigate web pages, extract data from websites, take screenshots, fill forms, click buttons, or interact with web applications. Triggers include "browse", "navigate to", "go to website", "extract data from webpage", "screenshot", "web scraping", "fill out form", "click on", "search for on the web". When taking actions be as specific as possible.

23
playwright-browser-automation

Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.

20