Memory Lab 2sep — DevOps skill for Claude Code

memory-lab-2sep — one owner's memory MCP on Cloudflare Workers, with a ledger of who called what from where

[](https://deploy.workers.cloudflare.com/?url=https://github.com/Soul-Brews-Studio/memory-lab-2sep)

Built 2026-09-02 for the 20:30 (+07) workshop "Memory ทำจริงได้ยังไงบ้าง — 5 มุม". Live instance: · MCP endpoint `…/mcp`. Written by an Oracle — AI speaking as itself (Rule 6). Every number below was measured today; the raw outputs are in [`out/`](out/). The same report as one self-contained page: [`docs/report.html`](docs/report.html) (open it locally; images embedded).

The Deploy button needs the source repository to be public — it is. The button path was not itself click-tested; the live instance was produced by `just deploy` from a checkout, which uses the same `wrangler.jsonc`. Deploying your own copy gives you your own Worker, your own D1, and your own secrets; the instance named below is the author's.

What it is

One Cloudflare Worker, one D1 database, **zero runtime dependencies**. It answers three questions at once:

Question	Answer	Where
Can memory be one click?	Worker + D1 provisioned by the Deploy button; schema created lazily on first request, so there is no migration step to run in Cloudflare's build container	wrangler.jsonc, src/schema.ts
Can claude.ai install it?	OAuth 2.1 with Dynamic Client Registration + PKCE S256, hand-rolled (the digger-wiki / Arra pattern), plus a static bearer for Claude Code / Codex / curl	src/oauth.ts, src/auth.ts
Who is connected, which method, from where?	Two D1 tables written per request via waitUntil: clients (one row per client) and calls (one row per JSON-RPC method). No Durable Object, no socket, no stream — a refresh is the live view	src/track.ts

Nine MCP tools: `remember`, `recall`, `read_memory`, `forget`, `list_memories`,