MCP memory server

Persistent memory for agent pipelines and chat clients: REST API, knowledge graph and autonomous consolidation, with remote MCP over OAuth.

Local persistent memory store with MCP, HTTP API and session import from many coding agents.

Notes-as-memory: your AI reads and writes plain Markdown files you can open in Obsidian, indexed locally.

Centralized, remote-accessible version of the Cline "memory bank" file pattern, served over MCP with per-project isolation.

MCP server for the hosted Graphlit platform: ingest content from many sources into a searchable project.

Open-source local AI memory system with pluggable retrieval (ChromaDB by default) and auto-save hooks for coding agents.

MCP server for Cognee memory; by default each client gets its own dataset so agents do not overwrite each other.

Memory-bank MCP server that builds a project-specific knowledge graph (decisions, progress, patterns) in a per-workspace SQLite DB.

MCP server exposing Graphiti knowledge-graph memory, with HTTP endpoint at /mcp/ and Docker Compose setups.

Knowledge-graph memory with semantic retrieval and temporal awareness, using Neo4j for both graph and vector search.

Knowledge-graph memory (entities, relations, observations) stored in a local JSONL file. The reference implementation many forks build on.

Fork of the official memory server focused on local development: persistent knowledge graph in local files.

Template MCP server for long-term agent memory using the Mem0 library and Postgres.

MCP server for the mem-agent model: an Obsidian-like Markdown memory managed by a small local LLM, with importers for ChatGPT and other exports.

Self-deployed remote MCP memory server on Cloudflare Workers, Vectorize, D1 and Durable Objects.

Persistent knowledge-graph memory for MCP backed by libSQL (local SQLite file or remote Turso).

Knowledge-graph memory MCP server backed by Neo4j (local or AuraDB), from Neo4j Labs.