One shared memory for every AI you use, in plain Markdown files you own.
Persistent memory for AI coding tools via MCP. Remembers across sessions and machines.
iOS leak/perf debugging via MCP: memgraph cycles, .trace analysis, SourceKit-LSP bridging.
MCP server for CarsXE vehicle data: VIN, specs, history, images, recalls, and OBD codes.
Permanent blockchain memory for AI agents.
Home appliance MCP: CPSC recall lookup, lifespan, maintenance, repair-or-replace, energy cost.
Individual-analyst context layer: recall, remember, and reconcile your data and engineering context.
ContextStream MCP server for code context, memory, search, and AI tools.
US consumer product recalls from the CPSC — hazards, remedies, and affected products.
Decode VINs, search recalls, complaints, crash ratings, and investigations.
Query FDA data on drugs, food, devices, and recalls via openFDA. STDIO or Streamable HTTP.
Offline agentic memory: remember/recall/relate/forget/why over a fused vector+graph+columnar engine.
An MCP server that gives LLMs persistent, searchable semantic memory.
Detects when workspace/system_memory/heartbeats.json mtime exceeds the silence threshold (default...
Self-maintaining knowledge vault: figure-level search, auto-wikilinks, and memory compression.
One searchable memory of your Claude.ai chats and Claude Code sessions, served over MCP.
Local-first, source-cited memory for AI agents with proposal review, failure memory, and MCP tools.
Associative key-graph memory for LLM agents — recall by association, not vector similarity.
PMLL Memory MCP — persistent KV context memory and Q-promise deduplication.
Procedure verification for AR/XR with memory, visual sessions, and DPO trajectory export.
Persistent, expiring, importance-graded sticky notes for Claude Code.
Email, EU VAT, IBAN, and domain validation plus evidence-backed U.S. CPSC recall screening.
File-first, local-first MCP memory for AI coding assistants: Markdown + YAML, no vector DB.
Essential MCP server: HTTP, web search, downloads, Wolfram|Alpha, shell, JS, file I/O, memory.
About Memory MCP servers
Memory servers solve the blank-slate problem: every new conversation starts without the context of the last one. They store facts, preferences and documents in a form the agent can recall, from simple local note stores to knowledge graphs and vector databases such as Chroma, Qdrant, Pinecone and Weaviate. Some index your own files; others manage a shared memory across tools and sessions.
Decide where memories live before you decide which server to use. Local servers keep everything on your machine, which is ideal for personal and sensitive context; hosted servers make memory available to every client you use. Look for servers that let you inspect, edit and delete what has been stored, and that separate retrieval tools from write tools.