getscreenshot-mcp
OfficialRelated Servers
Alternatives to getscreenshot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceScreenshot, visual-diff, and AI page-analysis API for AI agents. Capture any URL as PNG, JPEG, WebP, PDF, or HTML, diff two versions of a page to catch visual regressions, and get an AI summary of what a page contains.358 npm1MIT
- AlicenseAqualityCmaintenanceGive AI agents eyes on any web page: pixel-perfect screenshots, print-ready PDFs, branded OG images, code images, and structured page extraction (JSON or Markdown).722 npmMIT
- AlicenseAqualityBmaintenanceCapture screenshots, generate PDFs, and render HTML to images via AI agents. Supports batch capture, geo-targeting, async webhooks, and CSS/JS injection.1144 npm6MIT
- 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 gradedqualityCmaintenanceEnables AI agents to capture any public URL as PNG, JPEG, or PDF via REST API or MCP tools, including screenshot capture, page description, and PDF rendering.12 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI tools to turn web pages into optimized visual captures, including full-page tiles, specific DOM elements, and timed animated recordings for vision-model workflows.MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: public-page screenshot, local HTML rendering, visual comparison, PDF export, and quota reporting. capture_screenshot and render_html overlap in output type, but the descriptions sharply separate public URLs from local HTML strings.
All five tools follow a consistent verb_noun snake_case pattern: capture_screenshot, render_html, compare_screenshots, capture_pdf, get_usage. There are no mixed naming conventions or vague standalone verbs.
Five tools is well-scoped for a screenshot service, and each tool earns its place by covering a distinct workflow. The set avoids both a thin single-tool surface and an unnecessarily large catalog.
The set covers the core lifecycle: capture public pages, render local HTML, compare versions, export PDFs, and check quota. A minor gap is that PDF export is only available for public URLs, not local HTML rendered via render_html, though this is a workaroundable limitation.