# memory MCP server

Persistent agent memory paid per call via x402 USDC. Your wallet is your private memory namespace.

## At a glance

memory is an MCP server in the AI & Memory category. It is hosted remotely and connects over HTTP, and declares no required credentials. It exposes 8 tools, including memory_write, memory_search and memory_export. It scores D (33/100) on the MCP Skills Hub health score as of Oct 28, 2026.

## Install

### How to install memory in Claude Code

1. Add the server

```bash
claude mcp add --transport http memory https://mem.borisinc.com/mcp
```

2. Verify it's connected

```bash
claude mcp list
```

3. Sharing it with your team?

   Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

4. Use it in a session

   Ask Claude to use the tools this server exposes (e.g. memory_write, memory_search, memory_export). It discovers them automatically.

### How to install memory in Claude Desktop

1. Open your MCP config

   macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

2. Add this server

```json
{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mem.borisinc.com/mcp"
      ]
    }
  }
}
```

3. Why the wrapper?

   This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.

4. Restart Claude Desktop

   The tools appear under the 🔌 menu once the app reloads.

### How to install memory in Cursor

1. Create / edit .cursor/mcp.json in your project

```json
{
  "mcpServers": {
    "memory": {
      "url": "https://mem.borisinc.com/mcp"
    }
  }
}
```

2. Enable it

   Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

### How to install memory in Codex CLI

1. Add to ~/.codex/config.toml

```toml
[mcp_servers.memory]
command = "npx"
args = ["-y", "mcp-remote", "https://mem.borisinc.com/mcp"]
```

2. Why the wrapper?

   Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.

3. Run Codex

   Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

### How to install memory in Windsurf

1. Edit ~/.codeium/windsurf/mcp_config.json

```json
{
  "mcpServers": {
    "memory": {
      "serverUrl": "https://mem.borisinc.com/mcp"
    }
  }
}
```

2. Reload

   Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

### How to install memory in Cline

1. Open Cline → MCP Servers → Configure

   Adds to cline_mcp_settings.json.

2. Add the server

```json
{
  "mcpServers": {
    "memory": {
      "type": "streamableHttp",
      "url": "https://mem.borisinc.com/mcp"
    }
  }
}
```

### How to install memory in VS Code

1. Create .vscode/mcp.json

```json
{
  "servers": {
    "memory": {
      "type": "http",
      "url": "https://mem.borisinc.com/mcp"
    }
  }
}
```

2. Start it

   VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

## Tools

- `memory_write` — Store a memory permanently. Namespaced to YOUR paying wallet — your wallet is your private memory store. Semantic-indexed for later search. Optional supersedes=[ids] marks prior memories in your namespace as superseded by this one (excluded from search, still visible in export with their superseded_by id) — a Zep-style update-in-place without ever losing history. Paid: $0.001 per write via x402 (p
- `memory_search` — Semantic search over YOUR stored memories (payer-wallet namespace). Returns top-k by embedding similarity. Paid: $0.002 per search via x402.
- `memory_export` — Export memories in YOUR payer-wallet namespace (up to 1000/call, newest first; use offset to page through namespaces >1000). Your data is yours. Includes superseded_by so history is exportable. Paid: $0.01 via x402.
- `memory_import` — Bulk-write memories into YOUR namespace (max 200/call, content <=8k chars each). Accepts the exact shape memory_export emits, so a whole namespace can move in with one paid call. Embeds best-effort; missing embeddings are backfilled hourly. Paid: $0.01 flat via x402.
- `memory_forget` — Delete memories by id from YOUR namespace (or a namespace you hold a write/rw grant for). Max 100 ids per call. Paid: $0.001 per call via x402.
- `memory_write_free` — FREE (no payment): store a memory in YOUR namespace, proven by an EIP-191 personal_sign instead of an x402 payment. wallet_auth = base64 JSON {address,ts,signature} where signature = personal_sign of 'borismem-free:<address>:<ts>' (ts within 600s). Writes to the SAME namespace paid calls use. Capped at 1000 writes / rolling 30 days per wallet; over cap returns an error pointing to the paid tier.
- `memory_search_free` — FREE (no payment): semantic search over YOUR namespace, proven by an EIP-191 personal_sign. Same wallet_auth scheme as memory_write_free. Capped at 500 searches / rolling 30 days per wallet.
- `memory_stats` — FREE: count + last-write timestamp for any wallet namespace. Content is never returned on the free tier.

---

Source: https://mcp-skills-hub.vercel.app/mcps/com-borisinc-memory · MCP Skills Hub · data as of 2026-10-28T12:31:05Z