Screenshot Scout MCP Server
OfficialRelated Servers
Alternatives to Screenshot Scout MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceCaptures webpage screenshots via ScreenshotOne API, offering desktop, mobile, and element-specific views.1MIT
- FlicenseNot gradedqualityAmaintenanceEnables capturing web page images, including tiled full pages and specific DOM elements, with configurable viewport, wait strategies, and screencast/animated WebP output optimized for AI vision workflows.-
- 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
- AlicenseCqualityDmaintenanceEnables taking screenshots of web pages with support for multiple devices (desktop, mobile, tablet), custom dimensions, full-page capture, and various image formats. Built with Playwright for reliable web page rendering and screenshot generation.1MIT
- FlicenseNot gradedqualityAmaintenanceEnables fast, fresh webpage screenshots for AI vision workflows, including full-page tiling, element capture, and timed screencasts. Screenshots are optimized into 1072x1072 chunks and can return base64 images or save PNG/WebP files.-
- AlicenseAqualityBmaintenanceCapture screenshots, generate PDFs, and render HTML to images via AI agents. Supports batch capture, geo-targeting, async webhooks, and CSS/JS injection.11108 npm6MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between tools. Its purpose (capture a webpage as image or PDF) is stated unambiguously.
The single tool follows a clear verb_noun pattern (capture_screenshot) in snake_case. With one name there is no inconsistency to introduce, though consistency is trivially satisfied.
One tool is borderline thin; the screenshot domain is narrow enough that a single parameterized capture tool is defensible, but there is no separation for variants like full-page vs. viewport capture, batch capture, or quota status.
The core operation (capture) exists, but related lifecycle operations are missing: checking remaining quota before a consuming call, batch capture of multiple URLs, and listing or retrieving previously captured artifacts. Agents can work around this but will hit dead ends when quota or multi-URL needs arise.