OwnMemory

app.ownmemory由 ownmemory.app 发布v0.2.2更新于 Oct 24, 2026

Encrypted memory for Claude, on a server you deploy to your own Cloudflare account.

发布方自己的服务：Memory.fit

已验证Streamable HTTP可网页运行云端与基础设施知识与记忆

服务详情

标识符: app.ownmemory/ownmemory
传输: Streamable HTTP
运行时: Web executable
信任: Verified
发布于: Oct 17, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此服务的命名空间属于 ownmemory.app，但其端点不在该域名下，因此发布者未必运行此服务。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/app.ownmemory%2Fownmemory.svg)](https://sourceweft.com/mcp/app.ownmemory%2Fownmemory?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

OwnMemory 是部署在你自己 Cloudflare 账户中的加密记忆服务器，让 Claude 跨对话和应用记住你。

可以做什么: 在对话开始时加载核心记忆，包括个人资料、偏好和近期工作，并设置记忆模式（逐步启用、仅用 OwnMemory 或两者并存）。按语义和关键词搜索记忆，支持英文、中文和混合文本，并按类别列出最近记忆。保存单条事实或一次导入最多 50 条，并检测重复。更新或删除记忆，保留带日期的历史记录和 30 天保留期，并审查相似记忆以便合并。在服务器的记忆页面浏览、编辑、新增和删除记忆，并将全部内容下载为 Markdown。
适用场景: 当你希望 Claude 跨对话和设备保留个人上下文，但不想把记忆交给第三方服务时使用。适合愿意自行运行 Cloudflare Worker 并保管自己加密密钥的用户。
运行要求: 需要在你自己的 Cloudflare 账户中运行的远程 MCP 端点，通过一键部署创建，需免费 Cloudflare 账户并连接 GitHub。需要 12 位以上的随机所有者代码、在浏览器中输入的通行短语，以及连接 Claude 时的 OAuth 登录。可选使用 Google Drive 代替 D1 存储，并可用 SEMANTIC_SEARCH 密钥控制嵌入。

安装前请注意

保存或搜索时，服务器和 Anthropic 会看到明文记忆内容。记忆用由通行短语派生的密钥加密，丢失通行短语或锁定密钥文件将无法访问。除非将 SEMANTIC_SEARCH 设为 off，语义搜索会把记忆文本发送到你账户内的 Cloudflare Workers AI。服务器可保存、更新和删除记忆，删除后数据保留 30 天。软件处于早期 v0.2，Claude 之外的客户端未经测试。

安装

在 SourceWeft 中

打开控制台中的 OwnMemory，将其添加到工作区。
为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。远程服务在工作区中配置后即可从网页运行时运行。

其他 MCP 客户端

参照仓库中的启动说明。

README

[OwnMemory]

OwnMemory lets Claude remember you across chats and devices, with the memories stored encrypted under a key only you hold, in storage you own.

Claude calls a remote MCP server running in your own Cloudflare account. The server encrypts each memory and stores it in a D1 database in that account (the one-click default) or in an OwnMemory folder in your Google Drive. It works in the official Claude apps on the web, iPhone and Android.

[Deploy to Cloudflare]

Get started: create a free Cloudflare account and connect GitHub to it first (steps), then click the button above, choose a random owner code of 12+ characters, and open your server's address to follow its four setup steps. About 5 minutes, on a free Cloudflare account. Full guide, including Google Drive storage: docs/setup.md.

Status: early (v0.2). Built and tested for Claude: on the web, iPhone and Android, and in Claude Code. Other MCP clients that support remote servers with OAuth should be able to connect, but are untested.

How your memories stay yours

[Key flow]

Your passphrase never leaves your browser. When you connect Claude, the passphrase page turns it into a key that unlocks a random 256-bit memory key. Only the locked copy of that key is stored, in your storage (keyinfo.json).
Every memory is encrypted (AES-256-GCM) before it is stored, in a file with a random name. Your storage provider and anyone with the files see only ciphertext.
The server keeps no key at rest. The memory key and your Google token live only inside the OAuth grant, which is encrypted with Claude's access token. The MCP handler is stateless: nothing is written to Durable Objects or logs.
Hard rules in code. Blocked categories, a pause switch, and a filter that refuses passwords, API keys and card numbers, whatever the AI decides.
Search by meaning, still private. Embeddings come from Cloudflare Workers AI in your own account and are stored encrypted like the memories. Set the SEMANTIC_SEARCH secret to off to keep memory text away from it; search then uses keywords only.
See and fix what it remembers. Your server's /memories page lets you browse, search, edit, add and delete memories, decrypted only in your browser.
No lock-in. Download all on the memories page gives you every memory as Markdown, and ownmemory.app/decrypt decrypts a downloaded copy in your browser, even without your server.

The one unavoidable exposure: the server and Anthropic see a memory's text while a save or search runs, because Claude sends plain text. Running the server yourself is the safeguard.

Who else could get at your memories, person by person, and how to keep them out: docs/security-model.md.

Tools Claude gets

Tool	What it does
`load_core_memories`	Called at the start of a chat: returns the memory mode, any message for you, and (in OwnMemory-only mode) your profile, preferences and recent work
`search_memories`	Search by meaning and keywords, English, Chinese or mixed (finds "What do I like to drink?" without shared words)
`list_memories`	Most recent memories, optionally by category
`save_memory`	Saves one fact, after the hard rules allow it; points out facts already saved, even when worded differently
`import_memories`	Saves up to 50 facts at once, for example everything Claude's built-in memory knows
`update_memory`	Changes a fact, keeping the previous wording as dated history
`delete_memory`	Deletes a memory; it stays 30 days in D1, or in the Drive trash
`review_memories`	Finds memories with the same wording or meaning, to merge
`set_memory_mode`	Records how you use OwnMemory alongside Claude's memory: ramp-up, OwnMemory only, or keep both

Repository layout

Path	What's there
`server/src/`	The Cloudflare Worker: OAuth and sign-in flow (`auth.ts`), passkey and authenticator sign-in on one-click servers (`gate.ts`, `factors.ts`), the memories page's API (`memories.ts`), MCP tools (`tools.ts`), storage backends D1 and Drive (`storage.ts`, `google.ts`), encrypted memory store (`store.ts`), memory format, search and duplicate checks (`format.ts`), memory modes and ramp-up (`settings.ts`), pages (`pages.ts`)
`server/public/unlock.js`, `home.js`, `memories.js`, `gate.js`	Scripts for the passphrase page, the setup wizard, the memories page and the passkey / authenticator sign-in step
`server/public/keys.js`, `memory-file.js`, `zip.js`	Encryption, the memory file format and the zip builder, shared by the browser, the Worker, the decrypt tool and `site/public/decrypt.html` (copies; `npm run sync-site`), so the format can't drift
`site/`	The ownmemory.app landing page and the decrypt page: static files, no data collected
`server/scripts/decrypt.mjs`	Local export to plain Markdown
`server/test/`	Unit tests (`npm test`) and a recall evaluation against real embeddings (`npm run eval`)
`docs/`	Setup guide, "Who can read your memories" and the key-flow diagram
`design/logo/`	Logo sources from the design canvas and PNG/SVG exports

Contributing, security and license

Contributions are welcome; see CONTRIBUTING.md. Contributors sign a short contributor license agreement.
Found a security problem? Please report it privately: SECURITY.md.
Licensed under the Apache License 2.0. "OwnMemory" and the OwnMemory logo are trademarks of the project and are not covered by the license; forks need a different name.

来源：README.md，提交 7559297