Website Screenshot Capture MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Website Screenshot Capture MCP Server Take a full-page screenshot of example.com as a PNG"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Website Screenshot Capture MCP Server
An MCP server for the Mamba Labs Website Screenshot Capture actor on Apify. Turn a list of URLs into screenshot links, one row per page.
What's Inside
Related MCP server: screenshot
What it does
Give page URLs. Each page opens in a Chromium browser, waits for the load state you pick, and is saved as a PNG or JPEG image. You get one row per page with the image link, the final URL after redirects, the HTTP status, the page title, and the image size. Full page captures run up to 16,000 pixels tall.
All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.
Quick start
You need Node.js 18 or newer and an Apify account with an API token.
Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:
{
"mcpServers": {
"mamba-website-screenshot-capture": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-website-screenshot-capture"
],
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}Restart the client. The capture_website_screenshots tool appears.
Prerequisites
Node.js 18 or newer.
An Apify API token from console.apify.com/account/integrations, set as
APIFY_TOKEN. The server lists its tool without a token; a call needs one.
Example prompts
"Take full page screenshots of these three competitor home pages."
"Capture stripe.com at a 390 pixel mobile width as a JPEG."
"Screenshot each landing page in this list and tell me which ones return an error."
Tool
capture_website_screenshots. One tool. Example arguments:
{
"urls": [
"https://example.com"
],
"full_page": true
}Inputs
Every buyer facing input of the actor. Omitted inputs take the actor's own defaults.
Input | Type | Required | Description |
| array | no | Pages to capture, each starting with http:// or https://. A bare domain such as example.com gets https:// added. From Clay, put the column inside a one item list. |
| boolean | no | yes captures the whole scrollable page, up to 16,000 pixels tall. no (default) captures the visible window only. |
| number | no | Browser window width, 320 to 3840. Default 1280. |
| number | no | Browser window height, 240 to 2160. Default 800. With Full page on, the image is as tall as the page. |
| string | no | png (default) or jpeg. JPEG files are smaller. |
| number | no | 1 to 100, used for jpeg only. Default 80. |
| string | no | When the page counts as loaded. load (default): the page and its images loaded. domcontentloaded: the HTML is parsed, faster. networkidle: no network traffic for 0.5 s, best for pages that load content late. |
| number | no | Extra wait after the page loads and before the capture, 0 to 20000. Default 0. |
| boolean | no | yes scrolls down the page before the capture so images that load on scroll appear, then returns to the top. Default no. |
| array | no | Elements to hide before the capture, for example a cookie banner or a chat widget: #cookie-banner, .chat-widget. |
| boolean | no | yes (default) skips analytics, ad, and session replay scripts and video or audio files, which draw nothing you need in the image and make pages slower. no loads everything, so ads appear. |
| number | no | Longest wait for one page to load, 10 to 120. Default 60. A page still loading at this point is captured as it stands and marked partial. |
| string | no | Optional. The run stops before a charge that would pass this amount. Summary rows are always returned. |
| string | no | auto (default): pages load through the Apify proxy pool. none: pages load straight from the Apify server. A reliability setting only; it does not change what you pay. |
Pricing
Pay per event on Apify, billed to your Apify account. Prices in USD.
Event | Free plan | Bronze | Silver | Gold |
| $0.014 | $0.0133 | $0.0126 | $0.0119 |
| $0.023 | $0.02185 | $0.0207 | $0.01955 |
| $0.013 | $0.013 | $0.013 | $0.013 |
Pages that refuse the browser, pages that answer an HTTP error, unusable URLs, and refused input are free. Mamba Labs pays the platform costs of the run, Apify proxy traffic included.
Full actor documentation
apify.com/mambalabs/website-screenshot-capture
License
MIT. See LICENSE.
Available Tools
1 toolcapture_website_screenshotsCapture website screenshotsARead-onlyIdempotent
Open each URL in a Chromium browser and save a PNG or JPEG screenshot, full page or window only. Returns one row per URL with the image link, final URL, HTTP status, page title, and image size. Pages that refuse the browser come back as free blocked rows.
Inputs: urls, format, delay_ms, full_page, +10 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
The server exposes exactly one tool, so there is no possibility of misselection or overlap with a sibling tool. Its purpose (batch URL-to-image capture) is stated unambiguously.
A single snake_case verb_noun name (capture_website_screenshots) is internally consistent and follows a predictable convention. There is no competing convention to conflict with it.
The domain is genuinely single-operation (batch screenshot capture), so one tool is defensible rather than an oversight. It is on the thin side — no companion tool for retrieving or cleaning up stored images — but not a mismatch for the stated scope.
Core capture is well covered, including status, title, final URL, and blocked-page handling, which are good lifecycle signals. However, there is no way to list, fetch, or delete previously saved screenshots, and viewport/timeout/wait configuration is only hinted at, leaving agents at a dead end for any post-capture workflow.
Maintenance
Related MCP Connectors
Full-page, first-screen, mobile or element screenshots of any URL as PNG, JPEG or PDF.
Pixel-perfect webpage screenshots rendered in a real browser, full-page or viewport, via one POST.
Screenshots of any public web page as PNG, JPEG, WebP, PDF or a scrolling video.
Capture website screenshots, run bulk captures, and manage screenshot schedules and history.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides tools to capture pixel-perfect website screenshots as images or PDF. Supports configurable viewport, full-page capture, CSS injection, and returns either viewable images or base64-encoded content.MIT
- FlicenseNot gradedqualityBmaintenanceProvides pixel-perfect webpage image rendering in a real browser, supporting full-page or viewport captures with anti-bot and protected-page handling via a simple POST request.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to capture web page and DOM element images, tile full pages into AI-friendly chunks, and record animated screencasts with configurable waits and JavaScript injection.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants such as Claude, ChatGPT, Cursor, and Claude Code to capture full-page, viewport, mobile, and desktop images of web pages, returning signed public URLs. Supports JavaScript rendering, custom viewports, and device emulation for visual documentation, design comparison, and layout analysis.MIT