Website Screenshot Capture MCP Server
Related Servers
Alternatives to Website Screenshot Capture MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to capture public web pages as images with configurable viewport, format, full-page behavior, wait conditions, timezone, and locale, and to check remaining screenshot quota.306 npmMIT
- 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
- 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
- AlicenseNot gradedqualityBmaintenanceEnables rendering complete HTML documents (with inline CSS) into PNG images or A4 vector PDFs at a chosen viewport, and screenshotting live web pages by URL as whole-page or single-element captures. Each render also returns a shareable CDN URL, with configurable size, DPI, delays, and wait selectors.287 npmMIT
- 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.-
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.