MCP server for persistent, searchable memory for AI agents.
io.github.isiomaC/memstack MCP Server
This MCP server provides a persistent, searchable memory layer for AI agents. It is positioned to store, retrieve, summarize, and prune memory, and references an implementation priority in a canonical roadmap. The project is open-source and includes tooling associated with both memory management and MCP registry distribution.
π οΈ Key Features
Persistent memory for AI agents
Searchable memory
Store, retrieve, summarize, and prune
π Use Cases
RAG workflows requiring stored retrieval
Agent memory management with summarization and cleanup
Persistent memory for AI agents. Claude Code and Codex share one memory per project, and your own agents get the same pipeline: store, retrieve, summarize, and prune.
Tell one agent how your project works. The other already knows. Claude Code learns a convention; a new Codex session recalls it and gets the task right:
Every session then starts with the project's key memories, and both agents save what you ask them to remember. How harness memory works.
Building your own agent?
bash
# Use MemStack in your application
npm install @memstack/core
# Give your coding agents the MemStack skill (-g: every project; omit it for this project only)
npx skills add isiomaC/memstack -g
@memstack/core is the runtime SDK; the Agent Skill teaches compatible coding agents how to integrate and operate MemStack correctly. Without -g, the skill installs into the current project (.agents/skills/, plus a .claude/skills/ link for Claude Code). Update it later with npx skills update.
The problem: AI agents forget. Every interaction starts from zero. You either stuff everything into the context window (expensive, slow, degrades output quality) or the agent has no memory of past conversations.
What MemStack does: A persistent memory pipeline that lives between your agent and the LLM. It stores every interaction, retrieves only what's relevant, summarizes old memories to save tokens, and prunes stale ones automatically. One method call, no infrastructure required.
Think of it as the open-source alternative to Mem0 β pluggable storage, bring your own LLM, zero vendor lock-in.
LLMs have context windows, not memory. The difference matters.
Approach
Problem
Stuff everything in context
Cost is O(nΒ²). 100 conversations = thousands of tokens = dollars per call. Quality degrades from "lost in the middle" effect.
Use a vector DB directly
You get similarity search. You don't get summarization, pruning, recency weighting, deduplication, or token budget management. You're building the pipeline yourself.
Use Mem0
Proprietary, cloud-only with their hosted API. You don't control where your data lives.
Use MemStack
Full pipeline. Pluggable everything. Your data, your infrastructure. Open source.
What MemStack handles that raw vector DBs don't:
Summarization β compress 100 old interactions into one paragraph, keep meaning, save tokens
Importance scoring β not all memories are equal; high-importance ones survive pruning
Deduplication β identical or near-identical memories are collapsed in context assembly
Token budget β compileContext() tells you how many tokens you're spending before the LLM call
Memory-type routing β interactions, summaries, observations treated differently at retrieval time
Auto-pruning β old, low-importance memories clean themselves up
Quick Start
Claude Code and Codex
Persistent memory across agent harnesses: what you tell Claude Code, Codex
recalls in the same project, and the reverse.
bash
npm install -g @memstack/cli @memstack/mcp better-sqlite3@^11.10.0 # MemStack never installs storage drivers for you
memstack init # choose an LLM provider and a store
memstack connect claude-code
memstack connect codex
Then, in Claude Code: "Remember that this project uses Hono." In Codex, in the
same repository: "What framework does this project use?" Codex answers Hono.
See Harness Memory for how it works.
DeepSeek provides chat completions but has no embedding API. Use the OpenAI-compatible LLM adapter with baseURL and omit the embedding adapter β retrieval falls back to keyword + recency + importance ranking. You still get the full pipeline: store, summarize, prune, and compileContext.
// 1. Store what happenedawait memstack.memory.store({
actorId: "support-bot-42",
content: "User reports login failing with error 503 on Chrome 125.",
tags: ["login", "bug", "chrome"],
importance: 0.8,
});
// 2. Later, retrieve relevant contextconst memories = await memstack.memory.retrieve({
actorId: "support-bot-42",
query: "login error",
strategy: "hybrid",
});
// 3. Assemble an LLM-ready contextconst ctx = await memstack.memory.compileContext({
actorId: "support-bot-42",
maxTokens: 2000,
});
const response = await llm.complete({
system: `You are a support bot. Here is what you remember:\n${ctx.systemPrompt}`,
user: "The user is back and still can't log in. What do you do?",
});
console.log(response.text);
// "Based on our history, the user has been experiencing 503 errors on Chrome 125..."// 4. Every 100 interactions, summarization triggers automatically.// Old interactions are compressed into a paragraph. Token costs stay flat.
Harness Memory (Claude Code & Codex)
Coding agents forget everything between sessions, and they don't share what
they learn with each other. MemStack gives Claude Code and Codex one memory
per project: a decision made with one agent is known to the other, and to
every later session.
How it works
Saving. Each agent gets five MemStack tools (memory_store,
memory_retrieve, memory_get, memory_delete, memory_stats) through
the MCP harness profile. When you say "remember thatβ¦", or the agent learns
a durable fact, decision, preference, or rule, it calls memory_store.
MemStack asks your LLM for a few topic tags, so "uses Hono" can later be
found by "which framework?". If tagging fails, the memory is still saved.
Recalling. A session-start hook loads the project's most important
memories into every new session, so the agent starts out knowing them.
During a session the agent calls memory_retrieve with plain questions.
Recall runs locally with keyword ranking (BM25 with stemming) and never
calls the LLM, so it is fast and works offline.
Scope. Memories belong to the current project. Preferences that apply
everywhere can be saved as global (scope: "global") and are recalled in
every project. One project can never read or delete another's memories.
Safety. Agents don't get bulk or destructive tools, and the LLM key stays
in ~/.memstack/config.json (readable only by you), never in agent configs.
Agents are told never to store secrets, and MemStack checks too: a memory
that contains a credential (a private key, a cloud or source-host token, a
JWT, a password in a connection string, a password = "..." assignment) is
refused before the LLM or the store sees it, and the error names the kind of
secret without repeating it. The check is pattern-based, so a secret in a
format it doesn't know will pass; MEMSTACK_SECRET_POLICY=redact stores the
memory with [REDACTED:<kind>] in place of the secret, and off disables
the check.
Commands
Command
What it does
memstack init
Choose an LLM provider (optional) and a store. Verifies the key with a real request and writes ~/.memstack/config.json. Without a key, memories are saved without topic tags and recall works the same. Non-interactive: --provider, --base-url, --model, --api-key-env <VAR>, --no-llm, --store, --path, --url, --yes.
memstack connect <claude-code|codex>
Registers MemStack with the agent. Checks the server works first, and undoes everything if a step fails. --dry-run shows the changes; --no-hooks and --no-agents-md skip those parts.
memstack disconnect <claude-code|codex>
Removes everything connect added. Your memories are kept.
memstack status
Config, storage, the current project, and what each agent has connected.
memstack doctor
Diagnoses setup problems and prints the fix for each. --live also tests the LLM key.
memstack memories [query]
Lists or searches this project's memories. --global for global ones, --delete <id> to remove one.
memstack project
Shows this repository's project ID. project pin <id> fixes it in .memstack.json; project merge <old-id> moves memories from an old ID.
What connect changes
connect changes only these entries, backs up each file first, and
disconnect restores each file exactly:
Agent
File
Change
Claude Code
~/.claude.json
A user-scope memstack MCP server, added with claude mcp add-json.
Claude Code
~/.claude/settings.json
A SessionStart hook running memstack-mcp hook session-start.
Codex
~/.codex/config.toml
A memstack MCP server, added with codex mcp add.
Codex
~/.codex/hooks.json
A SessionStart hook. Codex runs it after you approve it once with /hooks.
Codex
~/.codex/AGENTS.md
A short block between memstack:begin/memstack:end markers telling Codex to save memories with memory_store.
The registered command is the memstack-mcp you installed, run by absolute
path, so it works even when the agent starts without your shell's PATH.
Restart Claude Code, or start a new Codex session, to load it.
Projects
The project ID comes from the repository itself, with nothing stored, so it
stays the same across clones, worktrees, renamed remotes, moved folders, new
machines, and storage switches:
a pinned ID in .memstack.json at the repository root
(memstack project pin <id>; commit it to share it with your team);
otherwise, the repository's first commit;
for shallow clones, the origin remote;
for repositories without commits, the git directory, and outside git, the
folder. Memories saved before a repository's first commit move to the new
ID automatically.
A fork shares its first commit with the original repository, so on one store
the two share memories until one of them runs memstack project pin.
Storage
Any supported store works; pick it in memstack init. MemStack never installs
storage drivers: install the one you need alongside @memstack/mcp.
Store
Driver to install
Notes
sqlite
better-sqlite3@^11.10.0
Default; one local file, safe for both agents at once.
postgres
postgres@^3.4.9
Shared across machines.
redis
ioredis@^5.11.1
disk, markdown
none
Single process only; doctor warns when both agents use them.
Switching stores keeps project IDs; move memories with memstack export and
memstack import.
Troubleshooting
Run memstack doctor first; it checks the config file and its permissions,
the LLM key, the storage driver, each agent's registration, hook, and
guidance, and starts the server to confirm it answers.
"memstack-mcp is not installed" or a missing driver: run the
npm install -g β¦ command it prints.
Codex doesn't load memories at session start: approve the MemStack hook
in Codex with /hooks.
Codex doesn't save when asked: check memstack status shows the
AGENTS.md guidance as present; reconnect if not.
Memories seem missing:memstack project shows which project you are
in. Use memstack project merge <old-id> to bring memories from an old ID.
MemStack's core is a five-stage pipeline. Each stage can be used independently.
1. Store
Every agent interaction becomes a Memory with metadata that controls how it's retrieved, summarized, and pruned later.
typescript
interfaceMemory {
id: string;
actorId: string; // Who this memory belongs to (user ID, agent ID, session ID)memoryType: MemoryType; // "interaction" | "summary" | "observation" | "fact" | "reflection" | "preference" | "decision" | "instruction"content: string; // The actual textimportance: number; // 0-1 β higher = survives pruning, ranks higher in retrievalemotionalValence: number; // -1 to 1 β for tone-aware retrievaltags: string[]; // Filter by tag: "bug", "billing", "urgent", etc.embedding?: number[]; // Computed automatically if embedding adapter is configuredmetadata?: Record<string, unknown>; // Your custom fieldsexpiresAt?: Date; // Auto-pruned after this datesourceId?: string; // Link back to the originating eventcreatedAt: Date;
}
typescript
// Simple storeawait ms.memory.store({
actorId: "agent-7",
content: "Customer asked about refund policy for Q2 purchases.",
tags: ["billing", "refund"],
});
// Batch store β embeddings are batched into one API call for efficiencyawait ms.memory.storeBatch([
{ actorId: "agent-7", content: "First interaction" },
{ actorId: "agent-7", content: "Second interaction" },
{ actorId: "agent-7", content: "Third interaction" },
]);
2. Retrieve
Pull back what's relevant β by keyword, by meaning (semantic), by recency, or by importance.
typescript
const memories = await ms.memory.retrieve({
actorId: "agent-7", // Scope to one actorquery: "refund policy", // What to search forstrategy: "hybrid", // How to rank: "recent" | "important" | "semantic" | "hybrid"limit: 10, // Max resultsmemoryTypes: ["interaction"], // Only certain typestags: ["billing"], // Only certain tags
});
Strategy behavior:
Strategy
Sorts by
Requires embeddings
Best for
recent
Newest first
No
Knowing what just happened
important
Highest importance first
No
Filtering noise, keeping signal
semantic
Cosine similarity to query
Yes
"Find memories about X"
hybrid
Semantic + importance blend
Yes
Best of both worlds
No embedding adapter? semantic and hybrid fall back to keyword matching + importance sort. No API costs, just less precise.
3. Compile Context
compileContext() takes retrieval results and assembles an LLM-ready system prompt β deduplicated, sorted by recency and importance, with a token estimate so you know the cost before calling the LLM.
typescript
const ctx = await ms.memory.compileContext({
actorId: "agent-7",
maxTokens: 2000, // Budget β assembler stops when it hits thismemoryTypes: ["interaction", "summary"],
});
// ctx.systemPrompt:// ## Important Memories// - The customer has been attempting login for 3 days. (importance: 0.85)// - Refund was processed for order #4521 on Jan 12. (importance: 0.72)// // ## Recent Interactions// - Customer asked about refund policy for Q2 purchases.// - Customer reported login error 503 on Chrome 125.console.log(ctx.tokenEstimate); // ~280// Inject into your LLM callconst currentMessage = "The user is asking about their refund status.";
const response = await llm.complete({
system: ctx.systemPrompt,
user: currentMessage,
});
console.log(response.text);
compileContext() handles deduplication, token budgeting, and splits context into important-vs-recent sections. Without it, you'd be concatenating raw retrieval results and risking context-window overflow.
4. Summarize
When an actor has hundreds of interactions, retrieval gets expensive and context gets bloated. Summarization compresses old interactions into a single paragraph using the configured LLM.
typescript
const { summary, deletedCount } = await ms.memory.summarize({
actorId: "agent-7",
olderThan: newDate(Date.now() - 7 * 86400000), // Older than 7 daysskipMostRecent: 10, // Never touch the 10 most recenttargetCount: 50, // Summarize at most 50 memoriesmemoryTypes: ["interaction"],
keepOriginals: false, // Delete originals after summary
});
// summary.content:// "Over the past week, the customer reported recurring login failures (error 503)// on Chrome 125. Multiple troubleshooting attempts including cache clearing and // password reset were unsuccessful. A refund was processed for order #4521."console.log(deletedCount); // 47 β 47 interactions compressed into 1 summary memory
Auto-summarization: Set summarizationThreshold in config (default: 100). Every 100th interaction for an actor triggers summarization automatically.
Warning:keepOriginals: false deletes the summarized memories. Set keepOriginals: true to preserve them alongside the summary.
Custom summarization prompt:
typescript
const ms = newMemStack({
llm,
defaults: {
summarizationPrompt:
"You are an enterprise support memory compressor. Highlight: customer name,
product, severity, resolution status, and any open issues.",
},
});
5. Prune
Not all memories deserve to live forever. Pruning removes low-value memories to keep storage and retrieval fast.
typescript
// Remove memories older than 30 daysawait ms.memory.prune({ type: "byAge", maxAge: 30 * 86400000 });
// Keep only memories above importance 0.3await ms.memory.prune({ type: "byImportance", minImportance: 0.3 });
// Keep at most 500 memories per actorawait ms.memory.prune({ type: "byCount", maxPerActor: 500 });
// Remove specific typesawait ms.memory.prune({ type: "byType", memoryTypes: ["observation"] });
// Custom logicawait ms.memory.prune({
type: "custom",
shouldRemove: (memory) => memory.content.includes("[RESOLVED]"),
});
// Dry run first β see what would be removedconst { wouldPrune, count } = await ms.memory.dryRunPrune({
type: "byAge",
maxAge: 86400000,
});
console.log(`Would remove ${count} memories:`, wouldPrune);
Auto-prune on every process() call by setting pruneStrategy in config:
// detectUrgency and classifyIntent are your own business logic.// They could be simple keyword matchers, regex, or an LLM call.functiondetectUrgency(msg: string): number {
if (msg.match(/urgent|asap|immediately/i)) return0.9;
if (msg.match(/error|fail|broken/i)) return0.7;
return0.5;
}
functionclassifyIntent(msg: string): string[] {
consttags: string[] = [];
if (msg.match(/bill|refund|charge|payment/i)) tags.push("billing");
if (msg.match(/error|bug|fail|crash/i)) tags.push("bug");
if (msg.match(/login|password|account/i)) tags.push("account");
return tags;
}
// Every customer message becomes a memoryasyncfunctionhandleMessage(customerId: string, message: string) {
await ms.memory.store({
actorId: `customer:${customerId}`,
content: message,
importance: detectUrgency(message),
tags: classifyIntent(message),
});
// Retrieve everything relevant to this customer's historyconst ctx = await ms.memory.compileContext({
actorId: `customer:${customerId}`,
maxTokens: 1500,
});
const response = await llm.complete({
system: `You are a support agent. Customer history:\n${ctx.systemPrompt}`,
user: message,
});
return response.text;
}
// Every 100th interaction, old history auto-compresses.// A customer with 10,000 messages still fits in a $0.02 LLM call.
RAG Pipeline
typescript
// Suppose you have documents from your knowledge baseconst documents = [
{ text: "Authentication uses JWT tokens with 15-minute expiry.", url: "/docs/auth", section: "security" },
{ text: "Refunds are processed within 5-10 business days.", url: "/docs/billing", section: "billing" },
];
// Index documents as observation memoriesfor (const doc of documents) {
await ms.memory.store({
actorId: "knowledge-base",
content: doc.text,
memoryType: "observation",
metadata: { source: doc.url, section: doc.section },
});
}
// Query with semantic searchconst relevantDocs = await ms.memory.retrieve({
actorId: "knowledge-base",
query: "How does authentication work?",
strategy: "semantic",
limit: 5,
});
const ctx = await ms.memory.compileContext({
actorId: "knowledge-base",
memoryTypes: ["observation"],
});
// Prompt the LLM with retrieved contextconst answer = await llm.complete({
system: `Answer using only these documents:\n${ctx.systemPrompt}`,
user: "How does authentication work?",
});
Multi-User Chatbot
typescript
// Each user gets their own memory spaceasyncfunctionchat(userId: string, message: string) {
await ms.memory.store({
actorId: userId,
content: message,
});
const ctx = await ms.memory.compileContext({
actorId: userId,
maxTokens: 1000,
});
return llm.complete({
system: `You are a friendly assistant. Conversation history with this user:\n${ctx.systemPrompt}`,
user: message,
});
}
// Get statsconst total = await ms.memory.count();
const userCount = await ms.memory.count({ actorId: "user-42" });
Memory Type Reference
Type
Purpose
Example
interaction
Default. Direct exchanges between agent and user/other agent.
"User asked about billing."
summary
Compressed collection of old interactions. Created by summarize().
"Over 3 weeks, user reported 5 login failures..."
observation
Passive knowledge β facts, documents, things the agent knows but didn't interact with.
"Company refund policy is 30 days from purchase."
fact
Verified knowledge β discrete truths the agent has confirmed.
"The user's subscription tier is Enterprise."
reflection
Self-generated insight β the agent thinking about its own experiences.
"I tend to over-explain billing policies β should be more concise."
preference
How the user likes things done.
"Prefer small pull requests with one concern each."
decision
A choice made, ideally with its reason.
"Chose Hono over Express for edge runtime support."
instruction
A standing rule to follow.
"Never commit directly to main."
Types control retrieval behavior β compileContext() treats interaction and summary differently from observation. Use types to separate "what happened" from "what I know."
Use recent for chatbots, ongoing conversations, anything time-sensitive
Use important for long-running agents where signal-to-noise matters
Use semantic for RAG, document search, knowledge base queries
Use hybrid for most agent memory β it balances meaning with significance
Keyword recall on any storage adapter
LexicalRetriever answers natural questions without embeddings or an LLM
call, and behaves the same on every storage adapter. It loads the memories
in the given actors through retrieve(), then ranks them in MemStack with
BM25 over content and tags, with stemming and prefix matching. When nothing
matches, it returns the most important memories instead.
typescript
import { LexicalRetriever } from"@memstack/core";
const retriever = newLexicalRetriever(storage);
const { hits, fallback } = await retriever.recall({
actorIds: ["project:abc", "global"], // Searched togetherquery: "What framework does this project use?",
limit: 10, // Max resultsmaxChars: 8000, // Max total content; the top hit is always returned
});
Up to 2,000 memories per actor are ranked (candidateLimit). Only returned
memories are marked as accessed.
Embeddings
Embeddings power semantic search. They're optional β without them, retrieval uses keyword matching.
With embeddings vs Without embeddings
With embeddings (embedding adapter configured):
typescript
import { MemStack, OpenAILLMAdapter, OpenAIEmbeddingAdapter, InMemoryStorageAdapter } from"@memstack/core";
const ms = newMemStack({
llm: newOpenAILLMAdapter({ apiKey: process.env.OPENAI_API_KEY! }),
embedding: newOpenAIEmbeddingAdapter({ apiKey: process.env.OPENAI_API_KEY! }),
storage: newInMemoryStorageAdapter(),
});
// store() computes a 1536-dim vector automaticallyawait ms.memory.store({
actorId: "agent-7",
content: "Customer asked about refund policy for Q2 purchases.",
});
// retrieve() with "semantic" or "hybrid" uses cosine similarity// Query: "refund" finds the refund policy memory even though the word "refund"// appears differently across stored memories.const results = await ms.memory.retrieve({
actorId: "agent-7",
query: "how do I get my money back",
strategy: "semantic",
});
// Matches "Customer asked about refund policy" β semantic match, not keyword match.
Without embeddings (no embedding adapter):
typescript
const ms = newMemStack({
llm: newOpenAILLMAdapter({ apiKey: process.env.OPENAI_API_KEY! }),
storage: newInMemoryStorageAdapter(),
// no embedding adapter
});
// store() works identically, just no vector computedawait ms.memory.store({
actorId: "agent-7",
content: "Customer asked about refund policy for Q2 purchases.",
});
// retrieve() with "semantic" or "hybrid" falls back to keyword matching// plus importance/recency sorting. No API costs, no setup required.const results = await ms.memory.retrieve({
actorId: "agent-7",
query: "refund",
strategy: "hybrid", // falls back to keyword + importance
});
// Still works β finds "refund" via substring match. Less precise for// paraphrased queries ("money back" won't match "refund").
Batch embedding:storeBatch() sends all texts in one embedding API call, reducing cost and latency.
typescript
// Disable auto-embedding if you only need keyword searchconst ms = newMemStack({
llm,
embedding: newOpenAIEmbeddingAdapter({ apiKey }),
defaults: { embedOnStore: false },
});
Vector dimensions and model compatibility
Different embedding models produce vectors of different lengths. Cosine similarity only works between vectors of the same dimension. If you change embedding models, existing vectors become incompatible β they can't be compared to new ones.
Adapter
Default model
Dimensions
OpenAIEmbeddingAdapter
text-embedding-3-small
1536
OpenAIEmbeddingAdapter
text-embedding-3-large
3072
CohereEmbeddingAdapter
embed-english-v3.0
1024
CohereEmbeddingAdapter
embed-english-light-v3.0
384
CohereEmbeddingAdapter
embed-english-v2.0
4096
CohereEmbeddingAdapter
embed-multilingual-v3.0
1024
What happens if dimensions don't match: If you store memories with one model (e.g., 1536 dims) then switch to another model (e.g., 1024 dims), the storage adapter receives query vectors and stored vectors of different lengths. Cosine similarity between vectors of different dimensions is undefined β results depend on the storage backend's behavior. Most will either error, return empty results, or produce meaningless scores.
Recommendation: Pick one embedding model per storage instance and stick with it. If you need to switch models, create a new storage instance and re-embed from scratch.
DeepSeek users: DeepSeek has no embeddings API. If you use DeepSeek as your LLM, you must either:
Omit the embedding adapter and use "recent" or "important" retrieval strategies (no API costs, less precise)
Pair DeepSeek with a separate embedding provider (e.g., OpenAI for embeddings, DeepSeek for chat)
Adapters
MemStack is provider-agnostic. Every boundary is an interface β bring your own LLM, embedding model, and storage backend.
LLM Adapters
Used by summarize() and compileContext(). Ships with OpenAI, Anthropic, Ollama, and Groq built-in β and via baseURL, the OpenAI adapter works with any OpenAI-compatible API (DeepSeek, Mistral, Gemini, Together AI, Perplexity, Fireworks, xAI, and dozens more).
Used by semantic retrieval. Ships with OpenAI and Cohere built-in β and via baseURL, the OpenAI adapter works with any OpenAI-compatible embedding API (Together AI, Voyage AI, Jina, Nomic, and more).
MemStack contains 18 storage-adapter implementations. Twelve are exported from @memstack/core; six remain experimental source implementations. Core has no runtime dependencies, and database clients are injected by callers.
Support levels:
Production-ready means exported from the public package, covered by unit tests, and supported as part of the public API.
Real-service E2E verified means the adapter also passes against its actual database implementation in pnpm test:e2e.
Mock-tested means unit coverage uses an injected fake client rather than a live cloud service.
Experimental means implemented in source but not exported from the published package.
Public package exports
Built-in (zero external deps):
Adapter
Backend
Use case
InMemoryStorageAdapter
In-memory Map
Testing, prototyping
DiskStorageAdapter
Local JSON files
Simple local persistence
MarkdownStorageAdapter
Append-only .md files
Human-readable, git-diffable, debug-friendly
HybridStorageAdapter
Compose any two StorageProviders
Cache + durable, edge + durable
Relational / SQL:
Adapter
Backend
Vector search
PostgresStorageAdapter
PostgreSQL + pgvector
HNSW native
SQLiteStorageAdapter
SQLite (better-sqlite3)
Cosine in-memory
Vector databases:
Adapter
Backend
QdrantStorageAdapter
Qdrant
WeaviateStorageAdapter
Weaviate
LanceDBStorageAdapter
LanceDB
MongoDBStorageAdapter
MongoDB Atlas Vector Search
Cache / KV:
Adapter
Backend
RedisStorageAdapter
Redis (ioredis)
Graph:
Adapter
Backend
Neo4jStorageAdapter
Neo4j
Experimental (mock-tested or missing an optional E2E capability)
These implementations are available to source contributors but are not part of the published package API.
Adapter
Backend
Blocker
TursoStorageAdapter
Turso (libsql)
Cloud-only (needs Turso account)
ChromaStorageAdapter
ChromaDB
Embedding function dependency
PineconeStorageAdapter
Pinecone
Cloud-only (needs API key)
UpstashStorageAdapter
Upstash Redis + Vector
Cloud-only (needs API key)
Mem0StorageAdapter
Mem0 OSS or Cloud
Cloud-only (needs API key)
ZepStorageAdapter
Zep Cloud or CE
Cloud-only (needs API key)
Live cloud compatibility remains unverified for Pinecone, Upstash, Mem0, Zep, and Turso. Chroma's real-client E2E suite is skipped when its optional default embedding function is unavailable. LLM and embedding-provider tests use mocks; live-provider testing is opt-in and is not part of CI.
import { MemStack } from"@memstack/core";
const ms = newMemStack({
llm: LLMProvider, // Required β for summarizationembedding?: EmbeddingProvider, // Optional β for semantic searchstorage?: StorageProvider, // Optional β defaults to InMemoryStorageAdapterdefaults?: {
summarizationThreshold?: number, // Auto-summarize every N process() calls. Default: 100embedOnStore?: boolean, // Auto-embed on store(). Default: truepruneStrategy?: PruneStrategy, // Auto-prune during process() (throttled). Default: disabledpruneInterval?: number, // Run auto-prune every N process() calls. Default: 100autoImportance?: boolean, // LLM-score importance in process() when not provided. Default: falseautoTags?: boolean, // LLM-extract tags in process() when not provided. Default: falsesummarizationPrompt?: string, // Custom prompt for the summarizer
},
hooks?: {
onMemoryStored?: (memory: Memory) =>void;
onMemoryPruned?: (ids: string[]) =>void;
onSummaryCreated?: (summary: Memory, deletedCount: number) =>void;
onError?: (error: Error, context: string) =>void;
},
});
Auto-behaviors run inside process(), not store().process() tracks a
per-actor call count: summarization fires every summarizationThreshold calls,
and pruning fires every pruneInterval calls (when pruneStrategy is set).
store() is the low-level write and never triggers these.
Each memory's original createdAt is preserved on import, so export β import is a lossless round-trip β safe for backups and cross-backend migration (e.g. disk β Postgres). All storage adapters honor a createdAt supplied on store()/storeBatch(); when omitted, they default to the current time.
remember asks the LLM for topic tags (disable with autoTags: false); every
other method makes no LLM call. recall uses LexicalRetriever.
Configuration
typescript
const ms = newMemStack({
llm: newOpenAILLMAdapter({ apiKey: "..." }),
// Defaults control auto-behavior (all applied during process())defaults: {
summarizationThreshold: 50, // Summarize every 50 process() calls (default: 100)embedOnStore: false, // Don't auto-embed β saves API costspruneStrategy: { // Auto-clean during process(), throttled by pruneIntervaltype: "byAge",
maxAge: 90 * 86400000, // 90 days
},
pruneInterval: 100, // Run the prune check every 100 process() calls (default: 100)autoImportance: true, // Let the LLM score importance when you don't pass oneautoTags: true, // Let the LLM extract tags when you don't pass any
},
// Hooks for observabilityhooks: {
onMemoryStored: (m) => logger.debug("memory:stored", { id: m.id, actor: m.actorId }),
onMemoryPruned: (ids) => logger.info("memory:pruned", { count: ids.length }),
onSummaryCreated: (summary, n) => logger.info("memory:summarized", { count: n }),
onError: (err, context) => logger.error("memory:error", { context, message: err.message }),
},
});
Harness configuration file
The CLI and the MCP harness profile read ~/.memstack/config.json (or
$MEMSTACK_HOME/config.json), which memstack init writes with permissions
readable only by you:
Environment variables override the file one section at a time: any LLM
variable (OPENAI_API_KEY, ANTHROPIC_API_KEY, MEMSTACK_OPENAI_BASE_URL,
MEMSTACK_LLM_MODEL) replaces the whole llm section, and MEMSTACK_STORAGE
replaces the whole storage section, so a key is never sent to another
provider's URL.
Advanced Usage
Custom Storage
Implement StorageProvider for any database. The interface is 9 methods. See the reference section above for the full contract.
Optional members, none of them required:
capabilities: { multiProcess?, textSearch? } declares whether several
processes can share the store safely and whether search() is native.
search(query) provides native full-text search. LexicalRetriever uses
it when textSearch is declared and ranks memories itself otherwise.
retrieve() should honor touch: false by returning memories without
marking them as accessed.
SQLiteStorageAdapter enables WAL and a 5-second busy timeout so several
processes can share one database file. Set walMode: false or
busyTimeoutMs to change this.
Custom LLM / Embedding
Implement LLMProvider or EmbeddingProvider for any service:
MemStack includes a Val benchmark pack for retrieval-only evidence-session recall on the public, cleaned LongMemEval-S split. The runner stores each question's sessions through MemStack's harness memory API, uses the local lexical retriever and in-memory storage, and does not call an answer model or judge. Secret scanning is disabled only for this benchmark's public corpus in the temporary in-memory store; do not use the runner with private data. Its recall metrics are not end-to-end QA accuracy and are not directly comparable to the official LongMemEval QA leaderboard. The published dataset is public, not a hidden evaluation set.
The dataset is not included in this repository. Validate the pack, then fetch only its explicitly named split with Val:
bash
val benchmark validate benchmarks/longmemeval/manifest.json
val benchmark fetch benchmarks/longmemeval/manifest.json --split public-evaluation
Val prints the SHA-256-addressed cache path. Pass it to the runner; --limit is a partial diagnostic run and must not be reported as the full benchmark:
The runner rechecks the exact declared size and SHA-256 before reading the file. It streams the JSON dataset, evaluates the default K values 1, 3, 5, and 10, excludes abstention questions marked with the upstream _abs question-ID suffix, and prints macro/micro evidence-session recall, question hit rate, and median/p95 retrieval latency. The upstream LongMemEval attribution and license are recorded in the manifest; this pack is not an official LongMemEval result.
Development
Setup & Tests
bash
git clone https://github.com/isiomaC/memstack.git
cd memstack
pnpm install
pnpm test# 407 core tests, no external services needed
pnpm test:packages # 78 package tests after dependency-ordered builds
pnpm test:e2e # 80 pass, 1 optional Chroma skip (requires Docker services)
pnpm test:e2e:run # Start services, run E2E once, preserve failure logs, clean up
pnpm smoke:artifacts # Built core, CLI, MCP, and server black-box checks
pnpm smoke:packages # Pack and install publishable tarballs in a clean project
pnpm smoke:docker # Build and exercise the server image
pnpm verify # Complete local verification pipeline
pnpm test:watch # Watch core tests
pnpm build:all # Build core and all workspace packages
pnpm check:all # Type-check core and all workspace packages
pnpm check:benchmark # Type-check the LongMemEval benchmark runner
CI exposes a stable verification job. Configure that job as a required status check in GitHub branch protection for main.
Debugging
Use hooks for observability β MemStack has no built-in logging: