| name | mempalace |
| description | MemPalace — mine projects and conversations into a searchable memory palace. Use when the user asks about MemPalace, memory palace, mining memories, searching memories, palace setup, wings, rooms, or drawers; or when they want to recall past work that may already be filed in their palace. |
MemPalace
A searchable memory palace for AI — mine projects and conversations, then search them semantically.
Prerequisites
Ensure mempalace is installed:
mempalace --version
If not installed (uv recommended):
uv tool install mempalace
Usage
MemPalace provides dynamic, version-correct instructions via the CLI. To get instructions for any operation:
mempalace instructions <command>
Where <command> is one of: help, init, mine, search, status.
Run the appropriate instructions command, then follow the returned instructions step by step.
Recalling past work
This skill covers setup, mining, and status. For questions about past
work, prior decisions, or people that may already be filed in the
palace, prefer the mempalace-recall skill — it enforces
search-before-answer so the agent reads the palace instead of guessing.
Cursor-specific notes
- The
mempalace-mcp server is auto-registered by this plugin. Once installed, all 33 MemPalace MCP tools (mempalace_search, mempalace_add_drawer, mempalace_diary_write, mempalace_check_duplicate, mempalace_diary_read, etc.) are available to the agent without any further configuration.
- For automatic background saving every N agent turns plus session-start memory recall, also install the Cursor hooks separately by running
hooks/cursor/install.sh --scope user from a cloned MemPalace repo. See website/guide/cursor-hooks.md for the full walkthrough.
- The recommended
agent_name when calling mempalace_diary_write from a Cursor session is cursor-ide (matches the precedent of claude-code and codex).