snaprender-mcp
Related Servers
Alternatives to snaprender-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to render website screenshots and PDFs, check page changes, and retrieve usage stats via REST calls.-

screenshotrun-mcpofficial
AlicenseAqualityCmaintenanceGive your AI agent the ability to capture website screenshots. Works with Claude, Cursor, and any MCP client. Supports full-page, dark mode, mobile emulation, OG image generation, base64 output, and more. Free tier included.2307 npmMIT
Grabbitofficial
AlicenseNot gradedqualityCmaintenanceScreenshot MCP for agents. Send a public URL, get a pixel-perfect CDN image. Full page, header, mobile, or custom. Cookie banner suppression. Handles sites that block headless browsers. Works with Claude, Cursor, Codex. $0.002/grab.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 gradedqualityCmaintenanceEnables AI assistants to capture website screenshots, automate browser interactions, and manage recurring screenshot configurations across 150+ global locations. It also supports AI-powered domain research and visual change monitoring for any web page.6 npmMIT
- 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.364 npm1MIT
TDQS
Scored across 11 tools
Each tool targets a distinct action+resource: single capture, batch capture, cache check, URL signing, batch polling, content extraction, webhook CRUD/test, and usage. The capture-family tools (take_screenshot, batch_screenshots, extract_content) are clearly differentiated by descriptions covering single vs. bulk vs. structured extraction.
Mostly a consistent verb_noun pattern (take_screenshot, check_screenshot_cache, get_batch_status, extract_content, list_webhooks, create_webhook, delete_webhook, test_webhook, get_usage). The lone deviation is batch_screenshots, which is noun-first but still readable and unambiguous.
11 tools is well within the sweet spot for a screenshot/rendering service, with each tool covering a distinct capability (capture, batch, cache, signing, extraction, webhooks, usage). No tool feels redundant or padded.
Covers the core lifecycle: single/batch capture, cache check, signed sharing, content extraction, webhook management, and usage reporting. Minor gaps exist such as no batch cancel/list or update_webhook (delete-and-recreate is the workaround), but no workflow dead-ends.