Bring MemPalace-style long-term memory to ChatGPT and remote AI agents.
Most knowledge and memory work still happens through a UI a human drives. Memheaven MCP server moves it into the conversation instead. Bring MemPalace-style long-term memory to ChatGPT and remote AI agents.
MemHeaven is a self-hosted remote MCP memory server that gives hosted AI clients searchable long-term memory you own.
The server publishes 13 tools. What each one is for:
Built — in memory is useful, but it is usually provider-owned and not an exact, searchable memory layerLocal — first memory tools are powerful, but hosted clients need remote MCPAccess-key — gated consent page backed by stateless JWT auth artifactsTenant — scoped drawer, diary, knowledge-graph, and tunnel storageMemPalace — compatible mempalace_* tool surface, including adapted local-only toolsWorker — safe semantic search using Workers AI embeddings + Vectorize + R2/D1 hydrationJWT_SIGNING_SECRET — TOKEN_ENCRYPTION_KEYHosted — client callback support stays narrow and contract-driven. Other clients may need explicit callback allowlist additions before they work end-to-endClient — StatusChatGPT — ConfirmedMethod — PathGET — /Configuration is passed through the environment: AUTH_KEY_PEPPER, MEMHEAVEN_BEARER_TOKEN, JWT_SIGNING_SECRET, TOKEN_ENCRYPTION_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
wrangler authenticated against the target Cloudflare accountBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Memheaven's toolset — Built, Local, Access-key and 10 more — is a fair guide to whether it matches your workflow. It is maintained by nazar256; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| 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. |
| Access-key | gated consent page backed by stateless JWT auth artifacts. |
| Tenant | scoped drawer, diary, knowledge-graph, and tunnel storage. |
| MemPalace | compatible mempalace_* tool surface, including adapted local-only tools. |
| Worker | safe semantic search using Workers AI embeddings + Vectorize + R2/D1 hydration. |
| JWT_SIGNING_SECRET | TOKEN_ENCRYPTION_KEY |
| Hosted | client callback support stays narrow and contract-driven. Other clients may need explicit callback allowlist additions before they work end-to-end. |
| Client | Status |
| ChatGPT | **Confirmed** |
| Method | Path |
| GET | / |
| POST | /register |
{
"mcpServers": {
"memheaven": {
"command": "npx",
"args": ["-y", "wrangler"],
"env": {
"AUTH_KEY_PEPPER": "your-value",
"MEMHEAVEN_BEARER_TOKEN": "your-value",
"JWT_SIGNING_SECRET": "your-value",
"TOKEN_ENCRYPTION_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
wrangler authenticated against the target Cloudflare account| Variable | Description | Required |
|---|---|---|
| AUTH_KEY_PEPPER | Credential the server authenticates with. | Yes |
| MEMHEAVEN_BEARER_TOKEN | Credential the server authenticates with. | Yes |
| JWT_SIGNING_SECRET | Credential the server authenticates with. | Yes |
| TOKEN_ENCRYPTION_KEY | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.