"Understanding the term 'temporal' and its uses" matching MCP servers:

A persistent, human-like memory system for AI companions in LM Studio, using SQLite and ChromaDB for hybrid storage, enabling seamless recall across sessions and models.

An enterprise-ready MCP server that exposes a RAG tool for retrieving relevant context and metadata from a Qdrant vector database using natural language queries.

Long-term persistent memory for AI agents with hybrid search (DiskANN + FTS), bi-temporal knowledge graph, and 81.1% LongMemEval accuracy.

Provides AI agents with persistent, searchable memory that survives across conversations using semantic search, temporal versioning, and smart organization. Enables long-term context retention and cross-session continuity for AI assistants.

Provides AI assistants with long-term semantic memory capabilities through local vector-based storage. Enables storing, recalling, and managing information across sessions with complete privacy using ChromaDB, with no data ever leaving your machine.

A multi-agent Retrieval-Augmented Generation system exposed as an MCP server. Ask a question and a LangGraph pipeline plans the retrieval, pulls evidence from a pgvector knowledge base, optionally augments it with live web research, drafts a cited answer, and then self-critiques it for grounding — revising until the answer is supported by the sources.

Semantic memory for AI builders: capture the tacit engineering know-how that never reaches your docs, recall it the moment it applies. Built in Rust on Postgres and pgvector.

An intelligent memory MCP server that provides AI applications with semantic search, entity extraction, and knowledge graph capabilities using local Redis caching and optional cloud sync. It enables LLMs to store and retrieve long-term context across sessions with high-performance multi-tier storage.

askDB is an MCP server that retrieves relevant database schema (DDL) from a Pinecone index and provides it to LLMs to write SQL, without connecting to the database itself.

Dual-mode tool providing long-term memory management for Claude Code and MCP clients, with semantic search and user/session isolation via Qdrant.

A Byzantine fault-tolerant MCP Memory server that uses SQLite write-ahead logging and FAISS hybrid vector search for deterministic, secure memory operations.

Long-term and multimodal memory for AI agents. Store facts and conversations with add_memory, recall them with search_memories — 8 tools over stdio/SSE/HTTP. Per-character memory isolation, LLM-based semantic deduplication, FAISS + JSON storage, and a fully local option (Ollama, no API key). Drop-in compatible with Mem0.

Enables agents to run hybrid dense and BM25 search over a local folder of Markdown files, read and write notes, and trigger reindexing as the folder changes. It also injects the most relevant sections into each prompt automatically and runs entirely locally with a bundled embedding model.

A Model Context Protocol (MCP) server that provides a local-first RAG engine for your markdown documents. It uses a file-based Milvus vector database to index your notes, enabling LLMs to perform semantic search and retrieve relevant content from your local files.

Enables AI agents to maintain long-term, cross-session memory by extracting facts, reconciling state conflicts, and retrieving relevant memories via vector search.

A semantic search system for Claude Code transcript history, exposed as an MCP server so Claude Code can query its own past sessions.

Enhanced MCP knowledge graph memory server with cloud persistence and semantic search, acting as a drop-in replacement for the standard memory server.

ArcadeDB Multi-Model Database, one DBMS that supports SQL, Cypher, Gremlin, HTTP/JSON, MongoDB and Redis. ArcadeDB is a conceptual fork of OrientDB, the first Multi-Model DBMS. ArcadeDB supports Vector Embeddings.

Gives AI agents private, persistent, semantically searchable long-term memory with RAG, governed multi-agent scopes, and real-time memory-change subscriptions.

Local-first agent-memory MCP server with a why() tool: recall a fact together with its connected subgraph (multi-hop), so linked memories surface even when they share no words with the query. remember/recall/relate/forget/why over one fused vector + graph + columnar engine a single offline Rust binary.