nazar256/memheaven

**MemHeaven is a self-hosted remote MCP memory server for ChatGPT and other cloud AI agents.**
It gives hosted AI clients searchable long-term memory you own, deployed on Cloudflare. MemHeaven is inspired by MemPalace's long-term-memory model while using a remote deployment shape for hosted clients.
**Deploy on a Cloudflare Free account. No VM, no Docker, no database admin.**
Free-tier limits apply; heavy usage may require paid Cloudflare usage.
**Quick links:** Quickstart · Getting started from zero · ChatGPT setup · Client compatibility · Security model · Behavior evals
What problem it solves
AI assistants are useful in the moment, but they often forget project context across chats, sessions, and tools.
Built-in memory features can help, but they are usually provider-owned and are not the same thing as an inspectable, searchable memory layer you control. Local-first memory tools are powerful too, but hosted clients like ChatGPT and other remote agents need a remote MCP server.
MemHeaven is for people who want:
- searchable memory they own
- inspectable and deletable stored context
- continuity for coding agents and other AI workflows across sessions
- a remote MCP deployment shape instead of a laptop-only setup
When MemHeaven fits
Choose MemHeaven when a hosted client or AI agent needs a searchable memory layer that persists outside the current chat:
- ChatGPT needs to retrieve project decisions, preferences, notes, or other durable context across chats.
- A remote MCP client cannot depend on a memory service running only on your laptop.
- Separate users or workflows need tenant-scoped access to stored context.
- You want to inspect, search, and delete the records held by your own deployment.
External memory, not a replacement for ChatGPT memory
MemHeaven does not change ChatGPT's built-in memory. It is a separate OAuth-protected MCP service that your client can call for context stored in your own deployment. There is no shared public MemHeaven instance: you operate the Worker, storage bindings, OAuth configuration, and access keys in your Cloudflare account.
ChatGPT long-term memory over remote MCP
If you want ChatGPT to use a searchable memory layer across chats without putting that memory in a shared third-party service, deploy MemHeaven in your own Cloudflare account and connect ChatGPT to your instance's /mcp endpoint. This external memory complements ChatGPT's built-in memory: you can inspect, search, and delete the records stored by your own deployment. See the ChatGPT setup and security model before connecting a client.
Why MemHeaven exists
- AI assistants forget project context across chats and sessions.
- Built-in memory is useful, but it is usually provider-owned and not an exact, searchable memory layer.
- Local-first memory tools are powerful, but hosted clients need remote MCP.
- Users want inspectable, searchable, deletable, portable memory.
- Coding agents need continuity across sessions, editors, and tools.
Cloudflare Free account is enough for personal use
MemHeaven is designed for personal use and small trusted-group usage on Cloudflare-managed services.
- **Worker** runs the HTTP server.
- **D1** stores relational metadata and indexes.
- **R2** stores drawer and diary bodies.
- **Vectorize** powers semantic vector search.
- **Workers AI** generates embeddings.
That means:
- no VM
- no Docker
- no database admin
- no long-running server process
Free-tier limits apply. MemHeaven does **not** promise unlimited free usage, enterprise uptime, or zero cost under every workload. Also note that some underlying Cloudflare services, especially Vectorize, have their own plan and usage constraints, so review the current Cloudflare pricing before a broad rollout.
Fastest happy path
Then connect your hosted client to:
When the authorization page opens, paste the printed raw_key.
If you want the hand-holding version, use docs/GETTING_STARTED_FROM_ZERO.md.
Supported / expected clients
| Client | Status | Notes |
| --- | --- | --- |
| ChatGPT | **Confirmed** | Manually verified end-to-end for the /mcp URL, OAuth authorization flow, and a mempalace_status tool call |
| Claude.ai hosted connectors | **Expected** | Known exact hosted callback is allowlisted, but public docs do not expose the URL and end-to-end verification is still needed |
| Local IDE / CLI MCP clients | **Expected** | Generic localhost / 127.0.0.1 / [::1] loopback OAuth callbacks are already allowed |