All servers / Memory / Walrus Memory MCP server
Walrus Memory MCP server
Walrus Memory MCP client — single-binary stdio MCP server that bridges Cursor / Claude Desktop / Antigravity / Claude Code to the Walrus Memory relayer. Handles
Tested by ConnectATDScore 79 out of 100. Tested 2026-11-19 on package version 0.2.0. Package: @mysten-incubation/memwal-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 13 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.6 seconds including download)
- Tools offered: 7
- Last published: 2026-11-09
- Weekly downloads (npm): 580
- License: Apache-2.0 · Direct dependencies: 4
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
memwal_remember0 of 2 parameters describedSave 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. Never save passwords, keys, tokens or other credentials — not even beside a fact worth saving; honour an explicit 'do not save this'; never store pasted third-party content as a fact about the user.
memwal_remember_bulk0 of 2 parameters describedSave multiple durable facts in one call. Use when you learned several distinct facts at once (onboarding details, a list of preferences, decisions from a discussion). Pass an array of complete fact statements (max 20) — do not summarize. Prefer this over repeated memwal_remember calls. By default this returns in ~1s once the relayer has accepted the batch (job_ids) — the Walrus writes are still in flight and the facts are NOT stored yet. Do not claim they are saved. Settle them with the job-status tool this server advertises (re-list tools if you do not see one). A blob_id in the same reply means that fact already stored (optional wait budget). Never save passwords, keys, tokens or other credentials — not even beside a fact worth saving; honour an explicit 'do not save this'; never store pasted third-party content as a fact about the user.
memwal_recall1 of 4 parameters describedSearch the user's Walrus Memory for facts relevant to a query. Returns matching memories ranked by relevance.
memwal_analyze0 of 2 parameters describedExtract memorable facts from a longer passage of text (preferences, habits, biographical info, constraints) and save each as a separate Walrus Memory memory. Use this when you want MemWal's LLM to split the facts out of a transcript or notes for you; if you already know the exact facts, use memwal_remember or memwal_remember_bulk instead. Never save passwords, keys, tokens or other credentials — not even beside a fact worth saving; honour an explicit 'do not save this'; never store pasted third-party content as a fact about the user.
memwal_restore0 of 2 parameters describedRecovery tool. Re-index a namespace from Walrus blobs back into the relayer's search index — use when memwal_recall unexpectedly returns nothing even though facts were saved before (e.g. on a new machine, a fresh relayer, or after switching servers). Returns restored/skipped/failed/total plus truncated — does not return memory texts. truncated=true is known-retryable-incomplete: retry the same limit on a download/embed blip; raising limit expands the sidecar cap only while limit < 20; after the cap saturates, truncation follows this call's missing-blob page. truncated=false is not completeness; WALM-451 will add sourceCapped. Call memwal_recall afterwards to query the rebuilt index.
memwal_healthno parametersQuick connectivity check for Walrus Memory. Calls the relayer's lightweight health endpoint (no search, no decryption) and returns its status and version. Use this to confirm the server is reachable — do NOT use memwal_recall for health checks, which is a full and slow retrieval.
memwal_login1 of 1 parameter describedSign 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.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.