Walrus Memory MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMWAL_WEB_URL | No | Override the web app URL used during login. | |
| MEMWAL_MCP_DEBUG | No | Enable verbose stderr logging. Set to '1' to enable. | |
| MEMWAL_NAMESPACE | No | Default memory namespace applied when the agent omits one. | |
| MEMWAL_SERVER_URL | No | Override the relayer base URL. | |
| MEMWAL_CLIENT_LABEL | No | Friendly delegate-key label shown in Walrus Memory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memwal_rememberA | Save a fact to the user's Walrus Memory personal memory. Call ONLY when the user explicitly asks to remember/save something. Pass the full, detailed text — never summarize. |
| memwal_recallA | Search the user's Walrus Memory for facts relevant to a query. Returns matching memories ranked by relevance. |
| memwal_analyzeB | Extract memorable facts from a passage of text (preferences, habits, biographical info, constraints) and save each as a separate Walrus Memory memory. |
| memwal_restoreA | Re-index a namespace from Walrus blobs back into the relayer's search index. Returns counts and truncated status; call again with a higher limit when truncated=true. |
| memwal_loginA | Sign this MCP client into your Walrus Memory account by opening a browser. Run once when the agent reports Walrus Memory is not signed in. Opens the dashboard in the default browser, waits for wallet approval, then writes credentials to ~/.memwal/credentials.json. Other memwal_* tools become usable on the next call after a successful login. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.