screenshot-mcp
Related Servers
Alternatives to screenshot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for capturing screen regions directly into Claude Code conversations via hotkeys or tool calls. It provides Windows-specific screen snipping with multi-monitor support, persistent storage, and automatic management of captured images.MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables Claude Code and other MCP clients to take screenshots of the full screen or specific windows, with support for repeated captures over intervals.131 npm8MIT
- AlicenseNot gradedqualityAmaintenanceOpen-source screenshot tool for Windows with a built-in MCP server that allows AI assistants like Claude to capture and view screen content through tools like take_screenshot, ask_user_to_select_region, and more.3MIT
- AlicenseNot gradedqualityDmaintenanceA Windows MCP server that enables AI agents to capture screenshots of open windows or the full desktop via stdio or HTTP.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for capturing screenshots of desktop windows on Windows. Allows AI assistants to see what's on screen for UI development, debugging, and iterating on designs.MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that enables AI assistants to capture and view screenshots, supporting multiple AI tools and platforms.9 npm22MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: full-screen capture, region capture, image viewing for vision, listing, specific deletion, and bulk cleanup. The only potential overlap is delete_image and cleanup, but cleanup is clearly bulk with filters, so boundaries are clear.
Most tools follow a verb_noun pattern (view_image, list_images, delete_image), but screenshot, screenshot_region, and cleanup deviate slightly. The naming is still readable and predictable, with only minor inconsistencies.
Six tools is well-scoped for a screenshot server, covering capture, viewing, listing, and deletion without unnecessary bloat. The count feels natural and each tool earns its place.
The server covers the full screenshot lifecycle: capture (full and region), view for AI analysis, list, delete specific, and cleanup. No obvious missing operations are apparent for the stated purpose.