Visual Memory MCP

io.github.putervisionPublished by GitHub account putervisionv1.4.2Updated Oct 27, 2026

Local visual UI cache for AI agents using perceptual hashing, CLIP, and 3D spatial grounding.

The publisher's own server: Memory.fit

Overview

AI-generated overview

Local-first visual memory cache for AI coding assistants, storing UI screenshots as perceptual hashes and CLIP embeddings to cut repeated vision calls.

What you can do
  • Analyze screenshots and recall cached visual states by perceptual hash or semantic vector search, with session context and compact slices
  • Ground UI elements to CSS selectors and coordinates, record action outcomes, plan navigation paths and wait for target visual states
  • Ingest WebM/MP4 recordings into keyframe timelines, compare states and trajectories, build evidence packs and export fine-tuning datasets
  • Manage visual spec baselines for regression checks, save and restore snapshots, undo ingestion and purge stored states
When to use it
Useful for frontend and UI-testing work where an assistant repeatedly looks at the same screens, or where screenshots and E2E recordings should become a searchable local visual history. Not intended for headless backend work, continuous high-framerate video, or very low-memory machines.
Requirements
Runs as a local stdio process installed from npm; Node.js 18.18.0 or newer. A workspace must be initialized first, which scaffolds database directories, a .env file and IDE rules. The full local CLIP model needs roughly 300 MB of RAM and downloads model files unless started with the skip-model-load option.
Before you install
It stores screenshots, accessibility-tree data and video keyframes on disk, so review the privacy and PII-redaction claims before ingesting sensitive screens. Initialization writes files into the project, including .gitignore and .env, and the tools can delete or revert stored states. Optional vision LLM fallback may send images to an external provider depending on configuration.

Installation

In SourceWeft

  1. Open Visual Memory MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@putervision/vision-memory-mcp

[npm version] [version] [npm downloads] [CI] [Node] [TypeScript] [Website] [License: MIT]

@putervision/vision-memory-mcp is a zero-infrastructure, local-first Model Context Protocol (MCP) server and CLI tool that provides AI coding assistants (such as Cursor, Claude Code, Gemini, or Copilot) with visual state caching using perceptual hashing, local CLIP embeddings, and transition graphs to eliminate repetitive vision LLM calls.

🌐 Official Documentation & Website: visionmemorymcp.com


⚡ Quick Start & Installation

Prerequisites: Node.js >= 18.18.0

1. Installation

bash
# Global installation via npmnpm install -g @putervision/vision-memory-mcp

2. Workspace Initialization

Run init in your project root to scaffold database directories, .gitignore, .env, and IDE rules:

bash
vision-memory-mcp init --yes

3. Basic MCP Client Setup

Add to your MCP client config (e.g. .cursor/mcp.json or .vscode/mcp.json):

json
{  "mcpServers": {    "vision-memory-mcp": {      "command": "vision-memory-mcp",      "args": ["run"]    }  }}

Alternative Options & CLI Usage Examples

bash
# Run stdio MCP server directly via binary (after global install)vision-memory-mcp run
# Start server skipping heavy CLIP model downloads (air-gapped / offline mode)vision-memory-mcp run --skip-model-load
# Re-initialize across all registered workspace projectsvision-memory-mcp init-global
# Health check dependencies, sharp bindings, and git safetyvision-memory-mcp doctor
# Run health diagnostics & aggregate metrics across all registered projectsvision-memory-mcp doctor-global
# Inspect stored visual states and metadata in terminal ASCII tablevision-memory-mcp inspect
# Register baseline design mockup contract (Visual SDD)vision-memory-mcp spec set --name "Dashboard" --file ./dashboard-spec.png
# Save visual memory checkpoint snapshotvision-memory-mcp snapshot save --name "v1.0-milestone"
# Ingest WebM / MP4 video recording into visual state memory timelinevision-memory-mcp video ingest ./playwright-test.webm --category playwright_test
# Open interactive force-directed visual graph viewer in browservision-memory-mcp view

🌟 Key Highlights

  • 👁️ Perceptual Visual Caching & Compact Slices: Sub-5ms L1/L2 dHash zero-token fast-path layout recognition and sub-1KB compact_slice export for Pentad System 1 StatePack assembly.
  • 🎬 WebM & MP4 Video Ingestion: Digest E2E test recordings & screen captures into searchable keyframe visual states & state transition graphs.
  • ⚡ 15 Core MCP Tools: High-coherence consolidated toolset covering perception, video memory, evidence packs, trajectory comparison, semantic retrieval, element grounding, visual SDD, snapshots, and unified context & metrics.
  • 🔗 Dual-MCP Synergy & Immutable Evidence Packs: Deeply bridges @putervision/state-memory-mcp task DAGs with visual state memory, generating cryptographically hashable evidence packs for compliance and audit trails.
  • 📉 Reduced Token Overhead: Caches UI states locally using dHash, local CLIP vector search, and accessibility trees to maximize vision token savings.
  • 🚀 Sub-5ms Fast-Path Latency: Eliminates repetitive vision LLM API calls and avoids visual hallucination loops.
  • 🎯 Element Grounding & Action Target Prediction: Maps screen elements to CSS selectors and coordinates for deterministic UI interaction.
  • 🎨 Visual Spec-Driven Development (Visual SDD): Register design mockups or screenshots as perceptual baseline contracts to verify visual regression.
  • 🛡️ 100% Local-First Privacy: Local LanceDB vector store, local CLIP model, zero cloud telemetry, and PII redaction guarantees.

🛠️ MCP Tool Suite

@putervision/vision-memory-mcp provides 15 production-grade consolidated MCP tools structured across 4 core visual perception & automation domains:

  • Perception & Semantic Search: analyze_screenshot (L1/L2 perceptual dHash & AX tree parsing, single/batch), recall_memory (text & image semantic vector search), get_session_context (aggregated cache hit metrics, recent states, and sub-1KB compact_slice export).
  • Element Grounding & Navigation: predict_next_action (deterministic CSS selectors & bounding coordinates), record_outcome (UI action transitions & visual blockers), get_navigation_paths (BFS shortest-path planner), wait_for_visual_state (polling for target UI state).
  • Video Trajectories & Evidence Packs: manage_video (WebM/MP4 keyframe ingestion, timeline search), compare_states (visual layout diffs & video trajectory comparison), create_evidence_pack (cryptographic audit proof linking video keyframes to state-memory DAGs), export_trajectories (multimodal fine-tuning datasets).
  • Snapshots & Visual SDD: manage_visual_spec (mockup baseline contracts & regression checks), manage_snapshot (checkpoints, export, restore), undo_visual_mutation (revert state ingestion), forget_state (privacy & PII purging).

👉 For complete parameter specifications, return schemas, and example payloads, see the Formal API Reference and Features & Architecture Guide.


🚀 Architecture At a Glance

                     Incoming Screen                            │                            ▼              ┌──────────────────────────────┐              │ L1: In-Memory Cache Lookup   │ ──(Hit)──▶ Return Cached Description & Grounded Elements              └──────────────┬───────────────┘                             │ (Miss)                             ▼              ┌──────────────────────────────┐              │ L2: Perceptual Hash Scan     │ ──(Hit)──▶ Return Cached Description & Grounded Elements              └──────────────┬───────────────┘                             │ (Miss)                             ▼              ┌──────────────────────────────┐              │ L3: Local CLIP Vector Search │ ──(Hit)──▶ Return Semantically Close              └──────────────┬───────────────┘                             │ (Miss)                             ▼              ┌──────────────────────────────┐              │ L4: Vision LLM Fallback      │ ──(Ingest)──▶ Save Redacted State to DB              └──────────────┬───────────────┘

📚 Documentation Directory

Explore dedicated guides and deep dives in the docs/ directory:

GuideDescription
🏗️ Architecture & Codebase DistillationHigh-signal architectural overview, 4-tier pipeline, module inventory, and design decisions.
🚀 Features & ArchitectureKey features, 4-tier retrieval pipeline, element grounding, and Dual MCP Synergy.
📘 Formal API ReferenceComplete specifications, parameters, and schemas for all 15 consolidated MCP tools.
🔌 Multi-IDE Integration GuideStep-by-step configs for Cursor, Claude Desktop, Antigravity, Windsurf, Zed, Roo Code & Agent Rules.
💻 CLI Commands ReferenceFull guide for all 16 CLI management, visual spec, and snapshot commands.
⚙️ Configuration GuideComplete .env environment variables, thresholds, and L4 vision fallback setup.
🔒 Storage Encryption & SecurityEncryption details, local storage privacy, and PII masking guarantees.
🤝 Contributing GuideDevelopment setup, codebase structure, and submission guidelines.
🛡️ Security PolicySecurity vulnerability reporting and privacy disclosures.
📜 ChangelogChronological record of release features, fixes, and patch updates.

⚠️ When Not to Use This Server

While vision-memory-mcp is designed for visual frontend state caching, UI testing, and multimodal workflows, it may not be appropriate for:

  • Headless / Pure Backend Development: Non-visual CLI tools, database scripts, or pure backend microservices with no UI rendering. (Use state-memory-mcp standalone instead).
  • High-Framerate Live Video Streaming: Continuous 60 fps live video ingest without discrete keyframe or test action boundaries.
  • Ultra Low-Memory Embedded Environments (<512 MB RAM): Running full local CLIP neural embeddings requires ~300 MB RAM (use --skip-model-load for lightweight dHash-only perception if memory is constrained).

🧪 Testing

bash
# Run full unit and integration test suite across all 72 test files (312 tests)npm run test

⚖️ License & Disclaimers

Developed and maintained by PuterVision. Released under the MIT License.

  • Local Storage Guarantee: Provided "as is" without warranty. Screenshots, perceptual hashes, vector embeddings, and transition graphs are stored locally unencrypted at the application level in .vision-memory-mcp/. Zero telemetry or analytics data is ever transmitted.
  • Trademarks & Non-Affiliation: Product names (Cursor, Claude Code, Gemini, Windsurf, VS Code, Sharp, LanceDB, ONNX, HuggingFace) are property of their respective owners and used solely for compatibility identification.

Source: README.md at commit 622c7fc

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

7
  1. v1.4.2LatestOct 8, 2026
  2. v1.4.1Oct 3, 2026
  3. v1.4.0Oct 2, 2026
  4. v1.3.2Sep 30, 2026
  5. v1.3.1Sep 29, 2026
  6. v1.3.0Sep 26, 2026
  7. v1.2.1Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Memory integrations