Vertiso Memory for Raycast

One memory, every agent

Decide it anywhere. Raycast already knows.

What you settle in one tool is on hand in Raycast, 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

Same room

Raycast · new session 9:42 AM

You Start the webhook migration branch.

Raycast AI 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

times you repeat yourself

8 types

decision, constraint, action, and more

You confirm

nothing closes itself

Install in Raycast

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 Raycast, open the Command Palette, search Install MCP Server, and add a new server. Choose HTTP transport, enter the URL, and pick Dynamic for the OAuth type. Raycast opens your browser to sign in and approve — no token to paste.

Install MCP Server (OAuth, recommended)

Name: Vertiso Memory
Transport: HTTP
URL: https://memory.vertiso.ai/mcp
OAuth Type: Dynamic

Prefer the vmem bridge or a pasted token?

Run vmem mcp install raycast for the stdio bridge (token stays in ~/.vmem), or use the HTTP transport with a bearer token in the form.

Raycast HTTP fields (bearer token fallback)

Name: Vertiso Memory
Transport: HTTP
URL: https://memory.vertiso.ai/mcp
Authorization: Bearer <paste your token here>
X-Agent-Source: agent:raycast

In Raycast, open Manage MCP Servers to review, disable, or remove the Vertiso Memory server later.

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.

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 →

Your memory, inside Raycast.

Decide it anywhere. Raycast already knows.

Install in Raycast

Start building your memory layer.