Walrus Memory MCP
# Walrus Memory Claude Code plugin
Walrus Memory gives Claude Code durable, user-owned memory. This plugin packages the published [`@mysten-incubation/memwal-mcp`](https://www.npmjs.com/package/@mysten-incubation/memwal-mcp) server with setup guidance, slash commands, and lifecycle hooks.
The MCP runtime, tests, and npm releases stay canonical in [`MystenLabs/MemWal/packages/mcp`](https://github.com/MystenLabs/MemWal/tree/dev/packages/mcp). This repository is plugin packaging only.
Publisher: [Mysten Labs](https://mystenlabs.com). Dashboard: [memory.walrus.xyz](https://memory.walrus.xyz). Docs: [Claude Code setup](https://docs.wal.app/walrus-memory/mcp/claude-code.html).
## Install
After the plugin is listed in the Claude plugin directory, install **Walrus Memory** from `/plugin` → Discover.
To load this repo locally for review:
```bash
claude plugin validate . --strict
claude --plugin-dir .
```
Then restart Claude Code or run `/reload-plugins`, and confirm `/plugin` and `/mcp` show `memwal`.
MCP-only (tools, no plugin hooks):
```bash
claude mcp add --scope user memwal -- npx -y @mysten-incubation/memwal-mcp@0.0.13 --label "Claude Code"
```
## Setup
```text
/memwal:setup
```
`memwal_login` opens the browser wallet flow and stores credentials at `~/.memwal/credentials.json` (mode `0600`). Do not paste that file or its private key into chat.
## Example prompts
1. `Connect Walrus Memory and confirm memwal_health is ok.`
2. `Remember that I use pnpm and TypeScript strict mode in this project.`
3. `What package manager and TypeScript settings do I prefer?`
## Commands
- `/memwal:setup`
- `/memwal:health`
- `/memwal:remember`
- `/memwal:recall`
- `/memwal:analyze`
- `/memwal:restore`
- `/memwal:logout`
## Authentication
This plugin uses local stdio MCP and delegate-key login. It does not use the hosted Claude custom-connector OAuth flow.
The hosted connector is a separate remote MCP surface at `https://relayer.memory.walrus.xyz/api/mcp`. See [`docs/usage/hosted-connector.md`](docs/usage/hosted-connector.md).
## Privacy and support
Walrus Memory encrypts memories with SEAL and stores them on Walrus. The local MCP process keeps a delegate private key on disk after login so it can sign relayer calls.
- Privacy policy: https://docs.wal.app/docs/legal/privacy
- Terms: https://docs.wal.app/docs/legal/walrus_general_tos
- Product docs: https://docs.wal.app/walrus-memory/mcp/claude-code.html
- Support: open an issue on this repository, or use the [Walrus Memory dashboard](https://memory.walrus.xyz)
## License
Apache-2.0
TDQS
Scored across 5 tools
Each tool serves a distinct purpose: login for authentication, remember for explicit saving, analyze for batch extraction, recall for searching, and restore for index maintenance. Although analyze and remember both create memories, their trigger conditions are clearly separated (passage processing vs. direct user request), preventing misselection.
All tools follow a uniform memwal_<verb> pattern using lowercase snake_case. The verb stems (analyze, restore, login, remember, recall) are consistent and predictable, making the naming highly coherent.
With only five tools, the surface is compact and focused on the essential operations of a personal memory system: authentication, writing, reading, batch processing, and maintenance. No tool feels redundant or extraneous.
The set covers authentication, creation, recall, and bulk ingestion, but lacks update and delete operations. For a memory system, the inability to forget or correct stored facts is a notable gap that could limit agent effectiveness.