🧠 𝑴𝒆𝒎𝒐𝒓𝒚-𝑷𝒍𝒖𝒔 is a lightweight, local RAG memory store for MCP agents. Easily record, retrieve, update, delete, and visualize persistent "memories" across sessions—perfect for developers working with multiple AI coders (like Windsurf, Cursor, or Copilot) or anyone who wants their AI to actually remember them.

MCP Server for persistent bot memory — stores learnings, preferences, skills and workflows in a local JSON store. Works with any MCP-compatible client (Claude Code, Claude Desktop, Cursor, etc.)

ReactiveMemory MCP Server gives AI assistants a persistent, queryable, locally-stored memory system backed by vector search, a temporal knowledge graph, and a vault-structured content store.

Cross-platform memory and ambient awareness for AI agents — knowledge store, alert collation, and intention tracking via MCP. Self-host or cloud.

A simple MCP server that stores and retrieves memories from multiple LLMs.

Persistent memory for AI agents — store, retrieve and search knowledge across sessions

JavaScript MCP Server for persistent agent memory — store, retrieve, search knowledge

Persistent memory for AI agents — store, retrieve and search knowledge across sessions

Local-first AI memory your assistants share. One store, every model, your machine.

An agent memory system with a causal core — facts, temporal state, and decision→outcome causal edges on one SQLite store

RAMen is a fast in-memory data store like Redis, but built for AI: drop-in Redis protocol, native vector search, semantic caching, and a built-in MCP server for agents. Single Go binary, BSD-3.

Memory for your AI agents. Remote MCP (Model Context Protocol) server for storing, retrieving, and semantically searching "memories" on behalf of AI agents

A content-addressed memory store for AI agents

A tiny local MCP server that learns how you talk — catchphrases, dialect, tone — without storing private memories. Local-first, no LLM calls.

Long-term memory for OpenAI Codex CLI: an MCP server and notify hook that store every turn in local SQLite with FTS5 search.

MCP server that gives a local model persistent memory: remember, recall, update and forget short facts stored in SQLite, launched by LM Studio

A memory for AI assistants that is just a SQLite file: full-text search over MCP, no vector store, no embeddings, no external service.

An MCP server providing a persistent key-value memory store with semantic search for your agents

A memory for AI assistants that is just a SQLite file: full-text search over MCP. No vector store, no embeddings, no external service.

MCP memory server for ZenBrain: agent memory for any Model Context Protocol client — store, recall, forget, consolidate, health. Local SQLite file, no account.

🧠 Manage AI context seamlessly with the MCP server for storing and retrieving semantic memory across sessions. Enhance your AI's knowledge retention.

Project-local MCP memory server for AI coding agents. Knowledge graph stored in .mcp/ inside each repo — isolated per project, Git-friendly JSON, dual-buffer (durable graph + active context).

Associative memory for LLM agents — a key-graph memory layer (MCP server) that recalls by association, not just vector similarity. A graph-based alternative to vector-store agent memory.

Persistent decision and constraint memory for coding agents: a local stdio MCP server and CLI that store ADR-style decisions as git-friendly markdown, linked to SpecGate requirement ids, tests and commits.

Local long-term memory for Claude Code and Codex: SQLite fact store, search in 18 languages, trust scoring, fact history, HRR recall and 23 MCP memory tools. No API key and no network by default.

Self-hosted AI memory ledger. You and your agents share one memory store over MCP — one SQLite file, web UI, REST, works offline.

Portable AI memory over a local folder or hosted vault, served via MCP — one memory shared across models and harnesses (Claude, ChatGPT, Codex, Cursor). Per-project spaces plus a shared org layer, stored as plain markdown you own.

Local-first persistent memory for AI agents — store, recall, and consolidate knowledge across sessions using FAISS, SQLite, and any LLM. MCP server for coding agents and any MCP client.

Enhanced MCP server-memory with ZeroDB cloud persistence and semantic vector search. Drop-in replacement for @modelcontextprotocol/server-memory that stores your knowledge graph in the cloud instead of local JSONL files.

MCP server providing persistent cross-session memory for AI agents — store, recall, search, and summarize memories across agent boundaries

Agent memory for Claude Code, Cursor, Codex: MCP server + Graph RAG over your Obsidian or markdown notes, a search layer for a Karpathy-style LLM Wiki. Wikilinks are the graph, SQLite the only store.

Pluggable, multi-store memory for any AI system — episodic, semantic, temporal-graph and dialectic user memory in one library.

Enable AI agents to store, search, and delete persistent memories across sessions to enhance context retention and recall. Integrate seamlessly with Mem0.ai's cloud or self-hosted Supabase storage for scalable and reliable memory management. Optimize your LLM applications with advanced filtering, semantic search, and flexible storage modes tailored to your needs.

Agent memory with no API key, no LLM, and no embedding provider. Serves MCP over stdio against a local SQLite store, or Cloudflare Workers + D1. Drop-in for @modelcontextprotocol/server-memory; every memory keeps its source, its scope, and the evidence th

MCP server for persistent memory using Qdrant vector store

Your portable AI memory layer. Classify, store, and recall what matters across models, tools, and devices.

Memory for coding agents: your AI stores every fix and finds it again when the problem returns. MCP server for Claude Code, Cursor, Copilot, Windsurf, Codex and Gemini CLI, hosted in the EU.

A persistent-memory MCP server for AI agents, with an honest health endpoint that survives its store dying.

A TypeScript-based MCP server implementing a memory system inspired by neurodivergent cognitive styles. It organizes thoughts into five districts (knowledge domains), ranks search results using BM25 semantic ranking, and stores memories as a persistent knowledge graph with bidirectional connections.

Local persistent memory store for LLM applications including continue.dev, cursor, claude desktop, github copilot, codex, antigravity, etc.

MCP server that gives coding agents git-backed, per-repo memory: Markdown memories in a per-repo git store keyed to the repo's root-commit SHA, every write a commit. Tools to write, search and seed memory from a repo's tree, package.json and docs.

Local-first MCP memory layer for AI coding assistants; persistent cross-session memory, stored entirely on your machine

A persistent memory MCP server for AI coding agents — stores, searches, and retrieves atomic learnings per repository.

Portable AI memory over a local folder or hosted vault, served via MCP — your memory roams with you across models and harnesses (Claude, ChatGPT, Codex, Cursor). Per-project spaces plus a shared layer, stored as plain markdown you own.

MCP server for encrypted, persistent agent memory: facts are embedded and encrypted on the client, so the server stores only ciphertext and vectors.

Local-first memory infrastructure for AI coding agents. One brain shared across Claude Code, Codex CLI, Cursor, Kiro, Continue, Cline, Windsurf, or any MCP client. Organized in pluggable pods, stored in your own Postgres. No cloud, no telemetry. Auto-capt

Git-backed project memory for AI coding agents: claims as reviewed markdown in your repo, anchored to the code they describe, with drift detection, supersede chains and a CI contradiction gate for shared stores.

RCLL — self-hosted shared memory for a team of AI agents. Rooms, hierarchical L0-L3 depth, MCP. The read path never invokes a language model. We publish the measured cost of one shared store versus ten private ones. Fork of vectorize-io/hindsight (MIT).

Portable long-term memory store for agents, exposed over MCP

Store, search, and retrieve memories with semantic and keyword search. Create relationships between memories to build knowledge graphs. Organize with tags, types, and trust levels. Publish memories to shared spaces and manage user preferences for intelligent context retention.

An MCP server that enables AI agents to persistently store and retrieve project information from a memory file.

Agent memory: SQLite fact store + Git wiki + keyword bridge. Multi-agent memory system for AI agents. No embeddings, no vector DB. Zero-dependency Python CLI with MCP server.

🦛 A hippocampus for your AI. Long-term memory for Claude & any MCP client, stored as Markdown in your own GitHub repo: hybrid semantic search, knowledge graph, auto-memory, compaction-proof, token-lean.

Free, local memory and rules hub for AI coding tools: persistent memory for Claude Code, Codex, Cursor and Gemini CLI. One SQLite store over MCP, REST and CLI. Rules sync to CLAUDE.md and AGENTS.md. claude-mem alternative.

Aletheia: a free, local memory and rules hub for AI coding tools such as Claude Code, Codex, Cursor and Gemini CLI. One store any tool reads over MCP, REST or CLI; rules synced to CLAUDE.md, AGENTS.md, Cursor and more; export and import to move between to

A Claude Code plugin that gives Claude persistent memory across sessions — stores lessons and decisions as markdown in your Obsidian vault, searches them with SQLite FTS5, and mines past transcripts automatically.

Shared long-term memory for AI coding agents — one local store for Claude Code, Codex CLI, opencode and anything that speaks MCP. SQLite + FTS5, no vector DB, $1-3/month.

Anti-poisoning memory store for agents: provenance, versioning, quarantine gate

Read-only MCP servers for memv2 and Javis memory, for chat Bots: one combined tool with cross-check labels, plus the two single-store servers.

Project memory for AI coding agents, stored in your repo. Branches, merges and gets reviewed with the code. Any MCP client.