Memory Bank MCP With Remote SSH Support 🧠
About
A Model Context Protocol (MCP) server that enables AI assistants to store and retrieve structured information across sessions using Memory Banks. It now supports storing Memory Banks on a remote server via SSH.
Details
- Author
- aakarsh-sasi
- GitHub stars
- 36
- Downloads
- 381
- Categories
- Knowledge Base
Jump to
- Initialize, find, and manage Memory Banks
- Read and write files in Memory Banks
- Track progress and log important decisions
- Maintain active context across sessions
- Support multiple modes (code, architect, ask, debug, test)
- Store Memory Banks on a remote server via SSH
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 Bank MCP With Remote SSH Support 🧠Command (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
Install via npm (npm install @aakarsh-sasi/memory-bank-mcp) or run directly with npx (npx @aakarsh-sasi/memory-bank-mcp). Use command-line flags like --path, --folder, --mode, and --remote with --remote-user, --remote-host, --remote-path for remote mode. Configure as an MCP server in code editors like Cursor by specifying the npx command and arguments.
initialize_memory_bank
Initialize a Memory Bank in the specified directory
set_memory_bank_path
Set a custom path for the Memory Bank
debug_mcp_config
Debug the current MCP configuration
read_memory_bank_file
Read a file from the Memory Bank
write_memory_bank_file
Write to a Memory Bank file
list_memory_bank_files
List Memory Bank files
get_memory_bank_status
Check Memory Bank status
migrate_file_naming
Migrate Memory Bank files from camelCase to kebab-case naming convention
track_progress
Track progress and update Memory Bank files
update_active_context
Update the active context file
log_decision
Log a decision in the decision log
switch_mode
Switches to a specific mode
get_current_mode
Gets information about the current mode
process_umb_command
Processes the Update Memory Bank (UMB) command
complete_umb
Completes the Update Memory Bank (UMB) process
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"memory bank mcp with remote ssh support \ud83e\udde0": {
"memory-bank-mcp-aakarsh-sasi": {
"command": "npx",
"args": [
"@aakarsh-sasi/memory-bank-mcp"
]
}
}
}
}McpServers
{
"memory-bank-mcp-aakarsh-sasi": {
"command": "npx",
"args": [
"@aakarsh-sasi/memory-bank-mcp"
]
}
}Memory Bank MCP With Remote SSH Support 🧠
A Model Context Protocol (MCP) server for managing Memory Banks, allowing AI assistants to store and retrieve information across sessions. Now with remote server support!
<a href="https://glama.ai/mcp/servers/@aakarsh-sasi/memory-bank-mcp">
</a>
Overview 📋
Memory Bank Server provides a set of tools and resources for AI assistants to interact with Memory Banks. Memory Banks are structured repositories of information that help maintain context and track progress across multiple sessions.
Features ✨
- Memory Bank Management: Initialize, find, and manage Memory Banks
- File Operations: Read and write files in Memory Banks
- Progress Tracking: Track progress and update Memory Bank files
- Decision Logging: Log important decisions with context and alternatives
- Active Context Management: Maintain and update active context information
- Mode Support: Detect and use .clinerules files for mode-specific behavior
- UMB Command: Update Memory Bank files temporarily with the UMB command
- Robust Error Handling: Gracefully handle errors and continue operation when possible
- Status Prefix System: Immediate visibility into Memory Bank operational state
- Remote Server Support: Store Memory Banks on a remote server using SSH
Directory Structure 📁
By default, Memory Bank uses a memory-bank directory in the root of your project. When you specify a project path using the --path option, the Memory Bank will be created or accessed at <project_path>/memory-bank.
You can customize the name of the Memory Bank folder using the --folder option. For example, if you set --folder custom-memory, the Memory Bank will be created or accessed at <project_path>/custom-memory.
For more details on customizing the folder name, see Custom Memory Bank Folder Name.
Recent Improvements 🛠️
- Remote Server Support: Store your Memory Bank on a remote server via SSH
- Customizable Folder Name: You can now specify a custom folder name for the Memory Bank
- Consistent Directory Structure: Memory Bank now always uses the configured folder name in the project root
- Enhanced Initialization: Memory Bank now works even when .clinerules files don't exist
- Better Path Handling: Improved handling of absolute and relative paths
- Improved Directory Detection: Better detection of existing memory-bank directories
- More Robust Error Handling: Graceful handling of errors related to .clinerules files
For more details, see Memory Bank Bug Fixes.
Installation 🚀
Installing via Smithery
To install Memory Bank for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @aakarsh-sasi/memory-bank-mcp --client claude
Manual Installation
```bashSign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
