mvalentsev
c4baceccb4
Follow-up to #766 which covers version.py, pyproject.toml, README, CHANGELOG, and CONTRIBUTING. These 11 files still had the old org name in URLs: - website/ (VitePress config + 6 docs pages) - .claude-plugin/ (plugin.json repository, README marketplace command) - .codex-plugin/ (plugin.json URLs, README links) Author name fields are intentionally unchanged.
39 lines
1.0 KiB
Markdown
39 lines
1.0 KiB
Markdown
# Claude Code Plugin
|
|
|
|
The recommended way to use MemPalace with Claude Code — native marketplace install.
|
|
|
|
## Installation
|
|
|
|
```bash
|
|
claude plugin marketplace add MemPalace/mempalace
|
|
claude plugin install --scope user mempalace
|
|
```
|
|
|
|
Restart Claude Code, then type `/skills` to verify "mempalace" appears.
|
|
|
|
## How It Works
|
|
|
|
With the plugin installed, Claude Code automatically:
|
|
- Starts the MemPalace MCP server on launch
|
|
- Has access to all 19 tools
|
|
- Learns the AAAK dialect and memory protocol from the `mempalace_status` response
|
|
- Searches the palace before answering questions about past work
|
|
|
|
No manual configuration needed. Just ask:
|
|
|
|
> *"What did we decide about auth last month?"*
|
|
|
|
## Alternative: Manual MCP
|
|
|
|
If you prefer manual setup over the marketplace plugin:
|
|
|
|
```bash
|
|
claude mcp add mempalace -- python -m mempalace.mcp_server
|
|
```
|
|
|
|
Both approaches give identical functionality. The plugin approach handles server lifecycle automatically.
|
|
|
|
## Hooks
|
|
|
|
Set up [auto-save hooks](/guide/hooks) to ensure memories are saved automatically during long conversations.
|