Skip to main content
Glama
PGHQdev

OpenScreenShot

Official

openscreenshot

Website screenshots from your terminal, your CI, or your AI agent.

A local CLI and MCP server. It drives the Chrome already on your machine. No hosted service. No API key. No account.

npm npm downloads License Node

Website · CLI guide · MCP guide · Report a bug


Quick start

npx openscreenshot shot https://example.com --out example.png --full

That opens a headless Chrome, loads the page, saves a full-page PNG, and closes the browser.

You need: Node.js 22.12 or newer, and Google Chrome, Chromium, or Microsoft Edge. The package ships no browser of its own, so the install stays small.

Package manager

Run once

Install globally

npm

npx openscreenshot shot <url>

npm i -g openscreenshot

pnpm

pnpm dlx openscreenshot shot <url>

pnpm add -g openscreenshot

Bun

bunx openscreenshot shot <url>

bun add -g openscreenshot

Install globally to use the openscreenshot command everywhere. For CI, add it to the project instead (npm i -D openscreenshot), so each run uses the version in your lockfile.

Related MCP server: PagePixels Screenshots MCP Server

CLI

openscreenshot shot <url> [--out <file>|-] [--full] [--width <n>] [--height <n>]
                    [--redact <selector>]... [--redact-pattern <name>]... [--redact-rect <x,y,w,h>]...
openscreenshot serve

Option

Default

What it does

<url>

required

The page to capture. Use a full URL with https://.

--out <file>

screenshot.png

Where to write the PNG. Use - to write bytes to stdout.

--full

off

Capture the whole scrollable page, not only the viewport.

--width <n>

1280

Viewport width in pixels, from 200 to 3840.

--height <n>

800

Viewport height in pixels, from 200 to 2160.

--redact <selector>

none

Cover the elements that match a CSS selector. Repeat for more.

--redact-pattern <name>

none

Cover text that matches email, phone, or secret. Repeat, or use a comma list.

--redact-rect <x,y,w,h>

none

Cover a rectangle, in pixels of the output image. Repeat for more.

Examples

# Full page
openscreenshot shot https://example.com --out page.png --full

# Fixed desktop viewport
openscreenshot shot https://example.com --out desktop.png --width 1440 --height 900

# Narrow viewport to check a responsive layout
openscreenshot shot https://example.com --out narrow.png --width 390 --height 844

# Pipe the PNG to another tool
openscreenshot shot https://example.com --out - > shot.png

# Cover the account menu, every email address, and a 200x40 area at the top left
openscreenshot shot https://example.com --out safe.png --redact "#account-menu" --redact-pattern email --redact-rect 0,0,200,40

See Redaction for how it works and what it can miss.

The output is always PNG. A .jpg or .pdf file name does not convert it.

A narrow viewport changes the layout width only. The CLI keeps a desktop user agent, so it does not emulate a phone's touch input or pixel ratio.

Exit codes

Code

Meaning

0

The PNG was written.

1

The capture failed, for example Chrome not found or a timeout.

2

Bad usage or an option out of range.

Exit code 0 means the browser saved an image. It does not prove that the page loaded correctly, so look at the PNG for error pages or loading spinners.

MCP server

openscreenshot with no arguments on a piped stdin starts a Model Context Protocol server over stdio, which is how an MCP client runs it. openscreenshot serve does the same and stays for existing configs. Your AI client starts it as a local process; there is no URL to enter.

Add it to your client

Clients that use an mcpServers object (Claude Desktop, Cursor, Windsurf, and others):

{
  "mcpServers": {
    "openscreenshot": {
      "command": "npx",
      "args": ["-y", "openscreenshot"]
    }
  }
}

Claude Code:

claude mcp add openscreenshot -- npx -y openscreenshot

Restart or reload the client after you save the config. The client must find npx (or pnpm, bunx) on its PATH.

Tool: capture_screenshot

Input

Type

Default

Notes

url

string

—

Required. A full page URL.

fullPage

boolean

false

Capture the whole page.

width

integer

1280

200 to 3840.

height

integer

800

200 to 2160.

redact

object

—

Optional. See below.

{ "url": "https://example.com", "fullPage": true, "width": 1440, "height": 900 }

redact has three optional lists:

Field

Type

What it covers

selectors

string[]

Elements that match each CSS selector.

patterns

("email" | "phone" | "secret")[]

Matching text in the page and in form values.

rects

{ x, y, width, height }[]

Rectangles, in pixels of the output image.

{
  "url": "https://example.com",
  "redact": {
    "selectors": ["#account-menu"],
    "patterns": ["email", "secret"],
    "rects": [{ "x": 0, "y": 0, "width": 200, "height": 40 }]
  }
}

The tool returns the PNG as MCP image content (image/png). It does not write a file. To save a named file, use the CLI.

Redaction

Redaction puts black boxes over the targets in the page, and then takes the screenshot. The unredacted pixels never get into the PNG, so they never get to your MCP client or to a hosted model.

  • Selectors. The box covers the element and all of its children. If a selector matches no element, or is not valid CSS, the capture fails.

  • Patterns. email finds email addresses. phone finds numbers with 9 to 15 digits. secret finds common API key and token shapes (OpenAI, Anthropic, Stripe, GitHub, AWS, Slack, Google, JWT). It also finds any run of 32 or more letters, digits, and underscores that has both a letter and a digit, such as a hash. Patterns look in text and in the values of input, textarea, and select fields.

  • Rectangles. Use these for canvas, images, and cross-origin iframes, where selectors and patterns cannot look. A rectangle that is fully outside the image fails the capture.

When redaction is on, the tool pauses CSS animations, places the boxes, and takes the screenshot. Then it finds the targets again. If a target moved out of its box, the capture fails. A failed capture writes no file and returns no image.

Patterns can miss text. They do not find text split across elements, text drawn in a canvas or an image, or a format they do not know. They can also cover text that only looks like a match. Look at the image before you share it.

What it can and cannot capture

Each capture starts a fresh headless browser with an empty profile.

  • It can capture any page a signed-out visitor can see: public sites, docs, status pages, staging builds, and localhost dev servers.

  • It cannot see your cookies or signed-in sessions. A page behind a login shows the login screen.

  • It does not click, type, wait for a selector, or set cookies. Navigation waits until the network is quiet (networkidle2), for up to 30 seconds.

For signed-in pages, annotations, or PDF export, use the OpenScreenShot browser extension for Chrome and Firefox.

Use cases

  • CI/CD: capture pages on every deploy for release notes, docs, or visual review. See the CI guide.

  • DevOps: snapshot dashboards and status pages into incident reports and runbooks from cron or a chat command.

  • AI agents: let an agent look at the page it just built or changed.

Troubleshooting

Chrome not found. The CLI checks the standard install paths on macOS, Linux, and Windows. If your browser is somewhere else, set CHROME_PATH to the executable file:

CHROME_PATH=/usr/bin/chromium openscreenshot shot https://example.com

On Windows, Chrome installed for one user lives under %LOCALAPPDATA%, and Edge is not probed. Set CHROME_PATH for both. In an MCP client, set CHROME_PATH in the server's env block.

A script hangs on openscreenshot with no arguments. With no arguments and a piped stdin, the command starts the MCP server and waits for a client. It prints one line to stderr that says so. Run openscreenshot shot <url> for a capture.

Timeout. The page did not go quiet within 30 seconds. Pages with long-polling or streaming connections can do this.

Blank or half-loaded image. Some pages render after the network goes quiet. The CLI has no extra wait option yet.

Privacy and security

  • Everything runs on your machine. The package sends no telemetry and calls no OpenScreenShot server.

  • In MCP mode, your client receives the image. If the client uses a hosted model, it may send the image to that model's provider. Use redact to cover data before the image leaves the tool.

  • The headless browser runs with --no-sandbox so it works in containers and CI. Capture only URLs you trust.

MIT © OpenScreenShot @PGHQdev

Available Tools

1 tool
capture_screenshotAInspect

Capture a PNG screenshot of a public web page locally via the system Chrome. Use redact to cover elements, text patterns, or rectangles with black boxes before the screenshot is taken. The capture fails with no image if a selector matches nothing or the page changes during the capture.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYes
widthNo
heightNo
redactNo
fullPageNo

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden and does well: it discloses that capture is local via system Chrome, that redaction is applied before the shot is taken, and two concrete failure modes (unmatched selector, page changing mid-capture). It stops short of describing the return payload (image bytes, file path, or base64) and viewport defaults.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core action, then redaction, then failure semantics. Every sentence earns its place with no repetition of schema or name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No annotations and no output schema, so the description is the only source of behavioral context; it covers failure modes and redaction ordering but omits what the tool returns and how results are delivered. For a 5-parameter tool with a nested object, that leaves a real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Top-level schema coverage is 0%, so the description must compensate; it explains the redact concept (elements, text patterns, rectangles with black boxes), which maps onto selectors/patterns/rects. It says nothing about width, height, or fullPage, leaving those parameters to be inferred from names and constraints alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb (Capture), resource (a public web page), output format (PNG screenshot), and mechanism (locally via the system Chrome). There are no sibling tools to differentiate from, and an agent knows exactly what this tool produces.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains how to use the redact parameter and states the conditions under which capture fails, which is useful operational guidance. However, it gives no explicit when-to-use/when-not-to-use framing or prerequisites (e.g. page must be publicly reachable), so usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev2.5.1
    • First observedcapture_screenshot

TDQS

A3.9/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusing it with another; its purpose (capture a PNG screenshot of a URL with optional redaction) is unambiguous.

Naming Consistency5/5

The single name capture_screenshot follows a clean verb_noun snake_case convention, and nothing in the set deviates from it.

Tool Count3/5

A one-tool server is defensible for a narrow, focused purpose, but it sits at the thin end of the scale with no batching, waiting, or alternate-output operations.

Completeness3/5

Core capture with redaction is covered, but the surface omits common needs such as full-page vs viewport control, wait/ready conditions, custom headers, cookies/auth, and alternate formats like PDF, leaving plausible agent requests unserved.

Maintenance

ActivityActive
ResponsivenessWithin a week

Related MCP Connectors

Related MCP Servers