// FOR AGENTS

Memorythatsurvivesthechat.

One command. Your agent stops starting from scratch. Local, offline, zero cost - or one click into the hosted Cortex API for instant power.

Fastest path: Cortex API

Grab a key, save your first memory in under two minutes. No infra, no config files.

Get API Key
Claude DesktopCursorWindsurfDeerFlowAny MCP Runtime
Agent memory · Live
5 stored
episodic
just now
Tracked the auth bug to a race condition on March 5
semantic
2m ago
Project runs on Next.js + Supabase, deployed via Railway
procedural
8m ago
To ship: merge to main, Railway handles the rest
self_model
14m ago
I over-explain things - need to keep it tighter
introspective
32m ago
Something keeps recurring across my last 10 tasks…
Recall in ~50msSHA-256 · Encrypted
// WHY

Notes aren't memory.

You've tried it already. MEMORY.md, daily logs, context dumps. They feel like memory - right up until your agent reaches for one and finds nothing there.

Storage isn't the problem. Selection is. Your agent has to guess what's worth keeping while the context window collapses under its feet. One miss and the thread dies.

Vitalis lives beneath the file layer. It pulls memories by meaning, not by path. It wires related thoughts together as they happen. And it quietly holds onto the things you would have lost.

Without Vitalis

  • Dig through folders, hope something turns up
  • Recall is only as sharp as your filenames
  • That bug from a month ago - gone with the chat
  • Every session starts from zero
Recommended

With Vitalis

  • Pull memories by meaning, not by path
  • Related thoughts link themselves together
  • What matters strengthens. What doesn't fades.
  • Every session picks up where the last one stopped
// INSTALL

Install in 30
seconds.

~ - bash
npx vitaliscad mcp-install --local
Detected Claude Desktop, Cursor
Wrote MCP entry to claude_desktop_config.json
Wrote MCP entry to .cursor/mcp.json
Restart your IDE to activate
// TOOLS

Four tools. Your agent uses them all.

Vitalis ships four MCP tools. Each one solves a different memory problem. Together they replace MEMORY.md, daily logs, and every other context dump that quietly stops working.

01
STORE

Persist a memory

store_memory writes anything worth holding onto with type, importance, and tags. Use it the moment a fact, decision, or signal earns a place in long-term memory.

02
RECALL

Recall by meaning

recall_memories runs multi-phase semantic search with graph traversal. Use it before responding to anything that depends on past context, not just keyword matches.

03
STATS

Inspect the brain

get_memory_stats returns an overview of memories by type, importance, and decay. Use it to see what the agent currently knows and how that shape is shifting.

04
CLINAMEN

Lateral leaps

find_clinamen surfaces unexpected lateral connections between unrelated memories. Use it for creative problem-solving and reflective thinking, not direct lookup.

// MEMORY TYPES

5 memory types.

Memory Record · Live
1 / 5
type · episodicmem_8a1f3c

Time-stamped events the agent lived through. Conversations, fixes, decisions, the moments worth replaying.

stored content

We tracked down the auth bug on March 5

stored2026-03-05 · 14:32
importance0.82
decayslow
// FAQ

Frequently asked.

"I already keep MEMORY.md and daily logs"
"What about privacy?"
"Is this a crypto thing?"
"Won't it be slower than files?"
"What if decay loses something important?"
// READY WHEN YOU ARE

Install once. Never forget again.

$npx vitalis mcp-install --local

Read the docs Open the lab Get an API key

83.9LoCoMo (ACL 2024)
MITOpen Source License
18K+Lines of Code

GitHubnpmBenchmarks