mempalace--mempalace
wehub-resource-sync
c3749daf48
Tests / test-linux (3.13) (push) Failing after 0s
Tests / test-linux (3.11) (push) Failing after 1s
Tests / lint (push) Failing after 0s
Tests / test-linux (3.9) (push) Failing after 1s
Docker / build (push) Failing after 1s
Docker / build-gpu (push) Failing after 2s
Tests / test-windows (push) Has been cancelled
Tests / test-macos (push) Has been cancelled
36 行
1.3 KiB
Markdown
36 行
1.3 KiB
Markdown
# OpenClaw Skill
|
|
|
|
MemPalace provides an official skill for [OpenClaw](https://github.com/openclaw/openclaw), making it trivial to give your ClawHub agents complete access to the palace's declarative memory and knowledge graph.
|
|
|
|
## Installation
|
|
|
|
The skill is built right into the `integrations/openclaw` directory of MemPalace.
|
|
|
|
You can add MemPalace as an MCP server to OpenClaw via the CLI:
|
|
|
|
```bash
|
|
openclaw mcp set mempalace '{"command":"python3","args":["-m","mempalace.mcp_server"]}'
|
|
```
|
|
|
|
Or by directly editing your OpenClaw configuration:
|
|
|
|
```json
|
|
{
|
|
"mcpServers": {
|
|
"mempalace": {
|
|
"command": "python3",
|
|
"args": ["-m", "mempalace.mcp_server"]
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
## How It Works
|
|
|
|
Once connected, OpenClaw agents receive all 34 tools along with the **Memory Protocol**—a strict behavioral guide indicating they should:
|
|
1. **Never guess**: Query `mempalace_search` or `mempalace_kg_query` before confidently answering.
|
|
2. **Keep an agent diary**: Maintain continuity between sessions by writing to `mempalace_diary_write`.
|
|
3. **Manage the Knowledge Graph**: Update declarative facts when things change using `mempalace_kg_add` and `mempalace_kg_invalidate`.
|
|
|
|
By connecting OpenClaw to MemPalace, you get both autonomous code execution and persistent, high-recall memory in the same workflow.
|