OpenMemory MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@OpenMemory MCP Server search my memories for dashboard configuration notes"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
OpenMemory MCP Server
MCP (Model Context Protocol) server that provides Claude Desktop with access to your OpenMemory API running on Ubuntu server richard-XPS-15-9560.local:8892.
Architecture
Claude Desktop (Windows)
↓ stdio
MCP Server (Python - this package)
↓ HTTP REST
OpenMemory API (richard-XPS-15-9560.local:8892)
↓
Neo4j + Vector DB (Ubuntu Docker)Related MCP server: Spomory
Features
The MCP server provides Claude Desktop with the following tools:
search_memories - Semantic search across OpenMemory graph
add_memory - Store new memories with sector classification
list_memories - Browse recent memories with pagination
get_memory - Retrieve specific memory by ID
reinforce_memory - Boost importance of a memory
delete_memory - Remove a memory
health_check - Verify OpenMemory API connectivity
Windows Installation
Prerequisites
Python 3.10 or higher installed on Windows
Download from: https://www.python.org/downloads/
During installation, check "Add Python to PATH"
Claude Desktop installed on Windows
Download from: https://claude.ai/download
Network access to
richard-XPS-15-9560.local:8892from your Windows PCTest with:
curl http://richard-XPS-15-9560.local:8892/healthin PowerShellOr open
http://richard-XPS-15-9560.local:8892/healthin browser
Step 1: Copy Files to Windows
Transfer the entire openmemory-mcp folder to your Windows PC. You can use:
Network share
USB drive
Git clone (if you push this to a repo)
Any file transfer method
Suggested location: C:\Users\YourUsername\openmemory-mcp
Step 2: Install Python Dependencies
Open PowerShell or Command Prompt and navigate to the folder:
cd C:\Users\YourUsername\openmemory-mcpInstall the package and dependencies:
pip install -e .This will install:
mcp- Model Context Protocol SDKhttpx- HTTP client for API callspython-dotenv- Environment variable management
Step 3: Configure Claude Desktop
Locate your Claude Desktop configuration file:
Path:
%APPDATA%\Claude\claude_desktop_config.jsonFull path example:
C:\Users\YourUsername\AppData\Roaming\Claude\claude_desktop_config.json
Open the file in a text editor (create it if it doesn't exist)
Add the OpenMemory MCP server configuration:
{
"mcpServers": {
"openmemory": {
"command": "python",
"args": ["-m", "openmemory_mcp"],
"env": {
"OPENMEMORY_URL": "http://richard-XPS-15-9560.local:8892"
}
}
}
}If you already have other MCP servers configured, add the openmemory entry to the existing mcpServers object:
{
"mcpServers": {
"existing-server": {
"command": "...",
"args": ["..."]
},
"openmemory": {
"command": "python",
"args": ["-m", "openmemory_mcp"],
"env": {
"OPENMEMORY_URL": "http://richard-XPS-15-9560.local:8892"
}
}
}
}Save the file
Step 4: Restart Claude Desktop
Completely quit Claude Desktop (check system tray)
Restart Claude Desktop
The MCP server should now be available
Testing
Test 1: Network Connectivity
From Windows PowerShell, verify you can reach the OpenMemory API:
curl http://richard-XPS-15-9560.local:8892/healthExpected response:
{"status": "ok", "timestamp": "..."}Test 2: MCP Server in Claude Desktop
In Claude Desktop, try asking:
"Can you check if OpenMemory is healthy?"
Claude should use the health_check tool and report success.
Test 3: Search Memories
"Search my memories for 'dashboard'"
Test 4: Add Memory
"Add a memory: 'Configured OpenMemory MCP server on Windows' to the semantic sector"
Troubleshooting
"Cannot connect to OpenMemory API"
Check network connectivity from Windows:
ping richard-XPS-15-9560.local curl http://richard-XPS-15-9560.local:8892/healthVerify OpenMemory container is running on Ubuntu:
docker ps | grep openmemory docker logs openmemoryCheck firewall settings on both Windows and Ubuntu
"Python not found" or "Module not found"
Verify Python is installed:
python --versionReinstall dependencies:
cd C:\Users\YourUsername\openmemory-mcp pip install -e . --force-reinstall
MCP Server Not Showing in Claude Desktop
Check the config file path is correct:
%APPDATA%\Claude\claude_desktop_config.json
Verify JSON syntax is valid (no trailing commas, proper quotes)
Check Claude Desktop logs (if available)
Completely quit and restart Claude Desktop
Memory Sectors
OpenMemory uses hierarchical memory sectors:
episodic - Event-based memories (what happened)
semantic - Conceptual knowledge (facts, concepts)
procedural - How-to information (processes, workflows)
emotional - User preferences, sentiment
reflective - Meta-learnings, insights
When adding memories, choose the most appropriate sector.
Development
Running Server Manually (for testing)
cd C:\Users\YourUsername\openmemory-mcp
python -m openmemory_mcpThe server will run in stdio mode and wait for MCP protocol messages.
Project Structure
openmemory-mcp/
├── pyproject.toml # Package configuration
├── README.md # This file
├── .env.example # Environment template
└── src/
└── openmemory_mcp/
├── __init__.py # Package entry point
├── __main__.py # CLI entry point
├── client.py # OpenMemory API client
└── server.py # MCP server implementationAdvanced Configuration
Using API Key Authentication
If your OpenMemory API requires authentication:
Set the API key in Claude Desktop config:
{
"mcpServers": {
"openmemory": {
"command": "python",
"args": ["-m", "openmemory_mcp"],
"env": {
"OPENMEMORY_URL": "http://richard-XPS-15-9560.local:8892",
"OPENMEMORY_API_KEY": "your-api-key-here"
}
}
}
}Using Custom OpenMemory URL
If your OpenMemory runs on a different host/port, update the URL:
"env": {
"OPENMEMORY_URL": "http://different-host:8892"
}Support
For issues:
Check the troubleshooting section above
Verify OpenMemory API is working directly (curl/browser)
Check Claude Desktop and MCP server logs
Ensure Python dependencies are correctly installed
License
MIT
Available Tools
8 toolsadd_memoryA
Store a new memory. content: one self-contained fact, with absolute dates. sector: optional override of the automatic classification (episodic, semantic, procedural, emotional, reflective). tags/metadata optional; a metadata 'type' such as system_info, preference, decision, troubleshooting helps later filtering.
Inputs: content (required), tags, sector, metadata. Returns: result
delete_memoryA
Permanently delete a memory and its vectors/links. Prefer adding a corrected memory over deleting.
Inputs: memory_id (required). Returns: result
get_memoryB
Fetch one memory by id, with full metadata.
Inputs: memory_id (required). Returns: result
health_checkA
Backend health, embedding provider in use, and per-sector counts/average salience.
Inputs: no named parameters. Returns: result
list_memoriesB
List memories newest first, with pagination. sector optionally filters by primary sector.
Inputs: limit, offset, sector. Returns: result
reinforce_memoryB
Raise a memory's salience (importance) by boost (0..1, default 0.1) and mark it as seen now.
Inputs: memory_id (required), boost. Returns: result
search_memoriesA
Keyword (BM25) search over all memories: best for exact terms such as hostnames, ports, file paths, names. Works regardless of embedding provider; no side effects.
query: words to look for. sector: optional filter (episodic, semantic, procedural, emotional, reflective). require_all: if true, every query word must appear.
Inputs: query (required), k, sector, require_all. Returns: result
semantic_searchA
Meaning-based search via the backend's /memory/query (embeddings + salience + recency + links). Good for questions phrased in your own words. Only meaningful when health_check shows a real embedding provider (openai, gemini, ollama); with 'synthetic' results are random. The backend marks every returned memory as seen and raises its salience slightly, so it also acts as reinforcement.
Inputs: query (required), k, sector. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
search_memories and semantic_search are clearly differentiated by keyword vs. meaning-based, though reinforce_memory overlaps with semantic_search's side effect of marking memories as seen and raising salience. The other tools (add, list, get, delete, health_check) are distinct.
All tools follow a consistent snake_case verb_noun pattern (search_memories, add_memory, list_memories, get_memory, delete_memory, reinforce_memory, health_check). health_check is a minor deviation but still clearly named.
Eight tools form a well-scoped set for a memory management server, covering search, CRUD, and health checks without bloat.
Core lifecycle (create, read, list, delete, search) and utility (health_check, reinforce) are covered. Missing an explicit update_memory tool, though the description suggests adding a corrected memory as a workaround.
Maintenance
Related MCP Connectors
Memory for Claude, ChatGPT and other AI apps: notes and docs as a searchable graph, EU-hosted.
Private persistent memory for Claude, ChatGPT & Gemini via MCP - semantic search, zero-code setup.
Persistent AI memory shared across Claude, ChatGPT, coding agents, and compatible MCP clients.
Persistent memory for AI agents across Claude, ChatGPT and any MCP client.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides Claude Desktop with persistent, structured memory and semantic search via a local SQLite knowledge graph, plus a web UI for visualization and management.MIT
- AlicenseAqualityBmaintenanceEnables personal AI memory management through MCP tools for adding, searching, exporting, and deleting memories, with knowledge-graph retrieval and multi-hop association for clients like Claude Desktop and Cursor.61Apache 2.0
- AlicenseAqualityBmaintenanceEnables Claude Desktop and compatible agents to search, read, add, update, and delete a locally stored, user-curated memory using hybrid retrieval with reranking and Qdrant. All processing runs locally without cloud services or API keys.9Apache 2.0
- AlicenseNot gradedqualityCmaintenanceGives every Claude surface (claude.ai, Desktop, mobile, Office add-ins, Claude Code) read and write access to the memories, transcripts and notes produced by Claude Code instances on all of your machines, with hybrid keyword and semantic search. Runs as a self-hosted remote MCP server with GitHub allowlist authentication, secret redaction and audit logging.MIT