Robust Long‑Term Memory MCP Server

Robust Long‑Term Memory MCP server exists for a simple reason — assistants are far more useful when they can act on Robust Long‑Term Memory directly instead of describing what you should do. A persistent, human‑like memory system for AI companions.

What you get

A persistent, human‑like memory system for AI companions in LM Studio, powered by a hybrid of SQLite (structured storage) and ChromaDB (semantic search). It’s designed for decades‑long use, seamless recall across sessions, and automatic backups — making your AI companion feel like a continuous, living persona. Now with biological behavior: time‑based lazy decay and reinforcement by use.

• The system prompt teaches the AI when each tool is appropriate
• If the user never phrases things like categories, tags, or “forget this,” only remember and search_memories will appear in logs
• To guide the AI toward other tools, phrase requests with keywords like:
• “Update…” → update_memory
• “Delete/forget…” → delete_memory
• “Preferences/facts/events…” → search_by_type

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need one environment variable: AI_COMPANION_DATA_DIR. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the robust long‑term memory mcp server does with a few real requests.

Choosing this one

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.