db-memory
A vector-DB MCP server that gives Claude conversational memory by storing solved problems and solutions as vectors and retrieving relevant ones when a new request resembles a past solution.
README
db-memory
A vector-DB MCP server that gives Claude conversational memory: it stores solved problems + solutions as vectors and resurfaces the most relevant ones when a new request looks similar to something solved before.
- Switchable backend —
VECTOR_BACKEND=local|cloud, no code change.local→ Chroma, embedded on disk. Offline, no account.cloud→ Qdrant Cloud, managed, shared across machines.
- Small/fast local embeddings —
all-MiniLM-L6-v2(384-dim). No API key, runs on CPU in ms.
Tools exposed
| Tool | What it does |
|---|---|
search_memory(query, top_k) |
Find past solved issues similar to the current request |
save_memory(problem, solution) |
Store a solved issue for future retrieval |
memory_stats() |
Show active backend + how many memories are stored |
Setup
cd ~/code/mcp/db-memory
python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
cp .env.example .env # edit if you want cloud
Run / test standalone
mcp dev memory_server.py # opens the MCP Inspector UI
Register with Claude Code
Local backend (default):
claude mcp add db-memory -- \
~/code/mcp/db-memory/.venv/bin/python ~/code/mcp/db-memory/memory_server.py
Then /mcp in Claude Code shows the three tools. Claude will call
search_memory when a request resembles a past one, and save_memory after
solving something.
Switching to cloud
-
Create a free cluster at cloud.qdrant.io, copy the URL + API key.
-
In
.env(or the MCP env):VECTOR_BACKEND=cloud QDRANT_URL=https://YOUR-CLUSTER.cloud.qdrant.io:6333 QDRANT_API_KEY=...
Same embeddings, same tools — only the storage moves. (The two backends don't share data; re-save or migrate if you switch with existing memories.)
Notes
- Embedding dimension is fixed by the model (384 for MiniLM). If you change
EMBED_MODEL, delete the old Chromamemory_db/or use a fresh Qdrant collection — vectors of different sizes can't mix. - An MCP tool only runs when Claude invokes it; it can't passively log every
message. For guaranteed full capture, log each turn to the same DB from your
app (or a Claude Code
Stophook) and keep this server for retrieval.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。