"Information about Redis, an in-memory data store" matching MCP servers:

Enables AI tools like GitHub Copilot to manage and persist context using a local JSON-based memory store. Provides CLI, MCP server, and VS Code integration for storing, retrieving, and managing context entries.

Enables storing, searching, and compressing contextual memories for LLM interactions, with tools for memory management and context injection.

A drop-in replacement for mcp-memory-duckdb with full concurrent access support using Redis Stack. Enables persistent knowledge graph storage with full-text search and multi-session concurrent access.

Enterprise support ticket system using FastMCP server with Redis for persistent state and multiple clients.

Provides AI coding assistants with persistent memory, AST-based project indexing, and tools for live context management and hallucination detection. It enables saving lessons to local files, trimming conversation history, and verifying code symbols to prevent errors.

Enables persistent skill management over the Model Context Protocol, allowing agents to use, write, list, and migrate skills backed by directory, Git, or S3 stores.

A Rust MCP stdio server for durable project-local AI notes, enabling agents to store, search, and manage verified facts, decisions, and conventions.

Persistent memory and pattern learning for AI coding assistants via MCP.

Auto-captured, auto-recalled, path-scoped memory for AI coding agents and teams.

Slipstream - Built by Vektor Memory - a persistent multi-layered memory architecture. 4-layer associative graph memory (MAGMA) with autonomous REM cycle, CLI, DXT-MCP Cloak Tools.

Gives AI coding agents persistent, evolving knowledge about a codebase, enabling them to store and retrieve observations about architecture, conventions, gotchas, and recent work context.

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

Provides persistent memory with semantic search for MCP-based AI agents, enabling them to store and recall information across sessions using vector embeddings.

An MCP server that provides AI assistants with persistent, semantic memory using Turso for storage and OpenAI for vector search. It enables natural language operations to store, retrieve, and refine information with automatic duplicate detection and quality validation.

Provides Claude Co-work with MCP tools to search and record organizational memory, including search, read, query, ingest, remember, sync, and status operations.

MCP server providing durable Substrate organizational memory tools, including search, read, query, ingest, remember, and sync. It integrates with Codex to automatically capture completed turns and session boundaries for persistent memory.

MCP Memory is an MCP Server that gives MCP Clients the ability to remember information about users across conversations. It uses vector search technology to find relevant memories based on meaning, not just keywords.

A local-only MCP server that uses SQLite to store, search, and manage a personal library of AI prompts. It enables developers to organize and reuse prompts across multiple AI clients like Claude and Cursor while keeping all data on their local machine.

MCP Memory is a MCP Server that gives MCP Clients the ability to remember information about users across conversations using vector search.

MCP server that connects Claude Code to Substrate organizational memory, providing tools for searching, reading, querying, and writing memory, with automatic capture of conversation turns.