🚨 CRITICAL HOTFIX: Import Error Fix
This is a critical hotfix release addressing a bug introduced in v8.61.0 that broke 5 MCP tools.
What Was Fixed
Problem: Phase 3 refactoring in v8.61.0 moved handler files to server/handlers/ directory but didn't update relative import paths, causing import resolution errors.
Error Message:
ModuleNotFoundError: No module named 'mcp_memory_service.server.services'
Root Cause: The relative import ..services (2 dots) resolved to mcp_memory_service/server/services/ instead of the correct mcp_memory_service/services/ after the handlers were moved.
Solution: Changed relative imports from ..services to ...services (3 dots) in server/handlers/memory.py at 5 locations.
Affected MCP Tools (All Fixed)
All 5 tools that were broken in v8.61.0 are now working correctly:
- ✅
update_memory_metadata- Update memory metadata without recreating entries - ✅
search_by_tag- Search memories by tags - ✅
delete_by_tag- Delete memories with specific tags - ✅
delete_by_tags- Delete memories containing ANY of specified tags - ✅
delete_by_all_tags- Delete memories containing ALL specified tags
Technical Details
Files Changed:
src/mcp_memory_service/server/handlers/memory.py(5 import statements updated)
Import Change:
# Before (broken in v8.61.0)
from ..services import storage_service
# After (fixed in v8.61.1)
from ...services import storage_serviceValidation
- ✅ Manual testing confirmed all 5 tools now work correctly
- ✅ All import paths resolve to correct locations
- ✅ No regression in other functionality
Upgrade Instructions
If you installed v8.61.0, please upgrade immediately:
pip install --upgrade mcp-memory-serviceImpact
- Severity: Critical - 5 MCP tools completely broken in v8.61.0
- Affected Versions: v8.61.0 only
- Resolution Time: < 2 hours from bug report to hotfix release
Related
- Fixes #299
Full Changelog: https://github.com/doobidoo/mcp-memory-service/blob/main/CHANGELOG.md#8611---2025-12-27