Redis Agent Memory Server

A memory layer for AI agents using Redis as the vector database.

Features

• Dual Interface: REST API and Model Context Protocol (MCP) server
• Two-Tier Memory: Working memory (session-scoped) and long-term memory (persistent)
• Configurable Memory Strategies: Customize how memories are extracted (discrete, summary, preferences, custom)
• Semantic Search: Vector-based similarity search with metadata filtering
• Flexible Backends: Pluggable vector store factory system
• AI Integration: Automatic topic extraction, entity recognition, and conversation summarization
• Python SDK: Easy integration with AI applications

Quick Start

1. Installation

# Install dependencies
pip install uv
uv install --all-extras

# Start Redis
docker-compose up redis

# Start the server (development mode)
uv run agent-memory api --no-worker

2. Python SDK

# Install the client
pip install agent-memory-client

from agent_memory_client import MemoryAPIClient

# Connect to server
client = MemoryAPIClient(base_url="http://localhost:8000")

# Store memories
await client.create_long_term_memories([
    {
        "text": "User prefers morning meetings",
        "user_id": "user123",
        "memory_type": "preference"
    }
])

# Search memories
results = await client.search_long_term_memory(
    text="What time does the user like meetings?",
    user_id="user123"
)

Note: While you can call client functions directly as shown above, using MCP or SDK-provided tool calls is recommended for AI agents as it provides better integration, automatic context management, and follows AI-native patterns. See Memory Integration Patterns for guidance on when to use each approach.

3. MCP Integration

# Start MCP server (stdio mode - recommended for Claude Desktop)
uv run agent-memory mcp

# Or with SSE mode (development mode)
uv run agent-memory mcp --mode sse --port 9000 --no-worker

Documentation

📚 Full Documentation - Complete guides, API reference, and examples

Key Documentation Sections:

• Quick Start Guide - Get up and running in minutes
• Python SDK - Complete SDK reference with examples
• Vector Store Backends - Configure different vector databases
• Authentication - OAuth2/JWT setup for production
• Memory Types - Understanding semantic vs episodic memory
• API Reference - REST API endpoints
• MCP Protocol - Model Context Protocol integration

Architecture

Working Memory (Session-scoped)  →  Long-term Memory (Persistent)
    ↓                                      ↓
- Messages                          - Semantic search
- Context                          - Topic modeling
- Structured memories              - Entity recognition
- Metadata                         - Deduplication

Use Cases

• AI Assistants: Persistent memory across conversations
• Customer Support: Context from previous interactions
• Personal AI: Learning user preferences and history
• Research Assistants: Accumulating knowledge over time
• Chatbots: Maintaining context and personalization

Development

# Install dependencies
uv install --all-extras

# Run tests
uv run pytest

# Format code
uv run ruff format
uv run ruff check

# Start development stack
docker-compose up

Production Deployment

For production environments, use Docket workers for better reliability and scale:

# Start the API server (production mode)
uv run agent-memory api

# Start MCP server (production mode - SSE)
uv run agent-memory mcp --mode sse --port 9000

# Start background workers (required for production)
uv run agent-memory task-worker --concurrency 10

Production features:

• Authentication: OAuth2/JWT with multiple providers (Auth0, AWS Cognito, etc.)
• Redis: Requires Redis with RediSearch module (RedisStack recommended)
• Background Processing: Docket workers handle memory indexing, summarization, and compaction
• Scaling: Supports Redis clustering and horizontal worker scaling
• Monitoring: Structured logging and health checks included

Development vs Production:

• Development: Use --no-worker flags for quick setup, tasks run inline
• Production: Use separate worker processes for better performance and reliability

License

Apache License 2.0 - see LICENSE file for details.

Contributing

We welcome contributions! Please see the development documentation for guidelines.