Vertiso Memory for Antigravity

Your memory, inside Antigravity.

Antigravity 2 connects over remote MCP with browser OAuth. Antigravity 1 goes through the vmem bridge.

Runs where your agents already work

One memory, every agent

Decide it anywhere. Antigravity already knows.

What you settle in one tool is on hand in Antigravity, typed and waiting for your confirmation.

Claude Desktop 9:41 AM
You Heads up: the billing cutover moves to Oct 14. Stripe webhooks stay on v2 until then.
Claude Noted. I saved that as a decision with the v2 constraint attached, dated today.
Remembered · decision · constraint
Vertiso Same room
Antigravity · new session 9:42 AM
You Start the webhook migration branch.
Agent Your memory says the cutover is Oct 14 and v2 stays live until then. I'll scaffold the v3 handler behind a flag and leave v2 untouched.
Recalled · decision · nothing re-explained

0

times you repeat yourself

8 types

decision, constraint, action, and more

You confirm

nothing closes itself

Install in Antigravity

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

In Antigravity 2, open Settings → Customizations → Installed MCP Servers, add a server pointing at the URL, then Refresh and click Authenticate to run the browser OAuth flow — no token to paste. You can also write the unified config directly at ~/.gemini/config/mcp_config.json:

Add MCP server (OAuth, recommended)
{
  "mcpServers": {
    "vertiso-memory": {
      "serverUrl": "https://memory.vertiso.ai/mcp"
    }
  }
}
On Antigravity 1 (stdio only), or prefer the vmem bridge?

Antigravity 1 connects only to local stdio servers, so it goes through the vmem bridge (token stays in ~/.vmem). Run vmem mcp install antigravity, then restart Antigravity.

~/.gemini/antigravity/mcp_config.json (vmem bridge, Antigravity 1)
{
  "mcpServers": {
    "vertiso-memory": {
      "command": "<run `which vmem` to get the absolute path>",
      "args": ["mcp", "serve", "--client", "antigravity"]
    }
  }
}

Without vmem, the Node-based mcp-remote bridge persists the token in the config file:

Antigravity MCP config (bearer token fallback)
{
  "mcpServers": {
    "vertiso-memory": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://memory.vertiso.ai/mcp",
        "--header",
        "Authorization: Bearer <paste your token here>",
        "--header",
        "X-Agent-Source: agent:antigravity"
      ]
    }
  }
}

Antigravity 2 (May 2026) added remote Streamable HTTP MCP with OAuth; Antigravity 1 is stdio-only and needs the vmem bridge.

Recommended: add a bootstrap instruction to your AGENTS.md (Antigravity reads it at the start of every session) 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 →

Session skills

Antigravity connects the memory tools over MCP and reads your AGENTS.md at the start of every session, which is where the standing instruction goes.

Ready when you are

Start building your memory layer.

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