Skip to main content

​
What is MemContext?

MemContext is memory infrastructure for AI agents and applications. It provides a REST API and MCP server that allow AI systems to:
  • Save durable user and project knowledge across sessions
  • Isolate app users and tenants with hard memory containers via scope
  • Search memories with natural-language questions and exact terms
  • Evolve memories over time with automatic version chains
  • Profile users with pre-aggregated context from their memory
  • Ingest workspace documents through Context Vault for RAG-style AI context

​
Who is it for?

MemContext serves three primary use cases:
  1. Coding assistants that need stable preferences, decisions, and project context across sessions
  2. Product applications that need evolving memory for content generation, support, onboarding, or personalization
  3. Workspace AI tools that need to retrieve source passages and extracted facts from files, docs, and URLs

​
The Three Retrieval Modes

MemContext supports three ways to retrieve context:
ModeUse it forReturns
MemoriesDurable facts, preferences, and decisionsAtomic memories
Document chunksRAG over PDFs, Markdown, docs, and URLsSource passages with citations
Hybrid workspaceProduction AI tools that need bothDocument chunks plus memory facts
This gives your app a clear choice. Use memories when you need concise facts. Use document chunks when you need source text. Use hybrid when you want the AI layer to receive both precise passages and clean extracted knowledge.

​
Core primitives

ConceptDescription
ScopeHard isolation boundary for app users or tenants (e.g. user_123)
CategoryBroad memory type: preference, fact, decision, or context
ProjectSoft grouping/filter inside the selected scope or default memory area
Version chainsMemories can supersede old memories without losing history
Hybrid searchNatural-language search that also handles exact names, tools, and decisions
MCP toolsAI assistants can save and search memory directly via Model Context Protocol

​
Why it exists

Simple retrieval is not enough for memory. Memory needs:
  • Updates when reality changes
  • History when strategy evolves
  • Exact-match retrieval for product names, org names, and decisions
  • Lightweight APIs other tools can build on

​
Next steps

Quickstart

Make your first API and MCP calls in under 2 minutes.

How It Works

Understand how MemContext saves, updates, and retrieves memory.

API Reference

Full endpoint documentation with interactive examples.

MCP Setup

Connect MemContext to Claude Desktop, Cursor, or any MCP client.