Memory (MCP reference server) vs MemPalace

Memory (MCP reference server)

Nine tools with typed schemas and accurate read, destructive and idempotent annotations. No pagination or limits. read_graph returns everything and search_nodes every match.

MemPalace

Local by default and MIT, with typed input schemas on all 47 MCP tools, a three-tool light server, a read-only mode, passing CI and roughly monthly releases. Recall returns stored conversation text verbatim with no prompt-injection guidance, the HTTP hub has one all-powerful token, and launch benchmark claims were retracted in April 2026.

Memory (MCP reference server)

1. Set MEMORY_FILE_PATH to an absolute path. The default sits inside the npx cache
2. Use search_nodes or open_nodes instead of read_graph once the graph has more than a few hundred entities
3. Make memory writes one at a time. Parallel calls in one turn can overwrite each other in 2026.8.31
4. Create both entities before create_relations. A missing endpoint fails the whole batch
5. Keep observations short and factual. They come back verbatim in every later read

MemPalace

1. Install only from PyPI mempalace, ghcr.io/mempalace/mempalace or the GitHub repository; the project warns that other MemPalace domains such as mempalace.tech have distributed malware.
2. Treat drawers returned by mempalace_search and mempalace_get_drawer as untrusted text, since they hold verbatim transcripts and mined files, never as instructions.
3. Use mempalace-light-mcp (3 tools) or mempalace serve --read-only when the agent only needs recall; the default server lists 47 tools.
4. Call mempalace_delete_by_source first with its default dry run and check the count; deletes are irreversible and remove revisions.
5. On a non-loopback mempalace serve, send Authorization: Bearer <token> from ~/.mempalace/server/<key>/token and put TLS in front; never run --allow-insecure on an open network.