"A tool or software for modeling memory systems or memory management" matching MCP servers:

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

Persistent project memory for coding agents, kept in a local SQLite store with FTS5 search: search and list memories by topic, read one with its history, add a fact, show the store's statistics, and read or regenerate the PROGRESS.md handoff. Pure standard-library Python; no network.

A persistent, project-scoped memory layer for AI coding agents, providing 39 tools for capturing, searching, deduplicating, relating, and maintaining memory records across long-running coding sessions.

A local MCP server that gives AI assistants persistent long-term memory using a biological neural architecture with cortex, synapses, and hippocampus.

Hand a project over — to your next session, to Cursor/Codex/Gemini, to your successor — with the reasons attached. Local-first memory MCP for coding agents: decisions re-injected before the agent acts, drift detection across every project you run. One SQLite file, nothing leaves your machine.

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.

Hosted memory for AI agents that learns from outcomes, with shared rooms. One key across Claude, Cursor & ChatGPT.

Enables multiple AI agents on one machine to write, search, fetch, link, and give feedback on a shared local store of Markdown-backed facts, preferences, and conventions that persists across sessions. Memories gain confidence as different hosts confirm their use and can be distilled into denser ones, so agents stop re-discovering the same context.

MCP server that exposes agent-memory-daemon to any MCP-compatible client — Kiro (CLI & IDE), Claude Desktop, Cursor, and others. The daemon does the thinking (consolidation + extraction); this server is a thin filesystem bridge so agents can read, append, and search memory through the Model Context Protocol.

Long-term memory for AI coding agents, stored as a tree of plain local files. Agents search it before answering and save what lasts; changed facts are kept as history and flagged as outdated.

Provides persistent local memory for any MCP-compatible AI agent, enabling agents to store, search, recall, forget, export, and manage preferences, rules, and facts with zero dependencies, no cloud, and no API keys.

MARM MCP provides persistent memory and structured session context beneath any AI tool, so your agents learn, remember, and collaborate across all your workflows.

A stateless MCP server that gives coding agents a curated entry point to shared memory, orchestrating Hindsight (facts) and LightRAG (corpora) for automatic routing, URL ingestion, and consistency tooling.

Local-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware and secret-safe.

Provides AI agents with persistent, long-term memory via OKF-formatted markdown and SQLite indexing, enabling stateful storage, retrieval, and search across sessions.

A vendor-agnostic cognitive persistence layer for AI agents. Eliminate the "repetition tax" by transporting your context, preferences, and history across sessions. Features an auto-adaptation engine that syncs global instructions to ensure operational cohesion and optimize token usage across any LLM or multi-agent workflow.

Wraps a dependency-free memory lifecycle engine as six read-only MCP tools, letting any agent extract facts with pure regex, score signals, compute Ebbinghaus decay and archival judgments, and simulate a full five-stage dream cycle for long-term memory growth. Runs over stdio or streamable HTTP with no API key, storing no caller data.

Enables Claude to store and retrieve memories as 1024-dimensional embeddings in a local SQLite database using the Model Context Protocol.

Persistent long-term memory for MCP clients. Store and recall semantic facts, episodic events, and task state with vector-based relevance search. Write what matters, retrieve what's needed — memory that persists across sessions and agents, backed by a local SQLite store with optional embeddings for meaning-based lookup. Simple file-based storage, no external services required.

Enables AI tools and agents to share a persistent memory space, so a decision, task, or encrypted secret saved in one client can be searched, recalled, and handed off from another. It also tracks goals day by day, moves unfinished work between sessions, and keeps exports, trash recovery, and per-account isolation under the user's control.