"Information about Memory" matching MCP servers:

A persistent memory implementation using a local knowledge graph that lets Claude remember information about users across conversations.

MCP server exposing memory search, index, and stats tools for agents, with honesty guards to prevent re-litigation of settled decisions.

Lets AI clients store, retrieve, update, and forget long-term facts in a local SQLite database with deterministic lexical search, sharing the same memory across multiple clients without relying on model APIs or embedding services.

Embedded, local-first agent memory: facts extracted into a per-namespace SQLite file (vec0 + FTS5) with hybrid retrieval and point-in-time (time-travel) queries. ADD-only history over stdio — no server process, no cloud dependency.

MCP server providing persistent memory for AI applications, enabling Claude to store and recall memories with hybrid search and knowledge graph.

Gives every AI agent working in a repository a shared, persistent knowledge graph stored in a plain JSONL file, with each entity, relation, and observation tagged with the date and agent that added it. Provides tools and prompts for searching, editing, renaming, merging, cleaning up, and exporting that memory, and keeps it locked to the repository that owns it.

Exposes tools that let an agent search a local Markdown-based memory store, fetch full cards by id, write new knowledge cards that are indexed immediately, and inspect or rebuild the SQLite index. All retrieval runs locally over Chinese-friendly full-text search with graded exact/prefix matching, so agents without a memory system can recall prior notes while existing Markdown files stay read-only.

Enables LLM agents to use associative memory with key/value graph-based retrieval, supporting multi-hop traversal and human-like associative leaps beyond embedding similarity.

An MCP server that gives agents persistent memory with namespaced facts, tags, full-text search, and TTL expiry, all running locally on SQLite with zero external dependencies.

Provides persistent memory for AI agents using hybrid search (vector embeddings + BM25) with neural reranking, enabling storage and retrieval of insights, debugging solutions, and patterns across coding sessions.

An MCP server that provides persistent memory capabilities for AI agents using Mem0, enabling storage, search, and management of contextual information across conversations with support for multiple backends and LLM providers.

A tool for detecting and cleaning Java memory shells via local or SSH remote execution. It enables AI agents to scan Java processes, analyze suspicious class code, and safely remove memory shells after user confirmation.

Local-first persistent memory for coding agents and MCP clients. It keeps important project context across sessions and reduces wasted tokens by retrieving only relevant memories instead of replaying unnecessary history.

Local-first agent memory & knowledge service: hybrid retrieval (vector + BM25/RRF) + memory governance (decay, dedup, freshness), REST + MCP dual protocol, fully offline without LLM. Python.

Project Memory stores decisions, evidence, outcomes and reviewed lessons in local SQLite. Assistants retrieve bounded context through three MCP tools. People follow and plan work in a live workspace with an overview, sprint board, decision history, readable documents, skills and project maps. Offline exports remain available.

Serves UltraRAG memory to agents over stdio MCP, providing project-local and per-user global memory. It lets agents read and append standing memory and daily dialogue rounds in UltraRAG's format, with an optional browser view.

Enables persistent session memory for LLMs by trust-scoring and injecting verified context between conversations.

Local-first memory engine for AI-agent teams: private/team/project ACL, associative recall, and federated sync across nodes. One SQLite file, no LLM required.

A persistent, project-scoped memory layer for AI agents, supporting hybrid retrieval (vector, keyword, and tag matching) and sharing across different MCP clients like Claude Code, Qoder, or Cursor.

A different approach from typical persistent-memory MCPs. Instead of a local SQLite + embeddings store, the memory lives as plain files in a .ai-memory/ directory you commit to your repo (facts.jsonl, decisions/\*.md, gotchas.md). Git is the sync layer — what one Claude/Cursor/Cline learns about a repo, the next session (or a teammate's agent) picks up automatically. 5 MCP tools: get_rep