mcp-openmemory

Openmemory MCP Server

mcp-openmemory gives Claude Desktop users local storage for conversation messages and an editable summary of past context. Its tools support recalling recent exchanges, carrying context between conversations, and separating memories by project.

Server facts

mcp-openmemory

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
71
Last commit
Data as of

Tags

  • agent memory
  • mcp
  • mcp server
  • openmemory

Overview

mcp-openmemory organizes conversation memory into saved messages and a separate abstract for condensed context. For Claude Desktop users carrying decisions, preferences, or project details between chats, save_memory records individual exchanges, while recall_memory_abstract retrieves the existing summary. get_recent_memories supplies recent messages when the abstract lacks a needed detail or needs revision. The summary maintenance workflow involves retrieving the abstract, reviewing recent exchanges, combining relevant information, and submitting the revised text through update_memory_abstract; the tools provide storage and retrieval rather than independently performing that synthesis.

The server runs on Node.js and stores its data locally in SQLite. MEMORY_DB_PATH needs to point to a persistent location: the default database location may be temporary and cleared after an application restart. Project separation can use different database paths for separate app instances, including Claude and Cursor, or context values that logically divide records within one database. Recent-history retrieval supports configurable time windows, but semantic search is not supported. Once configured in Claude Desktop, the server starts automatically and creates the database on first use.

mcp-openmemory setup notes

  • mcp-openmemory records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers