screenshotscout/screenshotscout-mcp

Use Screenshot Scout from an MCP client to capture
HTTP or HTTPS webpages as images or PDFs.
This server exposes one tool, capture_screenshot. It supports full-page and
element captures, device and viewport controls, location selection, page
interaction and blocking options, image sizing and quality, PDF layout, caching,
temporary result URLs and eligible MCP image content.
What you need
- A Screenshot Scout account and an
access key from the API keys page.
- Node.js 22 or newer for npm/stdio installation. Claude Desktop's MCPB runtime
is bundled by Claude.
- The optional secret key only when your selected API key requires signed
Screenshot Scout requests.
Every capture uses your Screenshot Scout account and is subject to its plan,
quota, and rate limits.
Local stdio with npm
Start with this local stdio configuration:
If the access key requires request signing, add the secret locally:
Keep personal configuration files out of source control. Credentials are process
environment values, not tool arguments. See
client-specific copy-paste configurations for Claude
Desktop, Claude Code, Cursor, VS Code/GitHub Copilot, Devin, and Cline.
Run from a source checkout
Point the client at the absolute path to dist/stdio.js with node, and provide
the same environment variables shown above.
Claude Desktop MCPB
To install the Claude Desktop extension:
1. Download screenshotscout-mcp- .mcpb from that version's GitHub
release.
2. In Claude Desktop, open **Settings → Extensions → Advanced settings** and
choose **Install Extension…**.
3. Select the downloaded file.
4. Enter the required access key. Enter the secret key only for an API key that
requires signed requests.
Claude Desktop treats both fields as sensitive settings. The v0.1.0 MCPB
supports Windows.
Hosted Streamable HTTP
The hosted API-key endpoint is live at:
It is intended only for clients that can attach a static HTTP header:
The endpoint accepts an access key only. Never send a Screenshot Scout secret
key to it, and never put either key in the URL or a tool argument. Clients that
cannot attach a static Bearer header cannot use this endpoint.
API keys that require request signatures must instead use local stdio or MCPB,
or use a dedicated unsigned access key for the hosted endpoint.
Local stdio with Docker
Build the production image from a source checkout:
Pass credentials from the local environment and keep stdin attached for MCP
stdio traffic:
SCREENSHOTSCOUT_SECRET_KEY remains optional. The image runs as an unprivileged
user and contains only the compiled stdio server and its production dependencies.
It declares no port or container health check: an MCP client owns the stdio
process and verifies readiness by completing MCP initialization. The image and
its Docker MCP Catalog metadata in docker-mcp-catalog.yaml are local
preparation; no public image is implied by these commands.
Tool: capture_screenshot
capture_screenshot sends one capture request for the supplied URL and options.
The target webpage is external, and its returned content must be treated as
untrusted.
Inputs
Only url is required. Captures use a 1280×720 viewport by default. When no
format is specified, the tool returns JPEG at quality 60. resultMode defaults
to "auto".
| Group | Inputs |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |