MCP-Memory-LanceDB-Pro
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLM_MODEL | No | LLM model for extraction | gpt-4o-mini |
| LLM_API_KEY | No | LLM API key for smart extraction | |
| JINA_API_KEY | Yes | Jina AI API key for embeddings | |
| LLM_BASE_URL | No | LLM API endpoint | https://api.openai.com/v1 |
| RERANK_MODEL | No | Reranker model name | jina-reranker-v3 |
| MEMORY_DB_PATH | No | LanceDB database path | ~/.claude/memory-lancedb |
| RERANK_API_KEY | No | Reranker API key | |
| RERANK_ENDPOINT | No | Reranker API endpoint | https://api.jina.ai/v1/rerank |
| RERANK_PROVIDER | No | Reranker provider: jina, siliconflow, voyage, pinecone | jina |
| MEMORY_DEFAULT_SCOPE | No | Default memory scope | agent:primary |
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 long-term memories using hybrid retrieval (vector similarity + BM25 full-text + cross-encoder reranking). Returns semantically relevant memories ranked by quality. |
| memory_storeA | Save important information to long-term vector memory. Auto-deduplicates and filters noise. Use for decisions, preferences, facts, project context — anything worth remembering across sessions. |
| memory_forgetB | Delete a memory by ID or search query. |
| memory_updateA | Update an existing memory (text, importance, or category). |
| memory_statsB | Memory usage statistics — total count, by scope, by category. |
| memory_listC | List recent memories, optionally filtered. |
| memory_extractA | Smart extraction: use LLM to analyze conversation text and automatically extract important memories (preferences, decisions, facts, entities, events, patterns). This is the equivalent of autoCapture — call it at the end of important conversations. |
| memory_decayA | Run the intelligent forgetting engine — removes low-quality, outdated memories based on Weibull decay model. Call periodically (e.g., once per session) to keep memory clean. |
| self_improvement_logA | Log structured learning or error entries into .learnings/ directory for governance and later distillation. Use when: (1) a command/tool fails, (2) user corrects you, (3) you discover a knowledge gap, (4) you find a better approach. |
| self_improvement_reviewA | Summarize governance backlog from .learnings/ files — pending, high-priority, and promoted counts. |
| self_improvement_extract_skillB | Create a new skill scaffold from a learning entry and mark it as promoted. |
| memory_reflectB | Run the reflection pipeline — analyze conversation text, extract invariant rules and derived knowledge, store as reflection memories. This is the equivalent of the memory-lancedb-pro reflection system. |
| memory_bulk_deleteB | Bulk delete memories by scope, category, or age. |
| memory_migrateB | Migrate memories from legacy memory-lancedb format to current format. |
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 14 tools
Each tool has a clearly distinct purpose: memory operations (store, list, recall, update, forget, etc.) and self-improvement logging are separate concerns. No ambiguity between tools.
All tools follow a consistent snake_case pattern with `memory_` or `self_improvement_` prefix, making predictable verb/noun structure throughout.
14 tools is well-scoped for a memory management server, covering core operations and advanced features like decay and reflection without being excessive.
CRUD operations are fully covered, plus advanced features (decay, reflection, migration, statistics) and self-improvement logging. No obvious gaps for the domain.