ui-screenshot-mcp
Related Servers
Alternatives to ui-screenshot-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceMCP server that gives AI agents browser-based access to Mobbin for design research, screen discovery, and screenshot collection through automated browser control.103-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that works with Mobbin — 600k+ real app screens and flows from 1,100+ apps. Search screens, browse flows, grab palettes, build better UI without leaving Claude.5ISC
- AlicenseAqualityCmaintenanceMCP server that scrapes Terminal Trove to search CLI/TUI tools and retrieve design references like screenshots and install commands for agentic UI research.12MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that lets coding agents ground UI work in real product screens by fetching one to three reference screens as inline images for a specific layout, state, or interaction question, and by looking up fonts, icons, or animated icons together with their recorded licenses. It also returns the full or selected design reference—overview, colors, typography, components, and provenance—for any web screen already picked.MIT
- AlicenseNot gradedqualityAmaintenanceScreenshot any URL from the command line with metadata sidecars, accessibility audits, visual regression, performance analysis, and MCP integration for AI-assisted development.34 npm1MIT
- AlicenseNot gradedqualityBmaintenanceLocal MCP server providing a curated 201-card design reference library with natural-language style search, structured filtering, card retrieval, theme borrowing, and capture tooling — all private and offline.1MIT
TDQS
Scored across 10 tools
Most tools have distinct purposes: external source exploration (ui_sources, search_ui, get_ui_screens, download_ui), local library management (library_search, library_stats), and browser capture (open_browser, capture_screenshot, close_browser, list_screenshots). The two search tools (search_ui vs library_search) and two image-saving tools (download_ui vs capture_screenshot) could be momentarily confused, but descriptions clarify remote vs local and download vs capture.
The set mixes verb_noun names (capture_screenshot, open_browser, list_screenshots) with noun_phrases (ui_sources, library_stats) and uses inconsistent prefixes like 'ui_' and 'library_' for related concepts. It remains readable, but the convention is not predictable across all tools.
Ten tools is well-scoped for a server that covers source discovery, search, screenshot capture, download, and local library management. Each tool has a clear role in the workflow without unnecessary duplication.
The surface covers the main lifecycle: discovering sources, searching remote and local libraries, downloading screens, opening a browser, capturing screenshots, and listing outputs. Minor gaps exist, such as no explicit tool to delete or update local library entries, but core workflows are covered.