A Model Context Protocol server for taking screenshots of web pages using Playwright
Most browser automation work still happens through a UI a human drives. Browserloop MCP server moves it into the conversation instead. A Model Context Protocol server for taking screenshots of web pages using Playwright.
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.
The server publishes 8 tools. What each one is for:
url — stringwidth — numberheight — numberformat — stringquality — numberfullPage — booleanselector — stringScreenshots — The Screenshots tool exposed by this serverConfiguration is passed through the environment: BROWSERLOOP_DEFAULT_COOKIES, BROWSERLOOP_DEFAULT_FORMAT, BROWSERLOOP_DEFAULT_QUALITY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Usage on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Browserloop's toolset — url, width, height and 5 more — is a fair guide to whether it matches your workflow. It is maintained by mattiasw; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| url | string |
| width | number |
| height | number |
| format | string |
| quality | number |
| fullPage | boolean |
| selector | string |
| Screenshots | The Screenshots tool exposed by this server. |
Reference in MCP config:
```json
{
"mcpServers": {
"browserloop": {
"command": "node",
"args": ["dist/src/mcp-server.js"],
"env": {
"BROWSERLOOP_DEFAULT_COOKIES": "/home/username/.config/browserloop/cookies.json",
"BROWSERLOOP_DEFAULT_FORMAT": "webp",
"BROWSERLOOP_DEFAULT_QUALITY": "85"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| BROWSERLOOP_DEFAULT_COOKIES | Configuration value read at startup. | Optional |
| BROWSERLOOP_DEFAULT_FORMAT | Configuration value read at startup. | Optional |
| BROWSERLOOP_DEFAULT_QUALITY | Configuration value read at startup. | Optional |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.