Walrus Memory MCP
Enables MCP clients to connect to Walrus Memory for persistent memory operations like remember, recall, analyze, and restore, with browser-based wallet login and local credential storage.
README
Walrus Memory MCP
Walrus Memory MCP is a stdio Model Context Protocol server for Walrus Memory. It lets MCP clients such as Cursor, Claude Desktop, Antigravity, and Claude Code connect to the Walrus Memory relayer without manually configuring remote headers or auth tokens.
On first use, the package advertises a memwal_login tool to the MCP client. The agent can call it inline — no separate CLI command needed. The tool opens a browser-based wallet login flow and stores local credentials at ~/.memwal/credentials.json. A matching memwal_logout tool clears the saved credentials.
Quick Start
Add Walrus Memory MCP to your MCP client config:
{
"mcpServers": {
"memwal": {
"command": "npx",
"args": ["-y", "@mysten-incubation/memwal-mcp"]
}
}
}
Login
Run the login flow manually:
npx -y @mysten-incubation/memwal-mcp login
The command opens your browser, asks you to connect your Sui wallet, and saves credentials locally.
Commands
memwal-mcp
memwal-mcp login
memwal-mcp --logout
memwal-mcp --help
Options
Use CLI flags or environment variables to override the default Walrus Memory endpoints.
| CLI flag | Environment variable | Description |
|---|---|---|
--relayer <url> |
MEMWAL_SERVER_URL |
Override the relayer base URL. |
--web-url <url> |
MEMWAL_WEB_URL |
Override the web app URL used during login. |
--label <text> |
MEMWAL_CLIENT_LABEL |
Friendly delegate-key label shown in Walrus Memory. |
--namespace <name> (alias --ns) |
MEMWAL_NAMESPACE |
Default memory namespace applied when the agent omits one. |
Enable verbose stderr logging with MEMWAL_MCP_DEBUG=1.
Default Namespace
By default the MCP tool schemas expose an optional namespace argument and the
agent has to pass it on every memwal_remember / memwal_recall /
memwal_analyze call (and memwal_restore requires it). Set a default once in
your client config instead:
{
"mcpServers": {
"memwal": {
"command": "npx",
"args": ["-y", "@mysten-incubation/memwal-mcp", "--namespace", "work"]
}
}
}
Or with an environment variable (e.g. Claude Desktop / Codex env blocks):
{
"mcpServers": {
"memwal": {
"command": "npx",
"args": ["-y", "@mysten-incubation/memwal-mcp"],
"env": { "MEMWAL_NAMESPACE": "work" }
}
}
}
Resolution and precedence:
- Per-call wins: an explicit, non-empty
namespacein a tool call is always used as-is — the configured default never overrides it. - Configured default: when the agent omits
namespace, the package injects--namespace(CLI) orMEMWAL_NAMESPACE(env); CLI wins over env. - Unset: if neither is configured, the call is forwarded without a
namespaceand the relayer applies its own"default"namespace.
memwal_restore still advertises namespace as required in its schema, so
agents normally pass one explicitly. If a default is configured and the agent
calls memwal_restore without a namespace, the configured default is filled
in the same way.
Verifying namespace injection
No automated test runner ships with this package (consistent with the rest of the monorepo). To verify manually:
- Start the server pinned to a namespace and with debug logging:
MEMWAL_MCP_DEBUG=1 npx -y @mysten-incubation/memwal-mcp --namespace demo-ns - From your MCP client, ask the agent to remember a fact without
specifying a namespace, then recall it without a namespace — the recall
should return that fact (both landed in
demo-ns). - Ask the agent to recall with an explicit different namespace
(e.g.
other) — it should not return the fact, proving the per-call value overrode the default.
The injection itself is the pure, exported applyDefaultNamespace(msg, ns)
function in src/bridge.ts if you want to assert it directly.
Environment Presets
memwal-mcp --prod
memwal-mcp --staging
memwal-mcp --local
You can also pass explicit URLs:
{
"mcpServers": {
"memwal": {
"command": "npx",
"args": [
"-y",
"@mysten-incubation/memwal-mcp",
"--relayer",
"https://relayer-staging.memory.walrus.xyz"
]
}
}
}
Credential Storage
Credentials are stored locally in ~/.memwal/credentials.json. To remove them:
npx -y @mysten-incubation/memwal-mcp --logout
License
Apache-2.0
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.