getsnap-mcp
Related Servers
Alternatives to getsnap-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityDmaintenanceEnables Claude to capture screenshots of the screen, windows, regions, and web pages, and compare screenshots for visual regression testing.6MIT
- AlicenseAqualityDmaintenanceEnables Claude Code to capture and analyze web page screenshots, responsive layouts, and page metadata using Puppeteer. It allows developers to perform visual UI inspections and compare designs across various viewports directly within the terminal.3MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI vision workflows to capture fresh webpage screenshots, specific DOM elements, and timed screencasts, automatically limiting resolution and tiling full pages into 1072x1072 chunks for LLM-friendly processing.-
- AlicenseAqualityBmaintenanceEnables AI agents to capture screenshots, scrape structured page content, and run automated visual checks on live websites via a headless Chromium browser.3MIT
- AlicenseAqualityBmaintenanceEnables AI agents to capture public web pages as screenshots or PDFs and to extract their content as markdown, text, HTML, links, or metadata. Pages render in a real Chrome browser, so JavaScript-drawn content is included, and a usage tool reports plan and remaining captures.3132 PyPIMIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: capture (screenshot/pdf), compare two pages, audit accessibility, and check credits. The only potential overlap—capture_screenshot vs capture_pdf vs compare_pages, all of which render URLs—is resolved explicitly in descriptions (e.g., PDF can't be shown inline, compare diffs two pages).
All tools follow a consistent snake_case verb_noun convention: compare_pages, audit_accessibility, capture_screenshot, capture_pdf, check_usage. The shared capture_ prefix is used sensibly for the two rendering tools.
Five tools is well-scoped for a page-capture/audit service, with no filler. Each tool earns its place and covers a distinct capability.
Core lifecycle is covered: screenshot, PDF, comparison, accessibility audit, and credit usage. Minor gaps exist (e.g., no HTML/text extraction or element-scoped capture beyond device/full_page params), but agents can work around these.