# Store via CLI - goes to ReasoningBank
$ claude-flow memory store "auth-pattern" "Use JWT with RS256"
✅ Stored successfully in ReasoningBank

# Try to retrieve via MCP - different database!
await mcp__claude_flow__memory_usage({
  action: "retrieve",
  key: "auth-pattern"
});
// ❌ Returns: { found: false, value: null }

Solution: UnifiedMemoryManager

Created a unified memory layer that both CLI and MCP use:

Priority-based Storage System:
1. 🧠 ReasoningBank (.swarm/memory.db) - AI-powered semantic search
2. 🗄️ SQLite (unified-memory.db) - Fast SQL queries
3. 📄 JSON (memory-store.json) - Always-available fallback

Features:
- ✅ Auto-Detection: Checks for .swarm/memory.db existence
- ✅ Lazy Loading: Imports ReasoningBank adapter only when needed
- ✅ Graceful Fallback: Falls back to JSON if ReasoningBank unavailable
- ✅ Semantic Search: Query by meaning, not keywords
- ✅ Similarity Scores: Ranked results (0-100%)

Changes

1. Core Integration (src/memory/unified-memory-manager.js)

- Added ReasoningBank detection and integration
- Implemented priority-based storage selection
- Enhanced methods: store(), query(), get(), getStats()

2. MCP Server (src/mcp/mcp-server.js)

- Replaced fallback-store with UnifiedMemoryManager
- Added memory_search case statement (was missing!)
- Enhanced responses with storage_type and semantic_search metadata


Test Results ✅

CLI → MCP Interoperability (Semantic Search):
# Store via CLI
$ claude-flow memory store "authentication-best-practices" \
    "Always use environment variables for API keys..." \
    --namespace security
✅ Stored in ReasoningBank

# Query via MCP with DIFFERENT words
await memoryManager.query("How should I store API credentials?");

# Result: Found with 31.0% similarity! ✨
{
  key: "authentication-best-practices",
  score: 0.310,
  confidence: 0.80,
  mode: "reasoningbank"
}

Semantic matching works:
- Query: "How should I store API credentials?"
- Found: "Always use environment variables for API keys"
- System understands: "store credentials" ≈ "environment variables"

Impact

For MCP Users:
- 🧠 Semantic search now accessible via MCP tools
- 📊 Similarity scores in search results
- 🔄 Can read data stored via CLI
- ⚡ Auto-detection, no config needed
- 🛡️ Graceful fallback to JSON mode

For CLI Users:
- 🔗 Data now accessible via MCP tools
- ✅ No breaking changes
- 📈 Enhanced MCP response metadata

Backward Compatibility ✅

- 100% Compatible: No breaking changes to existing APIs
- JSON Fallback: Works without ReasoningBank
- Existing Data: All previous data remains accessible
- Same Signatures: No changes to MCP tool parameters

Files Changed

- src/memory/unified-memory-manager.js - ReasoningBank integration
- src/mcp/mcp-server.js - UnifiedMemoryManager adoption + missing case fix


Testing

# 1. Store via CLI
./bin/claude-flow memory store "test-key" "semantic test value" --namespace test

# 2. Query via MCP with different words
# UnifiedMemoryManager returns results with similarity scores

# 3. Verify storage type
./bin/claude-flow memory mode
# Should show: "ReasoningBank Mode: Initialized ✅"

---
Ready for review! 🎉 Full interoperability between CLI and MCP memory interfaces with semantic search
capabilities.