mcpField
V
Visual Memory MCP

Visual Memory MCP

Local
visionmemorymcp.comMemory & Knowledge39Updated 3w ago

About Visual Memory MCP

Visual Memory MCP is a local-first MCP server and CLI that caches UI visual states for AI coding assistants such as Cursor and Claude Code, reducing repeated vision LLM calls. It combines perceptual hashing, local CLIP embeddings and transition graphs without extra infrastructure.

Key features

  1. 01dHash-based fast path for cached UI states
  2. 02Local CLIP embeddings with semantic search
  3. 03Keyframe ingestion from WebM and MP4 recordings
  4. 04Element grounding and action target prediction
  5. 05Visual spec checks for regression testing

Use cases

  1. 01Reducing repeated vision calls on UI screenshots in coding assistants
  2. 02Searching UI states and transition paths from end-to-end test recordings
  3. 03Registering design mockups as baselines for visual regression checks

MCP support

The project runs as an MCP server that exposes 15 tools, including analyze_screenshot, recall_memory and predict_next_action, to MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"putervision-vision-memory": {
"command": "npx",
"args": [
"-y",
"@putervision/vision-memory-mcp"
]
}
}
}
Run commandnpx -y @putervision/vision-memory-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@putervision/vision-memory-mcp1.4.2

Tools

15

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
tagsarrayNoOptional classification tags
itemsarrayNoBatch mode: array of 1–20 screenshot items to ingest/analyze. When provided, screenshot/file_path params are ignored.
trace_idstringNoOptional session_id or trace_id for correlation with state-memory-mcp
file_pathstringNoAbsolute path to a local image file (single mode). Use instead of screenshot to avoid base64 overhead
git_branchstringNoOverride the active git branch
screenshotstringNoBase64-encoded image string (single mode)
source_urlstringNoOptional app/page path or URL where captured
descriptionstringNoOptional human/agent-provided description of the screen
force_refreshbooleanNoBypass L1/L2 cache and force new ingestion
response_formatenumNoResponse verbosity. compact omits internal fields like hashes, vectors, AX trees. Default: compactcompact | full
export_detectionsbooleanNoStandardized perception bridge: export 3D observation detections for world-model-mcp
accessibility_treestringNoOptional JSON string representing the simplified AX tree

Details

From the project 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
# Global installation via npm
npm install -g @putervision/vision-memory-mcp
2. Workspace Initialization

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

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):

{
  "mcpServers": {
    "vision-memory-mcp": {
      "command": "vision-memory-mcp",
      "args": ["run"]
    }
  }
}
Alternative Options & CLI Usage Examples
# 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 projects
vision-memory-mcp init-global

# Health check dependencies, sharp bindings, and git safety
vision-memory-mcp doctor

# Run health diagnostics & aggregate metrics across all registered projects
vision-memory-mcp doctor-global

# Inspect stored visual states and metadata in terminal ASCII table
vision-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 snapshot
vision-memory-mcp snapshot save --name "v1.0-milestone"

# Ingest WebM / MP4 video recording into visual state memory timeline
vision-memory-mcp video ingest ./playwright-test.webm --category playwright_test

# Open interactive force-directed visual graph viewer in browser
vision-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

# 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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.