
Mempalace
Attach project-scoped memory to Claude Code through the MemPalace MCP server and lifecycle hooks so sessions recall decisions without re-pasting notes.
Overview
Mempalace-dev is a plugin marketplace for the Build phase that delivers project memory for Claude Code via MemPalace MCP and session lifecycle hooks.
What is this marketplace?
- mempalace plugin with MemPalace MCP integration for structured project memory
- Lifecycle hooks to persist and reload context across Claude Code sessions
- Local development marketplace layout (mempalace-dev) for the Claude plugin path
- Single-plugin bundle focused on memory—not a general skills anthology
- Marketplace contains 1 plugin: mempalace (MCP + lifecycle hooks).
What problem does it solve?
Claude Code forgets prior project decisions between sessions unless you manually restate context or maintain ad-hoc note files.
Who is it for?
Solo developers who want MCP-driven, repo-tied memory in Claude Code without folding an entire multi-tool workspace product.
Skip if: Teams that forbid MCP servers, avoid hook-based extensions, or only need generic skills with no persistent memory layer.
What do I get? / Deliverables
After install, hooks and MCP-backed MemPalace memory let the agent reload project-specific context as you iterate on the same codebase.
- mempalace plugin installed with MCP and hook integration
- Project-scoped memory channel usable across Claude Code sessions on that repo
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Project memory plugins are installed when you shape how the agent remembers repo context—primary shelf is Build agent-tooling with effects across later phases. MemPalace exposes MCP plus hooks, which is agent extension plumbing rather than backend APIs or launch distribution.
How it compares
MCP-backed project memory plugin, not a cloud workspace sync marketplace like Memlin or a filesystem CLI skill.
Common Questions / FAQ
Who is mempalace for?
Indie builders using Claude Code who want MemPalace MCP and hooks to keep project memory attached to one codebase across sessions.
When should I use mempalace?
Use it while setting up agent tooling at the start of a multi-week project or when chat amnesia is costing you rework—not for throwaway spikes with no memory needs.
How do I add mempalace to my agent?
Add the laozhong86/mempalace marketplace in Claude Code, install the mempalace plugin from plugins/claude/mempalace, run or connect MemPalace MCP per plugin docs, and enable lifecycle hooks in your project.