Memory Usage Dashboard
About
Provides a React-based dashboard for real-time monitoring and visualization of memory usage in MCP implementations, enabling developers to optimize performance and identify potential memory leaks.
Details
- Author
- doobidoo
- Repository
- doobidoo/mcp-memory-dashboard
- GitHub stars
- 1
- Categories
- Database, AI, Knowledge Base, Other, Design, Developer Tools, Infrastructure, Frontend
- Tags
- #web
Jump to
Individual delete buttons not appearing
- Ensure memories have valid IDs (refresh search results if needed)
- Check that you're using the latest version of the memory service
- Individual deletion requires memory service v1.2.0+
Time-based recall not working
- Try simpler expressions first: "today", "yesterday", "last week"
- Complex time expressions may require exact phrasing
- Check console logs (F12) for time parsing errors
Backup feedback not showing
- Verify backup directory has write permissions
- Check that backup path environment variable is set correctly
- Large databases may take longer to backup (progress is shown)
Query times still showing 0
- Perform a few searches to populate the average calculation
- Query time tracking requires at least one search operation
- Restart the application if metrics don't update
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
Memory Usage DashboardCommand (node, npx, python, etc.)uvArguments-
Argument 1
--directory -
Argument 2
/path/to/mcp-memory-service -
Argument 3
run -
Argument 4
memory
Environment-
MCP_MEMORY_CHROMA_PATH
/Users/yourusername/Library/Application Support/mcp-memory/chroma_db -
MCP_MEMORY_BACKUPS_PATH
/Users/yourusername/Library/Application Support/mcp-memory/backups
Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
-
Argument 1
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
1. Clone the repository:
git clone https://github.com/yourusername/mcp-memory-dashboard.git
cd mcp-memory-dashboard
2. Install dependencies:
npm install
3. Configure environment variables:
Create a .env file in the project root:
macOS/Linux:
1. Install Docker Desktop (if not already installed)
2. Enable Docker Mode: Set VITE_USE_DIRECT_CHROMA_ACCESS=true in your .env file
3. Start Dashboard: npm start - Docker container automatically managed!
📖 Complete Docker Setup Guide | 🏗️ Technical Architecture Details
VITE_MEMORY_SERVICE_PATH="C:\path\to\mcp-memory-service"
VITE_MEMORY_CHROMA_PATH="C:\Users\%USERNAME%\AppData\Local\mcp-memory\chroma_db"
VITE_MEMORY_BACKUPS_PATH="C:\Users\%USERNAME%\AppData\Local\mcp-memory\backups"
VITE_CLAUDE_CONFIG_PATH="C:\Users\%USERNAME%\AppData\Roaming\Claude\claude_desktop_config.json"
- Use double backslashes (\\) or forward slashes (/) in paths
- The %USERNAME% environment variable automatically resolves to your Windows username
- Claude Desktop config is stored in AppData\Roaming\Claude\
- Memory data is stored in AppData\Local\mcp-memory\
Ensure your MCP Memory Service is properly configured in your Claude Desktop configuration:
macOS/Linux:
json{
"mcpServers": {
"memory": {
"command": "uv",
"args": ["--directory", "/path/to/mcp-memory-service", "run", "memory"],
"env": {
"MCP_MEMORY_CHROMA_PATH": "/Users/yourusername/Library/Application Support/mcp-memory/chroma_db",
"MCP_MEMORY_BACKUPS_PATH": "/Users/yourusername/Library/Application Support/mcp-memory/backups"
}
}
}
}
Windows:
json{
"mcpServers": {
"memory": {
"command": "uv",
"args": ["--directory", "C:\\path\\to\\mcp-memory-service", "run", "memory"],
"env": {
"MCP_MEMORY_CHROMA_PATH": "C:\\Users\\yourusername\\AppData\\Local\\mcp-memory\\chroma_db",
"MCP_MEMORY_BACKUPS_PATH": "C:\\Users\\yourusername\\AppData\\Local\\mcp-memory\\backups"
}
}
}
}
``
| Variable | Description | macOS/Linux Example | Windows Example |
|----------|-------------|---------------------|-----------------|
|
VITE_MEMORY_SERVICE_PATH | Path to MCP Memory Service | /path/to/mcp-memory-service | C:\path\to\mcp-memory-service |
| VITE_MEMORY_CHROMA_PATH | ChromaDB database directory | ~/Library/Application Support/mcp-memory/chroma_db | C:\Users\%USERNAME%\AppData\Local\mcp-memory\chroma_db |
| VITE_MEMORY_BACKUPS_PATH | Backup storage directory | ~/Library/Application Support/mcp-memory/backups | C:\Users\%USERNAME%\AppData\Local\mcp-memory\backups |
| VITE_CLAUDE_CONFIG_PATH | Claude Desktop config file | ~/Library/Application Support/Claude/claude_desktop_config.json | C:\Users\%USERNAME%\AppData\Roaming\Claude\claude_desktop_config.json |
| VITE_USE_DIRECT_CHROMA_ACCESS | 🚀 NEW: Enable Docker ChromaDB mode | true (Docker) / false (MCP) | true (Docker) / false` (MCP) |
1. Check the console logs (F12) for detailed error messages
2. Verify all environment variables are set correctly
3. Ensure MCP Memory Service is working independently
4. Check file permissions for database and backup directories
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"memory usage dashboard": {
"env": {
"MCP_MEMORY_CHROMA_PATH": "/Users/yourusername/Library/Application Support/mcp-memory/chroma_db",
"MCP_MEMORY_BACKUPS_PATH": "/Users/yourusername/Library/Application Support/mcp-memory/backups"
},
"args": [
"--directory",
"/path/to/mcp-memory-service",
"run",
"memory"
],
"command": "uv"
}
}
}
Linux
{
"env": {
"MCP_MEMORY_CHROMA_PATH": "/Users/yourusername/Library/Application Support/mcp-memory/chroma_db",
"MCP_MEMORY_BACKUPS_PATH": "/Users/yourusername/Library/Application Support/mcp-memory/backups"
},
"args": [
"--directory",
"/path/to/mcp-memory-service",
"run",
"memory"
],
"command": "uv"
}
Macos
{
"env": {
"MCP_MEMORY_CHROMA_PATH": "/Users/yourusername/Library/Application Support/mcp-memory/chroma_db",
"MCP_MEMORY_BACKUPS_PATH": "/Users/yourusername/Library/Application Support/mcp-memory/backups"
},
"args": [
"--directory",
"/path/to/mcp-memory-service",
"run",
"memory"
],
"command": "uv"
}
Windows
{
"env": {
"MCP_MEMORY_CHROMA_PATH": "C:\\Users\\yourusername\\AppData\\Local\\mcp-memory\\chroma_db",
"MCP_MEMORY_BACKUPS_PATH": "C:\\Users\\yourusername\\AppData\\Local\\mcp-memory\\backups"
},
"args": [
"--directory",
"C:\\path\\to\\mcp-memory-service",
"run",
"memory"
],
"command": "uv"
}
🚨 DEPRECATED - This Repository is No Longer Needed! 🚨
> ⚠️ IMPORTANT NOTICE: This standalone dashboard is now OBSOLETE!
>
> The MCP Memory Service now includes an embedded dashboard with all the features of this standalone version and more!
>
> ## 🎉 What's New?
>
> The main MCP Memory Service now provides:
> - ✅ Built-in Web Dashboard - No separate installation needed
> - ✅ All Original Features - Store, search, recall, and manage memories
> - ✅ Better Integration - Direct access to the memory service
> - ✅ Simplified Setup - One installation, everything included
> - ✅ Active Development - New features added regularly
>
> ## 🔄 How to Migrate
>
> 1. Update your MCP Memory Service:
>
> git pull origin main
> python install.py
> >
> 2. Access the embedded dashboard:
> - Start the memory service with HTTP mode
> - Navigate to
http://localhost:8000 in your browser> - Enjoy all the features without this separate app!
>
> ## 📦 Why Was This Deprecated?
>
> To provide a better user experience, we've integrated the dashboard directly into the memory service. This means:
> - Fewer dependencies to manage
> - Easier installation and updates
> - Better performance and reliability
> - Single source of truth for all features
>
> ## 🔗 Get Started
>
> Visit the main repository for installation and usage instructions:
>
> 👉 MCP Memory Service
>
> ---
>
> The original README content is preserved below for historical reference.
>
> ---
MCP Memory Dashboard 
A professional desktop application for managing and interacting with the MCP Memory Service - a semantic memory system built on the Model Context Protocol (MCP).
🚀 NEW: High-Performance Docker ChromaDB Integration
Major Update: Now supports direct Docker ChromaDB access for 2-3x faster performance and zero service conflicts!
⚡ Docker Mode Benefits
- 🚀 2-3x Faster: Direct HTTP access eliminates MCP overhead (50-150ms vs 200-500ms) - 🔄 Zero Conflicts: Eliminates MCP service duplication that could interfere with Claude Desktop - 💾 Zero Data Loss: Uses your existing database directly via volume mounting - 🐳 Automatic Management: Transparent Docker container lifecycle management - 🛡️ Graceful Fallback: Automatically falls back to traditional MCP if Docker unavailableQuick Docker Setup
1. Install Docker Desktop (if not already installed) 2. Enable Docker Mode: SetVITE_USE_DIRECT_CHROMA_ACCESS=true in your .env file
3. Start Dashboard: npm start - Docker container automatically managed!
📖 Complete Docker Setup Guide | 🏗️ Technical Architecture Details
✨ Features
🧠 Memory Management
- Store Memories: Save content with tags and metadata - Semantic Search: Find memories using natural language queries with individual delete buttons - Time-Based Recall: Search memories by time expressions ("yesterday", "last week", etc.) - Individual Memory Deletion: Delete specific memories with confirmation dialogs - Tag Management: Organize and delete memories by tags with multiple selection - Real-time Results: Instant search and retrieval with similarity scores📊 Dashboard & Analytics
- Live Statistics: Total memories, unique tags, database health - Database Health Monitoring: Real-time health status (0-100%) - Performance Metrics: Real average query time tracking (1-3 seconds) - Storage Information: Database size and path information - 4-Tab Interface: Dedicated tabs for Store, Search, Recall, and Tag Management🔧 Database Operations
- Database Optimization: Clean up and optimize vector indices - Backup Creation: Create timestamped backups with detailed feedback (file path, size, timestamp) - Health Checks: Validate database integrity and performance - Auto-initialization: Seamless ChromaDB setup and configuration - Real Backup System: Complete tar.gz compression with success notifications🏷️ Enhanced Tag Management
- Multiple Tag Deletion: Select and delete multiple tags simultaneously - Visual Tag Selection: Interactive tag chips with add/remove functionality - Flexible Delete Options: Support for both single and multiple tag deletion - API Consistency: Consistent interface with search functionality - Clear Warnings: Understand OR vs AND logic for tag operations⏰ Time-Based Recall System
- Quick Filters: One-click buttons for [Today] [Yesterday] [Last Week] [Last Month] [Last 3 Months] - Natural Language: Free-text time expressions like "2 days ago", "last summer" - Smart Processing: Combines time filtering with semantic search when appropriate - Dedicated Tab: Separate "Recall by Time" interface for temporal queries🎨 User Experience
- Loading Indicators: Visual feedback during database initialization - Progress Tracking: Step-by-step status updates during startup - Professional Interface: Clean, modern Electron-based desktop app - Keyboard Shortcuts: F12 or Ctrl+Shift+I for developer tools - Responsive Design: Adaptive layout for different window sizes - Rich Feedback: Detailed success/error messages with dismissible notifications - Safety Features: Confirmation dialogs for destructive operations🚀 Quick Start
Prerequisites
- Node.js (v16 or higher)
- Python (v3.10 or higher) with UV package manager
- MCP Memory Service (compatible installation)
Installation
1. Clone the repository:
git clone https://github.com/yourusername/mcp-memory-dashboard.git
cd mcp-memory-dashboard
2. Install dependencies:
npm install
3. Configure environment variables:
Create a .env file in the project root:
macOS/Linux:
# Basic Configuration
VITE_MEMORY_SERVICE_PATH="/path/to/mcp-memory-service"
VITE_MEMORY_CHROMA_PATH="/Users/yourusername/Library/Application Support/mcp-memory/chroma_db"
VITE_MEMORY_BACKUPS_PATH="/Users/yourusername/Library/Application Support/mcp-memory/backups"
VITE_CLAUDE_CONFIG_PATH="/Users/yourusername/Library/Application Support/Claude/claude_desktop_config.json"
# 🚀 NEW: Docker ChromaDB Mode (High Performance)
VITE_USE_DIRECT_CHROMA_ACCESS=true # Enable Docker mode for 2-3x faster performance
# VITE_USE_DIRECT_CHROMA_ACCESS=false # Traditional MCP mode (stable fallback)
Windows:
# Basic Configuration
VITE_MEMORY_SERVICE_PATH="C:\path\to\mcp-memory-service"
VITE_MEMORY_CHROMA_PATH="C:\Users\%USERNAME%\AppData\Local\mcp-memory\chroma_db"
VITE_MEMORY_BACKUPS_PATH="C:\Users\%USERNAME%\AppData\Local\mcp-memory\backups"
VITE_CLAUDE_CONFIG_PATH="C:\Users\%USERNAME%\AppData\Roaming\Claude\claude_desktop_config.json"
# 🚀 NEW: Docker ChromaDB Mode (High Performance)
VITE_USE_DIRECT_CHROMA_ACCESS=true # Enable Docker mode for 2-3x faster performance
# VITE_USE_DIRECT_CHROMA_ACCESS=false # Traditional MCP mode (stable fallback)
4. Start the application:
npm start
🪟 Windows-Specific Notes
Path Configuration
- Use double backslashes (\\) or forward slashes (/) in paths
- The %USERNAME% environment variable automatically resolves to your Windows username
- Claude Desktop config is stored in AppData\Roaming\Claude\
- Memory data is stored in AppData\Local\mcp-memory\
…
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.





