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

Provides live wait times and office details for all 60 Oregon DMV field offices by scraping the ODOT website, with no authentication required.

Provides persistent memory for AI assistants via MCP, enabling them to store and recall facts, preferences, and tasks across conversations using either local file storage or a cloud backend with semantic search.

An MCP server that lets users capture quick phone thoughts via Android and later query them from AI assistants like Grok or Claude, functioning as a simple task memory store without notifications or geolocation.

Provides persistent memory for AgentChat agents with swim-lane summarization and self-evolving persona, enabling context management and persona mining across conversations.

A fully local persistent memory layer for LLM coding agents (Claude Code, Codex, Gemini CLI, OpenCode). A shell wrapper intercepts tool invocations, fires hooks on every tool call, then runs a 3-layer pipeline (extract → compress to ≤500-token digest → merge into project memory doc) at session end. The next session gets prior context injected automatically.

A simple MCP server implementation in TypeScript that communicates over stdio, allowing users to ask questions that end with 'yes or no' to trigger the MCP tool in Cursor.

Shared, live team memory for Claude — a remote MCP server on Cloudflare Workers + D1.

A local, persistent memory system for AI coding assistants that stores decisions, patterns, and session context via MCP tools. It enables cross-session memory management using SQLite and optional vector search without external dependencies or cloud storage.

Enables personal cross-tool memory by exposing a searchable episodic archive of AI sessions and a curated, high-trust semantic facts layer through MCP tools and resources.

MCP server for context-aware memory and retrieval with hybrid search, dual-phase memory, and boundary-first security.

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.

Local-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.

A fully-local AI memory system that saves notes, code, and terminal output to a vector database via Ollama and LanceDB, enabling context retrieval from terminal, API calls, or inside Claude Code.

MCP server implementing the Generative Agents memory architecture, enabling observation, retrieval, reflection, and planning for agent memory management.

A persistent, conflict-aware memory MCP server for AI coding assistants (Cursor, Claude Code).

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

Exposes local memory vaults as 6 MCP tools over stdio, enabling clients like Windsurf, Zed, and Claude Desktop to read and write memory.

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.

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

Self-hosted personal knowledge graph for Claude that persists across sessions, devices, and tools. Built on Neo4j with local semantic embeddings; OAuth 2.1 lets Claude Code, Claude Desktop, and claude.ai web all hit the same graph.