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