Vertiso Memory for Claude Code

Runs where your agents already work

Install in Claude Code

The same steps as the install guide, for this tool only: a live Marketplace listing where one exists, the public plugin repository, native HTTP MCP, then the local vmem bridge.

Vertiso Memory MCP URL

https://memory.vertiso.ai/mcp

This section is for the terminal CLI, which is installed separately from Claude Desktop. Install the complete plugin from Vertiso's public GitHub repository. It adds the remote MCP server and all four session skills.

Claude Code CLI plugin (GitHub, recommended)

/plugin marketplace add Vertiso/memory-claude
/plugin install vertiso-memory@vertiso

Start a new Claude Code CLI session after installation so the plugin and its skills are loaded.

Source and release notes: Vertiso/memory-claude .

MCP-only alternative. Add Vertiso Memory as a remote HTTP server, then run /mcp and choose Authenticate . Claude Code CLI opens your browser, completes OAuth, and refreshes the token automatically.

Add the remote server (OAuth, MCP only)

claude mcp add --transport http vertiso-memory https://memory.vertiso.ai/mcp
# then run /mcp in Claude Code CLI and choose Authenticate

Need a bearer token or the local vmem bridge?

Direct HTTP also accepts a bearer token, but stores that token in ~/.claude.json or the project .mcp.json.

Claude Code direct HTTP command (fallback)

claude mcp add vertiso-memory \
  --transport http https://memory.vertiso.ai/mcp \
  --header 'Authorization: Bearer <paste your token here>' \
  --header 'X-Agent-Source: agent:claude-code'

.mcp.json (fallback direct HTTP)

{
  "mcpServers": {
    "vertiso-memory": {
      "type": "http",
      "url": "https://memory.vertiso.ai/mcp",
      "headers": {
        "Authorization": "Bearer <paste your token here>",
        "X-Agent-Source": "agent:claude-code"
      }
    }
  }
}

For a local, headless bridge, run vmem mcp install claude-code. The bridge keeps its token in ~/.vmem and writes the user-scoped Claude configuration automatically.

~/.claude.json (vmem bridge)

{
  "mcpServers": {
    "vertiso-memory": {
      "command": "<run `which vmem` to get the absolute path>",
      "args": ["mcp", "serve", "--client", "claude-code"]
    }
  }
}

For project-scoped fallback config, add .mcp.json to .gitignore before pasting a real token.

Recommended: add a bootstrap instruction to your CLAUDE.md or AGENTS.md so your assistant registers with Vertiso Memory at the start of every session:

Bootstrap instruction

Vertiso Memory (vmem) is my persistent memory across every tool and session.

- Call the `hello` tool at the start of every session. Treat its primer
  as authoritative context, not a suggestion.
- `recall` before planning or answering anything that may depend on
  earlier context. Look it up instead of asking me to repeat it.
- `remember` durable decisions, preferences, constraints, and project
  state the moment they land. `update_memory` rather than writing a
  near-duplicate.
- Offer a handoff before the session ends, compacts, or moves to
  another tool.

Connected? Start a new conversation and say Hello. Your assistant greets you by name and mentions what it remembers. The standing instruction and the first conversation →

API token

Only the vmem bridge and the bearer-token fallbacks need one. OAuth clients sign in during the handshake instead.

Log in to get your token →

Power users: the vmem CLI

A native binary for working memory from the terminal, and a stdio-to-HTTP bridge for clients that cannot reach a remote server. It keeps your token in ~/.vmem instead of each app's config.

Install vmem

curl -fsSL https://memory.vertiso.ai/install.sh | sh

Every vmem command →

Ready when you are

Start building your memory layer.

Connect Claude, Codex, Antigravity, or any MCP-aware client. Your memory follows you everywhere.

Get started →

Your memory, inside Claude Code.

Decide it anywhere. Claude Code already knows.

Install in Claude Code

Start building your memory layer.