메뉴
Recall protocol for MemPalace — search the palace before answering about past work, prior decisions, people, or projects. Use when the user asks what was decided, what happened before, who someone is, what was discussed last time, or anything that may already be filed in their memory palace.
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.
Recall protocol for MemPalace — search the palace before answering about past work, people, projects, or prior decisions. Apply when the user asks what was decided, what happened before, who someone is, what was discussed last time, or anything that may already be filed in their memory palace; or when mempalace-recall is invoked. Complements the mempalace setup skill and requires the mempalace-mcp server.
Recall protocol for MemPalace — search the palace before answering about past work, people, projects, or prior decisions. Apply when the user asks what was decided, what happened before, who someone is, what was discussed last time, or anything that may already be filed in their memory palace; or when mempalace-recall is invoked. Complements the mempalace setup skill and requires the mempalace-mcp server.
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 — mine projects and conversations into a searchable memory palace. Use when asked about mempalace, memory palace, mining memories, searching memories, or palace setup.
MemPalace — Local AI memory with 96.6% recall. Semantic search, temporal knowledge graph, palace architecture (wings/rooms/drawers). Free, no cloud, no API keys.
| name | mempalace-recall |
| description | Recall protocol for MemPalace — search the palace before answering about past work, prior decisions, people, or projects. Use when the user asks what was decided, what happened before, who someone is, what was discussed last time, or anything that may already be filed in their memory palace. |
| allowed-tools | Bash |
Search-before-answer protocol for MemPalace. Read the user's memory
palace before answering anything that may already be filed there,
instead of guessing from model memory. This complements the mempalace
skill (install / mine / status); this one covers recall only.
mempalace --version
If the mempalace_* MCP tools are not available, tell the user the
server is not connected and point them at the mempalace skill or
/init. Do not silently fall back to answering from model memory.
Search the palace before answering whenever the user asks about something that may be filed:
Skip recall for pure greenfield work with no memory relevance (renaming a variable, fixing a typo). Recall is question-driven, not reflexive.
mempalace_search first. Use mempalace_kg_query
for relational or time-bound facts.mempalace_diary_write (skip if a background hook already saved).mempalace_kg_invalidate the old fact, then
mempalace_kg_add the new one.mempalace status or re-running /init; never fall back to guessing.The canonical protocol, shared across all MemPalace integrations, lives
in integrations/shared/recall-protocol.md.