Labsco
MCP SERVER

Memory MCP

by JamesANZ

A MongoDB-backed memory the assistant writes to and reads from, so what you established yesterday survives into tomorrow's session.

Agent Memory
Summary
Context that outlives the conversation window.

The database is the point: memories sit in MongoDB you control, so they survive a client restart, a new project and a different editor. Note that saving overwrites and appending does not — which of the two you call is the difference between adding a fact and replacing everything you had.

What it is

Persistent storage for the things you would otherwise re-explain. Memories live in MongoDB rather than the session, and the assistant can append to them, read them back, replace them or clear them out.

What you get
  • Memories saved to the database, and read back in a later session
  • Appending new memories without overwriting what is already stored
  • A full reset when the stored set has gone stale
  • Archiving of conversation context with tags, and retrieval of the relevant parts
  • Relevance scoring and summaries over what has been archived
Requirements

A MongoDB instance and its connection string in the environment. Node.js 18 or newer with npm.

Setup effort

One command — npm install -g @jamesanz/memory-mcp