memory-mcp
Persistent, searchable, versioned memory for AI agents, backed by Valkey and exposed as an MCP server over HTTP.
README
memory-mcp
Persistent, searchable, versioned memory for AI agents — backed by Valkey (Redis-compatible), exposed as an MCP server over HTTP.
Works with any MCP-compatible agent: Claude Code, Cursor, VS Code, and others.
What it does
- Stores named memory entries with tags, types, and project scopes
- Tag-intersection search, type/project filtering, and substring search
- Hit tracking (entries accessed more float to the top)
- Full version history with rollback
- Prometheus metrics endpoint
- Optional bearer token auth
Quick start
cp .env.example .env
# Optional: set MEMORY_MCP_AUTH_TOKEN in .env (see Auth section)
docker compose up -d
This pulls the pre-built image from GHCR. The MCP server is now available at http://127.0.0.1:3106/mcp.
To build locally instead:
docker compose build
docker compose up -d
Using an existing Redis or Valkey
By default docker compose up -d starts a bundled Valkey container. To connect to an existing Redis or Valkey instance instead, set VALKEY_URL and start only the memory-mcp service:
# .env
VALKEY_URL=redis://your-host:6379
docker compose up -d memory-mcp
Any Redis-compatible server (Redis 6+, Valkey, KeyDB, Upstash via rediss://, etc.) works. The server uses only basic data structures: hashes, lists, and sets.
Agent setup
Copy AGENTS.md from this repo into your project root. It tells your agent how to use the memory tools, what to store, and when.
Then register the MCP server with your agent client:
Claude Code
# Without auth
claude mcp add memory --transport http http://127.0.0.1:3106/mcp
# With auth
claude mcp add memory --transport http http://127.0.0.1:3106/mcp \
--header "Authorization: Bearer your-token"
Or add manually to ~/.claude.json:
{
"mcpServers": {
"memory": {
"type": "http",
"url": "http://127.0.0.1:3106/mcp",
"headers": { "Authorization": "Bearer your-token" }
}
}
}
Cursor
Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
{
"mcpServers": {
"memory": {
"url": "http://127.0.0.1:3106/mcp",
"headers": { "Authorization": "Bearer your-token" }
}
}
}
VS Code (GitHub Copilot, MCP extension)
Add to .vscode/mcp.json in your project:
{
"servers": {
"memory": {
"type": "http",
"url": "http://127.0.0.1:3106/mcp",
"headers": { "Authorization": "Bearer your-token" }
}
}
}
Omit the headers / Authorization line in any config if you are not using auth.
Configuration
Copy .env.example to .env and edit as needed.
| Variable | Default | Description |
|---|---|---|
MEMORY_MCP_BIND |
127.0.0.1 |
Interface to bind on. Use 0.0.0.0 only with AUTH_TOKEN set. |
MEMORY_MCP_HOST_PORT |
3106 |
Port exposed on the host |
MEMORY_MCP_AUTH_TOKEN |
(empty) | Bearer token for /mcp. Empty = no auth. Generate: openssl rand -hex 32 |
MEMORY_MCP_MAX_ENTRIES_WARN |
300 |
Soft cap — warns on write when exceeded |
MEMORY_MCP_MAX_VERSIONS_PER_ENTRY |
20 |
Max version snapshots per entry |
MEMORY_MCP_MEM_LIMIT |
256m |
Container memory cap |
VALKEY_IMAGE |
valkey/valkey:9.0.3 |
Valkey image to use |
Auth
By default the server runs unauthenticated. This is safe when bound to loopback (127.0.0.1) and accessed only from the local machine.
To enable auth:
# Generate a token
openssl rand -hex 32
# Add to .env
MEMORY_MCP_AUTH_TOKEN=your-generated-token
docker compose up -d
All requests to POST /mcp must then include:
Authorization: Bearer <token>
GET /health and GET /metrics are always unauthenticated.
Available tools
| Tool | Description |
|---|---|
memory_search |
Search by tags (intersection), type, project, or text substring |
memory_get |
Fetch one entry by ID (increments hit counter) |
memory_set |
Create or update an entry (versioned on every write) |
memory_list |
List entries with optional type/project filter |
memory_delete |
Delete an entry (tombstone version written first) |
memory_history |
View version history for an entry |
memory_rollback |
Restore an entry to a previous version |
memory_prune_candidates |
Surface zero-hit stale entries for review (read-only) |
Memory types
pattern, decision, reference, feedback, incident, project, entity, state
Endpoints
| Method | Path | Auth | Description |
|---|---|---|---|
POST |
/mcp |
if configured | MCP JSON-RPC endpoint |
GET |
/health |
none | Health check |
GET |
/metrics |
none | Prometheus metrics |
Data model
Each entry is stored as a Redis hash at mem:<id>:
| Field | Description |
|---|---|
title |
Short descriptive title |
body |
Full content |
type |
Entry type |
tags |
Comma-separated tag list |
source |
Who wrote it |
project |
Project scope (empty = cross-project) |
created |
ISO date of creation |
updated |
ISO date of last update |
hits |
Times retrieved via memory_get |
ttl |
Expiry in seconds (optional) |
Version history is stored in a Redis list at memver:<id> (newest-first, capped at MAX_VERSIONS_PER_ENTRY).
Tag, type, and project indexes are Redis sets (tag:<name>, type:<name>, project:<name>).
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.