内存自定义：PouchDB🧠
此项目为MCP团队提供的内存服务器添加了新功能。它允许创建和管理通过语言模型（LLM）捕获交互的知识图。 🚀
此回购是从 这是一个很好的起点，再次感谢您修复时间戳。这个仓库的目标更多的是通过不断增加的json文件来解决这个问题。
新功能✨
1.PouchDB集成💾
- 服务器现在使用PouchDB进行强大的基于文档的存储
- 为什么？：更好的数据一致性、内置版本控制和改进的大型数据集性能
- 维护文件备份以实现兼容性
2.自定义内存路径📁
- 用户现在可以为各种项目指定不同的内存文件路径
- 为什么？：此功能增强了内存数据的组织和管理，允许特定于项目的内存存储
3.时间戳⏰
- 服务器现在为交互生成时间戳
- 为什么？：时间戳可以跟踪每个内存的创建或修改时间，为存储的数据提供更好的上下文和历史记录
入门指南🚀
先决条件🔧
- Node.js（版本16或更高）
- PouchDB（作为依赖项自动安装）
通过Smithery安装📦
通过以下方式自动安装克劳德桌面知识图谱内存服务器 史密瑟里:
npx -y @smithery/cli install @bneil/mcp-memory-pouchdb --client claude安装🛠️
- 克隆存储库：
git clone git@github.com:bneil/mcp-memory-pouchdb.git
cd mcp-memory-pouchdb- 安装依赖项：
npm install配置⚙️
服务器需要设置两个环境变量：
MEMORY_FILE_PATH：存储内存备份文件的绝对路径POUCHDB_PATH：存储PouchDB数据库的绝对路径
您的配置示例 claude_desktop_config.json / .cursor/mcp.json:
{
"mcpServers": {
"memory": {
"command": "node",
"args": ["/path/to/mcp-memory-pouchdb/dist/index.js"],
"env": {
"MEMORY_FILE_PATH": "/path/to/custom/memory.json",
"POUCHDB_PATH": "/path/to/custom/pouchdb_directory",
"DISABLE_MEMORY_FILE": "true"
}
}
}
}如果未设置任何环境变量，服务器将无法启动。 🚫
可选环境变量：
POUCHDB_OPTIONS：附加PouchDB配置选项的JSON字符串DISABLE_MEMORY_FILE：设置为“true”禁用保存到memory.json文件（仅使用PouchDB进行存储）
运行服务器🚀
更新mcp服务器json文件📝
将此添加到您的 claude_desktop_config.json / .cursor/mcp.json 文件：
{
"mcpServers": {
"memory": {
"command": "node",
"args": ["/path/to/mcp-memory-pouchdb/dist/index.js"],
"env" : {
"MEMORY_FILE_PATH":"/home/.../local_dbs/memory.json",
"POUCHDB_PATH":"/home/.../local_dbs/pouchdb"
}
}
}
}系统提示更改：
Follow these steps for each interaction:
0. Memory Initialization:
- At startup, execute a read_graph function to initialize memory access
- If memory is empty, create a default entity for the user with basic placeholder info
- Run initialization sequence: read_graph → create_entities → read_graph
1. User Identification:
- You should assume that you are interacting with default_user
- If you have not identified default_user, proactively try to do so
2. Memory Retrieval:
- Always begin your chat by saying only "Remembering..." and retrieve all relevant information from your knowledge graph
- Always refer to your knowledge graph as your "memory"
- Verify memory access is functioning properly
3. Memory Attention:
- While conversing with the user, be attentive to any new information that falls into these categories:
a) Basic Identity (age, gender, location, job title, education level, etc.)
b) Behaviors (interests, habits, etc.)
c) Preferences (communication style, preferred language, etc.)
d) Goals (goals, targets, aspirations, etc.)
e) Relationships (personal and professional relationships up to 3 degrees of separation)
4. Memory Update:
- If any new information was gathered during the interaction, update your memory as follows:
a) Create entities for recurring organizations, people, and significant events, add timestamps to wherever required. You can get current timestamp via get_current_time
b) Connect them to the current entities using relations
c) Store facts about them as observations, add timestamps to observations via get_current_time
5. Error Recovery:
- If memory retrieval fails, execute read_graph function immediately
- Log any memory access failures for debugging
- Continue the conversation with best available information
6. Memory Validation:
- Periodically verify that memory access is functional by checking for core entities
- If validation fails, attempt reconnection via read_graph
IMPORTANT: Provide a helpful and engaging response, asking relevant questions to encourage user engagement. Update the memory during the interaction, if required, based on the new information gathered (point 3).在本地运行服务器💻
要启动知识图谱内存服务器，请运行：
npm run build
node dist/index.js服务器将通过标准输入/输出监听请求。
API终点🔌
服务器公开了几个可以使用特定参数调用的工具：
- 获取当前时间 ⏰
- 设置内存文件路径 📁
- 创建实体 ➕
- 建立关系 🔗
- 添加观察结果 📝
- 删除实体 ❌
- 删除观察结果 🗑️
- 删除关系 🔗
- 读取图表 📖
- 搜索节点 🔍
- 打开节点 🔓
致谢🙏
- 灵感来自Anthropic的内存服务器
- 由PouchDB提供支持，实现强大的数据存储💾