Pim Messelink
9f5b8f5fd6
The MCP server config used `python -m mempalace.mcp_server` which fails when mempalace is installed via pipx or uv, since the system python cannot find the module in the isolated venv. Adding a `mempalace-mcp` console_scripts entry point ensures the MCP server works regardless of installation method (pip, pipx, uv, conda). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
28 lines
583 B
Markdown
28 lines
583 B
Markdown
# MCP Integration — Claude Code
|
|
|
|
## Setup
|
|
|
|
Run the MCP server:
|
|
|
|
```bash
|
|
mempalace-mcp
|
|
```
|
|
|
|
Or add it to Claude Code:
|
|
|
|
```bash
|
|
claude mcp add mempalace -- mempalace-mcp
|
|
```
|
|
|
|
## Available Tools
|
|
|
|
The server exposes the full MemPalace MCP toolset. Common entry points include:
|
|
|
|
- **mempalace_status** — palace stats (wings, rooms, drawer counts)
|
|
- **mempalace_search** — semantic search across all memories
|
|
- **mempalace_list_wings** — list all projects in the palace
|
|
|
|
## Usage in Claude Code
|
|
|
|
Once configured, Claude Code can search your memories directly during conversations.
|