screenshot-vision-mcp
Related Servers
Alternatives to screenshot-vision-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables Claude Code and other MCP clients to analyze local images using Ollama's multimodal models, with privacy as images are processed locally.1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for local Ollama vision analysis, enabling text-only agents like Claude Code to inspect images via a single tool. Processes images locally with Ollama, keeping image bytes on the machine and returning text reports.2MIT
- FlicenseAqualityBmaintenanceEnables Claude to capture screenshots, watch your screen in real-time, read text via OCR, and analyze video files, all running locally as an MCP server.14-
- FlicenseAqualityDmaintenanceMCP server for vision capabilities, enabling screenshot, camera, and image analysis using Ollama vision models.41-
- FlicenseNot gradedqualityBmaintenanceAn MCP server that gives Claude the ability to watch any desktop window, detecting changes and providing compact image bundles for Claude's vision, enabling real-time screen-watching without API costs.-
- AlicenseBqualityDmaintenanceA local vision-language MCP server that enables Claude Code to perform image analysis, OCR, and UI-to-code generation using the Qwen3 VL 4B model via LM Studio. It provides privacy-focused visual processing by running entirely on the user's local hardware without external API dependencies.3168 npm1MIT
TDQS
Scored across 3 tools
analyze_screenshot and capture_window both perform capture-and-analyze, but their contexts are clearly differentiated (headless URL vs. live window). locate_element is distinct as it returns coordinates. Minor overlap exists for public pages that could be captured either way.
All three tools follow a consistent verb_noun pattern with snake_case: analyze_screenshot, capture_window, locate_element. Predictable and clear.
Three tools is a focused, appropriate scope for a screenshot-vision server—each serves a distinct purpose without redundancy.
The set covers the core workflows: capture from URL, capture from live window, and element location. A general 'analyze existing image' tool is missing, but the primary use cases are covered.