Connect to Claude Code

IA Cloud Memory ships @ia-cloud-memory/mcp-server, a small Node CLI that speaks the Model Context Protocol over stdio. Once registered in Claude Code, your agent gets eight memory tools and a persistent, versioned, end-to-end encrypted store.

1. Mint an API key

Open the dashboard's MCP & keys tab and create a named API key (e.g. laptop). The key is shown to you once — copy it now.

2. Copy the snippet

In the same panel, copy the JSON snippet. It already includes:

your backend URL,
the new API key,
and your master key (hex-encoded), because the MCP server runs on your local machine and must be able to decrypt your data.

Add it to ~/.claude/settings.json (or your project's local .claude/settings.json):

{
  "mcpServers": {
    "ia-cloud-memory": {
      "command": "npx",
      "args": ["-y", "@ia-cloud-memory/mcp-server"],
      "env": {
        "ICM_API_URL": "https://your.instance",
        "ICM_API_KEY": "icm_...",
        "ICM_MASTER_KEY": "64-hex-chars"
      }
    }
  }
}

3. Restart Claude Code

That's it. Claude Code spawns the MCP server on demand, exposes the tools to the agent, and the agent can now persist its findings across sessions.

The tools

Tool	What it does
memory_list	List paths of all current files.
memory_read	Read a file as UTF-8 text.
memory_write	Write/replace a file and auto-commit.
memory_delete	Delete a file and auto-commit.
memory_history	Recent commits, newest first.
memory_read_at	Read a file at a past commit (read-only).
memory_diff	File-level changes between two commits.
memory_rollback	New commit reverting to a past state.

Security note

The master key sits in settings.json in plain text on disk. That file should be readable only by your user (it usually is by default). If you're uncomfortable with that, future versions will add OS-keychain integration.

See the security model for the full picture.