MCP OpenMemory Server
About
Simple standalone MCP server giving Claude the ability to remember your conversations and learn from them over time.
Details
- Author
- baryhuang
- GitHub stars
- 72
- Downloads
- 463
- Categories
- Other
Jump to
- Store and recall individual conversation messages.
- Maintain summarized memory context across conversations.
- Access recent conversations within configurable time windows.
- Uses SQLite for persistent storage without external dependencies.
- Supports memory namespacing by project via separate databases or a “context” field.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
MCP OpenMemory ServerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Configure the server in Claude Desktop’s claude_desktop_config.json using npx with the package @peakmojo/mcp-openmemory@latest, setting the environment variable MEMORY_DB_PATH to a persistent absolute path. The server starts automatically when Claude Desktop is launched and creates the database on first use. Four tools become available: save_memory, recall_memory_abstract, update_memory_abstract, and get_recent_memories.
save_memory
Save individual conversation messages to memory storage. Use this when you want to persist important parts of our current conversation. Call this for each significant message or exchange that should be remembered for future conversations. Typically used during or at the end of conversations to store key information, decisions, or context.
recall_memory_abstract
Retrieve the current memory abstract that summarizes past conversations and context. Use this at the beginning of conversations to understand what has been discussed before, or when you need to check existing memory context. This gives you the processed summary of previous interactions, not raw messages. Call this to "remember" previous conversations with this user.
update_memory_abstract
Save a new or updated memory abstract after processing recent conversations. Use this when you have reviewed recent messages, combined them with existing memory context, and created an improved summary. The typical workflow is: 1) Get current memory abstract, 2) Get recent memories, 3) Process and combine them, 4) Save the updated abstract here. This maintains the evolving memory summary over time.
get_recent_memories
Retrieve recent raw conversation messages from the last few days. Use this when you need to see actual conversation history rather than the processed summary. Helpful for creating or updating memory abstracts, or when you need specific details from recent exchanges. This gives you the unprocessed message data to work with.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mcp openmemory server": {
"mcp-openmemory": {
"command": "npx",
"args": [
"@peakmojo/mcp-openmemory@latest"
]
}
}
}
}McpServers
{
"mcp-openmemory": {
"command": "npx",
"args": [
"@peakmojo/mcp-openmemory@latest"
]
}
}MCP OpenMemory Server
Gives Claude the ability to remember your conversations and learn from them over time.
https://github.com/user-attachments/assets/aef82b8e-3793-4ebd-b993-ddaef14d52d1
Features
- Memory Storage: Save and recall conversation messages
- Memory Abstracts: Maintain summarized memory context across conversations
- Recent History: Access recent conversations within configurable time windows
- Local Database: Uses SQLite for persistent storage without external dependencies
⚠️ Important
You must configure MEMORY_DB_PATH to a persistent location to avoid losing your conversation history when Claude Desktop closes. If not configured, the database defaults to ./memory.sqlite in a temporary location that may be cleared when the application restarts.
Configuration
Prerequisites
- Node.js: Required to run the MCP server. Verify installation with:
node --version
If not installed, download from nodejs.org
- Claude Desktop: Download the latest version for macOS or Windows
Claude Desktop Integration
Configuration File Location
The Claude Desktop configuration file is located at:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
To access: Open Claude Desktop → Claude menu → Settings → Developer → Edit Config
macOS/Linux
Run directly using npm{
"mcpServers": {
"mcp-openmemory": {
"command": "npx",
"args": [
"@peakmojo/mcp-openmemory@latest"
],
"env": {
"MEMORY_DB_PATH": "/Users/username/mcp-memory.sqlite"
}
}
}
}
Windows
Run directly using npm{
"mcpServers": {
"mcp-openmemory": {
"command": "npx",
"args": [
"@peakmojo/mcp-openmemory@latest"
],
"env": {
"MEMORY_DB_PATH": "C:\\Users\\username\\mcp-memory.sqlite"
}
}
}
}
Run from source (all platforms)
{
"mcpServers": {
"memory": {
"command": "npx",
"args": ["/path/to/your/repo/server.js"],
"env": {
"MEMORY_DB_PATH": "/path/to/your/memory.sqlite"
}
}
}
}
Environment Variables
- MEMORY_DB_PATH: Path to SQLite database file (default: ./memory.sqlite)
Verification
After configuring and restarting Claude Desktop, you should see:
1. Slider Icon (🔧) in the bottom left of the input box
2. Available Tools when clicking the slider:
- save_memory
- recall_memory_abstract
- update_memory_abstract
- get_recent_memories
Troubleshooting
Server Not Showing Up
1. Restart Claude Desktop completely
2. Check JSON syntax in your configuration file
3. Verify paths are absolute (not relative) and exist
4. Test manual server start:
# Test if the server runs correctly
npx @peakmojo/mcp-openmemory@latest
Check Logs
Log Locations:
- macOS: ~/Library/Logs/Claude/
- Windows: %APPDATA%\Claude\logs\
View recent logs:
```bash
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
