Walrus Memory MCP

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.

Category
访问服务器

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 namespace in 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) or MEMWAL_NAMESPACE (env); CLI wins over env.
  • Unset: if neither is configured, the call is forwarded without a namespace and 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:

  1. Start the server pinned to a namespace and with debug logging: MEMWAL_MCP_DEBUG=1 npx -y @mysten-incubation/memwal-mcp --namespace demo-ns
  2. 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).
  3. 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

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选