MemPersist MCP server

Mempersist

Mempersist is a clean-room, Cloudflare-native long-term memory service for AI conversations. It preserves original ChatGPT exports and normalized conversation graphs in R2, catalogs them in D1, builds disposable lexical and semantic indexes, and exposes compact retrieval and intentional writes through MCP.

It does not silently capture ChatGPT traffic, extract replacement “facts,” provide a SaaS billing layer, or make search indexes canonical. “Unlimited” means no application message quota; Cloudflare limits and billing still apply.

Architecture

ChatGPT conversations.json / MCP writes
                  |
          validation + IDs
                  |
          R2 canonical archive  <------ export / recovery
                  |
             D1 catalog
                  |
        Cloudflare Queues
          /             \
   D1 FTS5          Workers AI BGE-M3 -> Vectorize
          \             /
       normalized hybrid search
                  |
       HTTP + OAuth-protected MCP

R2 is the source of truth. D1 holds operational metadata and the derived FTS representation. Vectorize is disposable. A canonical write succeeds before indexing is queued, and an indexing failure never reports that durable memory was lost.

See ARCHITECTURE.md, SECURITY.md, and docs/operations-and-recovery.md.

Prerequisites

• WSL2/Linux, Node.js 22+, Yarn 1.22, and Wrangler 4.x
• A Cloudflare account with Workers, D1, R2, Vectorize, Workers AI, and Queues available
• Wrangler OAuth authentication: yarn wrangler whoami

Use Yarn only.

Setup

yarn install
cp .dev.vars.example .dev.vars
yarn types:bindings
yarn db:migrate:local
yarn dev

Set a long random MEMORYAPITOKEN in .dev.vars. Local D1 and R2 are simulated; Workers AI and Vectorize bindings are remote in the main configuration. Unit and integration tests do not call remote AI.

Cloudflare provisioning

Provisioning is intentionally manual and must be explicitly authorized. Follow docs/cloudflare-resources.md, then add the real D1 database_id returned by Wrangler to wrangler.jsonc. Never invent IDs or reuse unrelated account resources.

Set the production secret without putting it in source:

yarn wrangler secret put MEMORY_API_TOKEN

Apply migrations and deploy only after review:

yarn db:migrate:remote
yarn deploy:dry-run
yarn deploy

ChatGPT import

Export data from ChatGPT, extract conversations.json, then:

MEMPERSIST_URL=http://localhost:8787 \
MEMPERSIST_TOKEN='your-token' \
yarn import:chatgpt /path/to/conversations.json

Files up to 16 MiB use direct streaming upload. Larger files use 16 MiB R2 multipart parts. The Worker hashes the completed object, preserves it unchanged, detects exact duplicate exports, and processes at most 25 conversations per queue turn. Check progress with:

MEMPERSIST_TOKEN='your-token' yarn import:status <import-id>

See docs/chatgpt-import.md.

MCP

The Streamable HTTP endpoint is https:///mcp. Interactive clients such as ChatGPT use OAuth 2.1 authorization-code flow with PKCE: the consent page takes an email, sends a single-use magic link, and completes the connection only after the link is opened. Existing emails reconnect to their archive; a new archive is created after the first link. The owner archive is bound to vhie1046@gmail.com across all of its namespaces (personal, astaraaltv2, coding/mempersist, test/mempersist-blackbox); entering that email reconnects to the same data. Each account can own multiple namespaces, and the same namespace name may exist in different accounts with fully separated data. Developer scripts and the CLI may keep sending MEMORYAPITOKEN as a bearer token for the owner archive.

Shortened. The full README is on GitHub.