Vertiso Memory for Cursor

Runs where your agents already work

Install in Cursor

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

For the complete plugin with all four session skills, clone Vertiso's public GitHub repository and copy it into Cursor's local plugin directory.

Cursor plugin source (GitHub, recommended)

git clone https://github.com/Vertiso/memory-cursor.git
mkdir -p ~/.cursor/plugins/local
cp -R memory-cursor/vertiso-memory ~/.cursor/plugins/local/vertiso-memory
# Restart Cursor or run "Developer: Reload Window"

Use a physical copy. Cursor rejects a symlink whose target is outside its local plugin directory. Source and release notes: Vertiso/memory-cursor .

MCP-only alternative. Click Add MCP server to Cursor , or open Settings → Tools & MCP → New MCP Server . Cursor opens your browser for OAuth. This connects memory tools without the bundled skills.

Add MCP server to Cursor MCP only — bundled skills not included

New MCP Server (OAuth, MCP only)

Name:  Vertiso Memory
URL:   https://memory.vertiso.ai/mcp

Need a bearer token or the local vmem bridge?

Direct HTTP also accepts a bearer token stored in ~/.cursor/mcp.json or the project's .cursor/mcp.json:

~/.cursor/mcp.json direct HTTP (fallback)

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

For a local bridge that keeps its token in ~/.vmem, run vmem mcp install cursor. It writes the user-scoped MCP configuration automatically.

~/.cursor/mcp.json (vmem bridge)

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

Recent Cursor builds support the OAuth connect flow directly; older builds can fall back to the vmem bridge or direct HTTP. Restart Cursor's Composer (or run MCP: Reload servers from the command palette) to pick up the new server.

Recommended: add a bootstrap instruction to your Cursor Rules (a User Rule or a project rule) 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 Cursor.

Decide it anywhere. Cursor already knows.

Install in Cursor

Start building your memory layer.