memvid-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMVID_PATH | No | Path to the memvid binary | memvid |
| MEMVID_TIMEOUT | No | Default command timeout (ms) | 120000 |
| MEMVID_VERBOSE | No | Set to 1 for verbose logging | 0 |
| MEMVID_LOG_LEVEL | No | Log level: debug, info, warning, error | warning |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memvid_createB | Create a new .mv2 memory file |
| memvid_openB | Open and display information about a memory file |
| memvid_statsB | Show statistics for a memory file |
| memvid_verifyB | Verify integrity of a memory file |
| memvid_doctorA | Diagnose and repair a memory file |
| memvid_putB | Add content to a memory file from a file or directory |
| memvid_put_manyA | Batch add multiple files from a directory with progress tracking |
| memvid_viewB | View content of a specific frame |
| memvid_updateB | Update content of a specific frame |
| memvid_deleteA | Delete a specific frame |
| memvid_correctB | Correct/amend content of a frame (creates correction record) |
| memvid_api_fetchB | Fetch content from a URL and add to memory |
| memvid_findB | Search in a memory file using hybrid, lexical, or vector search |
| memvid_vec_searchB | Vector-only similarity search (semantic search) |
| memvid_askB | Ask a question using RAG (Retrieval-Augmented Generation) |
| memvid_timelineB | Show chronological timeline of frames |
| memvid_whenB | Temporal search - find when something was mentioned |
| memvid_auditB | Generate an audit report with sources and citations |
| memvid_debug_segmentB | Debug segment information (internal structure) |
| memvid_exportB | Export memory data to JSON, CSV, or JSONL format |
| memvid_tablesB | List internal tables and structures |
| memvid_schemaB | Schema operations - infer or show schema summary |
| memvid_modelsB | List available embedding models |
| memvid_enrichB | Run NER (Named Entity Recognition) enrichment to extract entities |
| memvid_memoriesB | Memory card operations - list, stats, or filter by entity |
| memvid_stateB | State management - show current memory state |
| memvid_factsB | Fact extraction - list facts or extract from frame |
| memvid_followC | Follow entity relationships in the knowledge graph |
| memvid_whoB | Entity lookup - find information about an entity |
| memvid_sessionB | Session management - list, start, stop, or replay sessions |
| memvid_bindingB | Memory binding operations - show or unbind |
| memvid_statusB | Show system status (version, NER model status) |
| memvid_sketchC | Sketch operations (SimHash) - build or show stats |
| memvid_nudgeC | Nudge operations - trigger background processing |
| memvid_lockB | Encrypt a memory file (creates .mv2e encrypted file) |
| memvid_unlockB | Decrypt an encrypted memory file |
| memvid_process_queueB | Process pending operations queue |
| memvid_verify_single_fileB | Verify integrity of a single frame |
| memvid_configA | Show current configuration (embedder settings, paths) |
| memvid_versionA | Print memvid version information |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 40 tools
Most tools have distinct purposes, but there is some overlap that could cause confusion. For example, memvid_find and memvid_vec_search both handle search operations with different methods, and memvid_verify and memvid_verify_single_file are similar in function but differ in scope. The descriptions help clarify, but agents might misselect between closely related tools.
All tool names follow a consistent snake_case pattern with a 'memvid_' prefix, such as memvid_fetch, memvid_ask, and memvid_audit. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 40 tools, the count is excessive for a memory management server, making it feel heavy and potentially overwhelming. A more focused set of 10-20 tools would be more appropriate for this domain, as many operations could be consolidated or simplified.
The tool set provides comprehensive coverage for memory file operations, including creation, reading, updating, deletion, search, enrichment, export, and management tasks like encryption and diagnostics. There are no obvious gaps, and it supports full CRUD/lifecycle workflows for the domain.