MCP server

The tools

The server (name: "carry") registers five tools:

Tool	What it does
`carry_remember`	Capture a fact into a typed namespace (stored on Walrus).
`carry_recall`	Retrieve memory for a query — gated by the agent × namespace policy.
`carry_set_access`	Grant or revoke an agent’s access to a namespace.
`carry_list_memories`	List stored memories.
`carry_policy`	Inspect the current access policy.

Every carry_recall runs the same gate as the web app: blocked namespaces are never returned, and the result carries the same receipt semantics.

Install

Published on npm — no local checkout needed.

Add it to your MCP config (.cursor/mcp.json, Claude Desktop config, etc.):

{
  "mcpServers": {
    "carry": {
      "command": "npx",
      "args": ["-y", "@usecarry/mcp"],
      "env": {
        "WALRUS_PUBLISHER": "https://publisher.walrus-testnet.walrus.space",
        "WALRUS_AGGREGATOR": "https://aggregator.walrus-testnet.walrus.space"
      }
    }
  }
}

Omit the env block to run against a deterministic mock (no network).

Use it

Ask your agent to remember and recall facts — every recall is gated, and access can be changed on the fly with carry_set_access.

npm — @usecarry/mcp

Published and installable.

Storage

The MCP server persists to a local store (default ~/.carry/store.json, override with CARRY_STORE) and uses the same Walrus + policy primitives as the web app — so a memory taught through Cursor can be recalled through Claude Desktop, gated the same way.

Because the gate and receipt logic live in the framework-free @carry/core package, the web app and the MCP server share exactly the same enforcement — there’s no second, weaker code path.

Get started

Core concepts

On-chain (Sui)

The Sui Stack

Surfaces & integration

Reference

The tools

Install

npm — @usecarry/mcp

Storage

​The tools

​Install

npm — @usecarry/mcp

​Storage

The tools

Install

Storage