screenshot-mcp binary for linux x64
screenshot-mcp binary for linux x64. The screenshot mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.
Capture full-page and viewport screenshots of any URL via Chrome DevTools Protocol — single static binary, no runtime required.
Everything the assistant can do here goes through one of these:
Cursor — Chrome is auto-downloaded on first use if not found. To override: "env": { "CHROME_PATH": "/path/to/chrome" }capture_page — Captures a screenshot of a web page, waiting for JavaScript to finish renderingInstallation goes through your MCP client rather than a global install: point it at @kembec/screenshot-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need one environment variable: CHROME_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
No manual setup required. On first use, screenshot-mcp automatically downloads a pinned Chromium build to your OS cache directory (~/.cache/screenshot-mcp/ on Linux, ~/Library/Caches/screenshot-mcp/ on macOS) if no Chrome is detected. If you already have Chrome installed, it is used directly — no download occurs. You can also set CHROME_PATH to point to any Chromium-compatible binary.
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. Screenshot's toolset — Cursor, capture_page — is a fair guide to whether it matches your workflow. It is maintained by kembec; 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 |
|---|---|
| Cursor | Chrome is auto-downloaded on first use if not found. To override: "env": { "CHROME_PATH": "/path/to/chrome" }. |
| capture_page | Captures a screenshot of a web page, waiting for JavaScript to finish rendering. |
{
"mcpServers": {
"screenshot-2": {
"command": "npx",
"args": ["-y", "@kembec/screenshot-mcp"],
"env": {
"CHROME_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
No manual setup required. On first use, screenshot-mcp automatically downloads a pinned Chromium build to your OS cache directory (~/.cache/screenshot-mcp/ on Linux, ~/Library/Caches/screenshot-mcp/ on macOS) if no Chrome is detected. If you already have Chrome installed, it is used directly — no download occurs. You can also set CHROME_PATH to point to any Chromium-compatible binary.
| Variable | Description | Required |
|---|---|---|
| CHROME_PATH | Filesystem location the server is allowed to use. | 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.