Memory MCP - Redis Stack Backend
Uses Redis Stack as the backend data store, leveraging RediSearch for full-text search and ReJSON for native JSON document storage.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Memory MCP - Redis Stack Backendsearch for entities about Redis Stack"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Memory MCP - Redis Stack Backend
A drop-in replacement for mcp-memory-duckdb with full concurrent access support using Redis Stack.
Features
Concurrent Access: Multiple Claude sessions can read/write simultaneously
RediSearch: Full-text search across entities and observations
ReJSON: Native JSON document storage
Persistent Storage: RDB snapshots + AOF for durability
Git-Friendly Export: Auto-exports to JSONL after every change
API Compatible: Same tools as mcp-memory-duckdb
Cross-Platform: Works on macOS, Windows, and Linux
Related MCP server: r3 (Recall)
Quick Install
Windows (One-liner)
# PowerShell (run as Administrator recommended)
irm https://raw.githubusercontent.com/BakeMark/mcp-memory-redis/main/install.ps1 | iexOr download and run:
curl -O https://raw.githubusercontent.com/BakeMark/mcp-memory-redis/main/install.bat
install.batmacOS
# Install Redis Stack
brew tap redis-stack/redis-stack
brew install redis-stack
# Clone and install
git clone https://github.com/BakeMark/mcp-memory-redis.git ~/.claude/mcp-memory-redis
cd ~/.claude/mcp-memory-redis
npm install
# Start Redis
redis-stack-server --daemonize yesDocker (Any Platform)
# Start Redis Stack
docker run -d --name redis-stack \
-p 6379:6379 \
-v redis-memory-data:/data \
--restart unless-stopped \
redis/redis-stack:latest
# Clone and install
git clone https://github.com/BakeMark/mcp-memory-redis.git
cd mcp-memory-redis
npm installConfiguration
Claude Code MCP Config
Add to ~/.claude/mcp-servers.json (macOS/Linux) or %USERPROFILE%\.claude\mcp-servers.json (Windows):
macOS/Linux
{
"mcpServers": {
"memory": {
"command": "node",
"args": ["~/.claude/mcp-memory-redis/src/index.js"],
"env": {
"REDIS_URL": "redis://localhost:6379",
"MEMORY_DIR": "~/.claude/memory",
"MEMORY_EXPORT_PATH": "~/.claude/memory/knowledge.jsonl"
}
}
}
}Windows
{
"mcpServers": {
"memory": {
"command": "node",
"args": ["C:\\Users\\USERNAME\\.claude\\mcp-memory-redis\\src\\index.js"],
"env": {
"REDIS_URL": "redis://localhost:6379",
"MEMORY_DIR": "C:\\Users\\USERNAME\\.claude\\memory",
"MEMORY_EXPORT_PATH": "C:\\Users\\USERNAME\\.claude\\memory\\knowledge.jsonl"
}
}
}
}Environment Variables
Variable | Default | Description |
|
| Redis connection URL |
|
| RediSearch index name |
|
| Directory for exports |
|
| JSONL export path |
Windows Requirements
The install script handles these automatically:
Requirement | Install Method |
Node.js 18+ |
|
Docker Desktop |
Alternative to Docker: Memurai (Windows-native Redis)
CLI Usage
# Export knowledge graph
node src/cli.js export ~/backup.jsonl
# Import knowledge (merge with existing)
node src/cli.js import ~/backup.jsonl --merge
# Import knowledge (skip existing entities)
node src/cli.js import ~/backup.jsonl --skip
# Search the graph
node src/cli.js search "database"
# Show statistics
node src/cli.js stats
# Clear all data
node src/cli.js clearAPI Tools
The MCP server exposes these tools:
Tool | Description |
| Create new entities with observations |
| Create relationships between entities |
| Add observations to existing entities |
| Full-text search across entities |
| Retrieve specific entities by name |
| Get entire knowledge graph |
| Delete entities (cascades) |
| Delete specific observations |
| Delete relationships |
| Export to JSONL |
| Import from JSONL |
Migration from DuckDB
Import your existing knowledge:
# Export from current DuckDB (if needed)
node /path/to/mcp-memory-duckdb/src/cli.js export /tmp/backup.jsonl
# Import to Redis
node src/cli.js import /tmp/backup.jsonl --mergeConcurrent Access
Unlike DuckDB which only allows single-writer access, Redis Stack supports:
Multiple concurrent readers
Multiple concurrent writers
Atomic transactions via MULTI/EXEC
No file locking issues
This means you can run multiple Claude Code sessions simultaneously, all accessing the same knowledge graph.
Data Schema
Entities are stored as JSON documents with the key prefix entity::
{
"name": "EntityName",
"entityType": "Type",
"observations": ["obs1", "obs2"],
"createdAt": "2026-01-30T12:00:00.000Z",
"updatedAt": "2026-01-30T12:00:00.000Z"
}Relations are stored with the key prefix rel::
{
"from": "EntityA",
"to": "EntityB",
"relationType": "relates_to",
"createdAt": "2026-01-30T12:00:00.000Z"
}Troubleshooting
Windows: Docker not starting
# Start Docker Desktop manually, then retry
Start-Process "C:\Program Files\Docker\Docker\Docker Desktop.exe"Redis Connection Failed
# Check if Redis is running
redis-cli ping
# Docker: check container
docker ps | grep redis-stack
docker logs redis-stack
# Restart container
docker restart redis-stackSearch Index Issues
The search index is created automatically on first startup. If issues persist:
redis-cli
> FT._LIST
> FT.INFO memory_idxWindows: Uninstall
.\uninstall.ps1License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BakeMark/mcp-memory-redis'
If you have feedback or need assistance with the MCP directory API, please join our Discord server