memory-lancedb-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORY_DB_PATH | No | LanceDB storage directory | |
| EMBEDDING_MODEL | No | Model name (default: text-embedding-3-small) | |
| EMBEDDING_API_KEY | Yes | API key for embedding provider | |
| EMBEDDING_BASE_URL | No | Custom base URL for non-OpenAI providers | |
| MEMORY_LANCEDB_CONFIG | No | Path to JSON config file |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_recallA | Search through long-term memories using hybrid retrieval (vector + keyword search). Use when you need context about user preferences, past decisions, or previously discussed topics. |
| memory_storeB | Save important information in long-term memory. Use for preferences, facts, decisions, and other notable information. |
| memory_forgetB | Delete specific memories. Supports both search-based and direct ID-based deletion. |
| memory_updateA | Update an existing memory. For preferences/entities, changing text creates a new version (supersede) to preserve history. Metadata-only changes (importance, category) update in-place. |
| memory_mergeA | Merge two related memories into one. Creates a new merged memory and invalidates both originals. Use when duplicate or fragmented memories cover the same topic. |
| memory_historyA | Trace the version history of a memory through its supersede/merge chain. Shows how a memory evolved over time. |
| memory_visualizeA | Generate an interactive HTML visualization of the memory graph. Shows semantic clusters, similarity edges, duplicate detection, importance distribution, and growth timeline. Returns the HTML as text or writes it to a file path. |
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 7 tools
Each tool maps to a distinct memory operation: search, store, delete, update, merge, history, and visualize. Boundaries are clear, with well-differentiated pairs like update vs merge and recall vs history.
All tools follow a consistent memory_<verb> snake_case pattern with predictable verbs. No mixing of conventions or ambiguous naming.
Seven tools is well-scoped for a long-term memory management server. Each tool earns its place without redundancy.
The surface covers create, read, update, delete, merge, history, and visualization. However, there is no explicit list-all or get-by-ID tool, though recall search can work around this minor gap.