"Information on memory" matching MCP servers:

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

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

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.

Local memory for coding agents that can refuse, not only recall. A rule carrying a machine-checkable proof blocks the matching command before it runs, while prose-only rules can warn but never block.

On-chain delivery receipts for x402 AI-agent payments on Solana: anchors SHA-256 digests of delivered content to a PDA after settlement; buyers verify proof of delivery offline with zero trust in the seller. Live MCP endpoint + npm bridge.

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

Memory vaults on your own machine, one per life domain, retrieved with a local BM25 index fused with vector search, where the human decides which vaults a model may answer from. Requires the Mnemosyne OS desktop app running locally; it also reports what other coding agents on the same machine are doing.

A public, source-linked notebook for AI agents and people. Search and read without a key; publish findings, questions, and corrections with permanent IDs and linked replies using an operator-controlled posting key.

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.

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.

Hermetic memory for AI agents — one Rust binary, one SQLite file, zero network. Recall returns evidence with provenance or abstains: no code path for making things up.

Enables AI coding agents to store and retrieve durable project decisions, conventions, environment notes, and bug fixes in Notion, with optional Obsidian Vault dual-write.

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.

A persistent world your agents share across sessions and models. MCP memory server with semantic memory retrieval, cross-agent handoff, a hosted remote endpoint with OAuth, a free 24-hour room, and an open-source local stdio server.

Live verifiable on-chain data for the $BOBAI token on BNB Chain: price computed from pair reserves × Chainlink (no price API), liquidity depth with LP-burn proof, buyback-and-burn audit trail, and fee-on-transfer-safe trade params. 13 read-only tools + 2 guided prompts, no API key.

A Linux system monitoring MCP server that provides real-time information on CPU, memory, disk, network, processes, Docker, security, and more via MCP tools.

Local-first bitemporal memory for AI agents with deterministic supersession, point-in-time recall, erasure proofs, and tamper-evident audit history.

Local MCP server giving AI coding agents (Claude Code, Cursor, VS Code/JetBrains Copilot) a shared, persistent memory of your projects and every bug/issue faced during development. Stateless, plain-file storage (AGENTS.md + issues.jsonl) — no database.

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