github doobidoo/mcp-memory-service v8.13.3
v8.13.3: Fix MCP Memory Tools (Critical)

latest releases: v10.31.2, v10.31.1, v10.31.0...
5 months ago

v8.13.3 - Critical Patch Release

🚨 MCP Memory Tools Restored

This critical patch fixes a v8.12.0 regression that completely broke all MCP memory operations.


🐛 Issue Fixed

All MCP Memory Tools Broken

  • Error: KeyError: 'message' when calling any MCP memory tool
  • Impact: MCP tools (store, retrieve, search, delete) completely non-functional since v8.12.0
  • Symptoms: "Error storing memory: 'message'" in Claude Code/Desktop

🔍 Root Cause

v8.12.0 MemoryService Architecture Regression

The MemoryService refactoring changed response format:

  • MemoryService returns: {success: bool, memory: {...}}
  • MCP tools expect: {success: bool, message: str, content_hash: str}
  • Result: MCP protocol tries to access missing 'message' field → KeyError

Why It Persisted:

  • ✅ HTTP API works fine (doesn't need these specific fields)
  • ✅ Integration tests passed (only tested HTTP, not MCP protocol)
  • ❌ No MCP protocol integration tests to catch this

✅ Changes

mcp_server.py (lines 173-206):

  • ✅ Transform MemoryService response to MCP TypedDict format
  • ✅ Extract content_hash from nested memory object
  • ✅ Add descriptive message field for MCP protocol
  • ✅ Handle 3 response cases:
    • Failure: Return error message
    • Chunked: Return chunk count and hashes
    • Single: Return content hash

🎯 Result

MCP memory tools now work correctly:

  • ✅ Proper message field in responses
  • ✅ Correct content_hash extraction
  • ✅ Descriptive error messages
  • ✅ Chunked memory support maintained

⚠️ User Action Required

Restart MCP Server to Load Fix:

Claude Code:

# Type this command:
/mcp

Claude Desktop:

  • Restart the application

This will:

  1. Terminate old MCP server process (running broken code)
  2. Start new MCP server with fix
  3. MCP memory tools will work again

📊 Technical Details

  • Introduced: v8.12.0 MemoryService architecture (#176)
  • Affected: All MCP memory operations (store, retrieve, search, delete)
  • HTTP API: Unaffected (uses different response format)
  • Test Gap: Need MCP protocol integration tests

📚 Full Changelog

See CHANGELOG.md for complete details.

🔗 Related

  • Previous: v8.13.2 (sync script fix)
  • Regression from: v8.12.0 MemoryService architecture
  • Issue: Need MCP integration tests (#190 related)

Don't miss a new mcp-memory-service release

NewReleases is sending notifications on new releases.