alioshr memory bank mcp

WHAT IT CONNECTS

What alioshr memory bank mcp gives an AI Agent

• **Multi-Project Support**
• Project-specific directories
• File structure enforcement
• Path traversal prevention
• Project listing capabilities
• File listing per project
• **Remote Accessibility**
• Full MCP protocol implementation
• Type-safe operations
• Proper error handling
• Security through project isolation
• **Core Operations**
• Read/write/update memory bank files
• List available projects
• List files within projects
• Project existence validation
• Safe read-only operations
• Configure the MCP server in your settings (see Configuration section below)
• Start using the memory bank tools in your AI assistant
• For Cline extension: `~/Library/Application Support/Cursor/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`
• For Roo Code VS Code extension: `~/Library/Application Support/claude-code/User/globalStorage/rooveterinaryinc.roo-cline/settings/mcp_settings.json`
• For Claude desktop app: `~/Library/Application Support/Claude/claude_desktop_config.json`
• `MEMORY_BANK_ROOT`: Directory where project memory banks will be stored (e.g., `/path/to/memory-bank`)
• `disabled`: Set to `false` to enable the server
• `autoApprove`: List of operations that don't require explicit user approval:
• `memory_bank_read`: Read memory bank files
• `memory_bank_write`: Create new memory bank files
• `memory_bank_update`: Update existing memory bank files
• `list_projects`: List available projects
• `list_project_files`: List files within a project
• Build the Docker image:
• Run the Docker container for testing:
• Add MCP configuration, example for Roo Code:
• Fork the repository
• Create a feature branch (`git checkout -b feature/amazing-feature`)
• Commit your changes (`git commit -m 'Add amazing feature'`)
• Push to the branch (`git push origin feature/amazing-feature`)
• Open a Pull Request
• Use TypeScript for all new code
• Maintain type safety across the codebase
• Add tests for new features
• Update documentation as needed
• Follow existing code style and patterns
• Write unit tests for new features
• Include multi-project scenario tests
• Test error cases thoroughly
• Validate type constraints
• Mock filesystem operations appropriately