MemPalace
Local memory for agents: stores conversations and project files verbatim and retrieves them with semantic search over MCP
Install
npx skills add MemPalace/mempalaceInstalls only the skills; the agent then installs the CLI and MCP server via the mempalace skill.
This is third-party code. Review the repository files before installing.
What it does
MemPalace puts your agent conversation history and project files into a local index without summarizing or extracting facts. Data is structured: people and projects are wings, topics are rooms and original text sits in drawers, so searches can be scoped. The MCP server gives the agent tools for reading and writing memory, a temporal entity graph, agent diaries and task handoffs. Hooks for Claude Code, Codex and Cursor save sessions during work and before context compaction. The repository also ships skills for guided setup, search-before-answer recall and task delegation.
Who it is for. For people who work with agents on projects over time and want past decisions and discussions retrievable without cloud services.
Good fit when
- The agent forgets why a decision was made in the project
- You need to keep Claude Code sessions that otherwise expire after 30 days
- Several machines or agents should share memory through a hub
Not a fit when
- You want a short fact summary rather than verbatim storage
- Disk space is tight or Python 3.9+ is unavailable
Example request
Search memory for why we switched to GraphQL and take it into account in the planLimitations
Requires Python 3.9+ and about 300 MB for the embedding model; the first model download needs network access. Native Termux install is not supported. The only official sources are GitHub, PyPI and mempalaceofficial.com; the authors warn about impostor sites.
How to disable. Remove the mempalace MCP server from the agent config or the plugin via /plugin, then run uv tool uninstall mempalace. Palace data is stored locally and removed separately.
MCP
- Transport
- stdio
- Authentication
- not required
| Environment variables | |
|---|---|
| MEMPALACE_BACKEND | Vector backend: chroma, sqlite_exact, milvus, qdrant, pgvector and others. |
Security check
- Reads project files and session transcripts
- Hooks write data to the local database automatically
README in short
The README explains the MemPalace storage model and offers three install paths: skills with agent-guided setup, uv or pipx, and a Docker image with an MCP config example. It covers pluggable backends (ChromaDB by default, SQLite, Milvus, Qdrant, pgvector), the mine, search and wake-up commands, benchmark results with reproduction steps, the knowledge graph and auto-save hooks. MIT licensed.
FAQ
Do I need an API key?
No, core search runs locally without an LLM or keys. Embeddings can be moved to your own OpenAI-compatible server.
How do I import old Claude Code sessions?
Run mempalace mine ~/.claude/projects/ --mode convos.
Related
Open-source personal AI assistant on your own machine: answers in Telegram, Slack, Discord and WhatsApp, extended with skills and plugins
A self-improving agent from Nous Research with a TUI, messaging gateway, cron jobs and skills it writes itself
An open source coding agent for the terminal and desktop with build and plan modes
Open prompt library with a Claude Code plugin, MCP server and CLI: search, fetch and improve prompts and skills from an agent