A
licenseA
qualityB
maintenanceEnables blind AI coding models to debug visual bugs by capturing screenshots, analyzing them with a vision-capable model, and returning a written report.
1
5
MIT
vision-memory-mcp
by putervision
Related Servers
Alternatives to vision-memory-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables LLMs to capture and analyze screenshots of your screen, windows, or regions with smart detection capabilities. Features natural language queries, automatic window targeting, and text enhancement for UI debugging and visual inspection.2MIT
- AlicenseNot gradedqualityBmaintenanceEyes for text-only LLMs: decodes screenshots into exact structured text (words, coordinates, sizes, colors) using pure-code CV and OCR. Enables text-only models to reason about UI layouts without vision models or VRAM usage.2MIT
- FlicenseNot gradedqualityAmaintenancePersistent memory for AI coding agents: local-first semantic search, dependency graphs, git history.1-
- AlicenseNot gradedqualityCmaintenanceProvides structured visual analysis tools for coding agents, enabling UI analysis, screenshot comparison, OCR, and crop-based refinement through VLM.MIT
- AlicenseNot gradedqualityAmaintenanceVisual memory for computer-use agents — stores UI screenshots as semantic scene nodes and queries them by intent across sessions.MIT
TDQS
B3.1/5.0
Scored across 24 tools
Disambiguation2/5
Several tools have overlapping purposes: compare_states and get_visual_diff both return visual differences between two states; analyze_screenshot and recall_memory both accept screenshots and return state information; export_visual_trajectories and export_joint_trajectories both export trajectory data; save_visual_snapshot and export_snapshot both create snapshot archives. This creates ambiguity in tool selection.
Naming Consistency4/5
Most tools follow a consistent verb_noun pattern (e.g., list_visual_specs, analyze_screenshot, recall_memory). The only outlier is 'app_version', which is a noun phrase rather than an action. Minor inconsistency.
Tool Count2/5
At 24 tools, the set feels bloated. Several tools could be consolidated (compare_states/get_visual_diff, export_visual_trajectories/export_joint_trajectories, save_visual_snapshot/export_snapshot), and batch_analyze_screenshots is just a convenience wrapper. The count exceeds the recommended range and doesn't justify itself.
Completeness3/5
The tool set covers core visual memory operations (ingest, search, compare, snapshot, export, forget, navigate), but has gaps: no direct way to list all visual states, no update/delete for visual specs, and create_visual_blocker depends on an external server (state-memory-mcp) for the actual logging, creating a dead end. Overall coverage is decent but not comprehensive.
Maintenance
ActivityActive
ResponsivenessNo issues