MCP Memory Service

# Claude Code Integration: Commands vs MCP Server This guide helps you choose the best integration method for your workflow and needs. ## TL;DR - Quick Decision ### Choose **Commands** if you want: ✅ **Immediate setup** (2 minutes to working) ✅ **Simple usage** (`claude /memory-store "content"`) ✅ **No configuration** (zero MCP server setup) ✅ **Context awareness** (automatic project detection) ### Choose **MCP Server** if you want: ✅ **Deep integration** with Claude Code's MCP system ✅ **Multi-server workflows** (alongside other MCP servers) ✅ **Maximum flexibility** and configuration control ✅ **Traditional MCP tool** interactions --- ## Detailed Comparison ### Installation & Setup | Aspect | Commands (v2.2.0) | MCP Server | |--------|-------------------|------------| | **Setup Time** | 2 minutes | 5-15 minutes | | **Configuration** | Zero config required | Manual MCP server registration | | **Prerequisites** | Claude Code CLI only | Claude Code CLI + MCP knowledge | | **Installation** | `python install.py --install-claude-commands` | `claude mcp add memory-service spawn -- ...` | | **Updates** | Automatic with installer updates | Manual server path updates | ### User Experience | Aspect | Commands | MCP Server | |--------|----------|------------| | **Usage Pattern** | `claude /memory-store "content"` | Natural language in conversations | | **Discovery** | Direct command execution | Tool-based interactions | | **Learning Curve** | Immediate (command help built-in) | Moderate (need to learn MCP patterns) | | **Error Handling** | Built-in guidance and fallbacks | Standard MCP error responses | | **Context Help** | Rich conversational interfaces | Basic tool descriptions | ### Features & Capabilities | Feature | Commands | MCP Server | |---------|----------|------------| | **Memory Storage** | ✅ Full support | ✅ Full support | | **Time-based Recall** | ✅ Natural language queries | ✅ Natural language queries | | **Semantic Search** | ✅ Tag and content search | ✅ Tag and content search | | **Health Diagnostics** | ✅ Comprehensive health checks | ⚠️ Basic connectivity | | **Context Detection** | ✅ Automatic project/git context | ❌ Manual context specification | | **Service Discovery** | ✅ Auto mDNS discovery | ⚠️ Manual endpoint configuration | | **Batch Operations** | ✅ Session context capture | ⚠️ Individual tool calls only | ### Integration & Workflow | Aspect | Commands | MCP Server | |--------|----------|------------| | **Workflow Integration** | Direct CLI commands | Conversational interactions | | **Multi-server Support** | ❌ Standalone commands | ✅ Works with other MCP servers | | **Protocol Compliance** | ❌ Custom implementation | ✅ Full MCP protocol | | **Future Compatibility** | ⚠️ Depends on command format | ✅ Standard MCP evolution | | **Extensibility** | ⚠️ Limited to defined commands | ✅ Full MCP tool ecosystem | ### Technical Considerations | Aspect | Commands | MCP Server | |--------|----------|------------| | **Performance** | ⚡ Direct execution | ⚡ Similar performance | | **Resource Usage** | 🟢 Minimal overhead | 🟢 Standard MCP overhead | | **Debugging** | 🟡 Command-specific logs | 🟢 Standard MCP debugging | | **Monitoring** | 🟢 Built-in health checks | 🟡 External monitoring needed | | **Customization** | 🟡 Limited to command options | 🟢 Full MCP configuration | --- ## Use Case Recommendations ### Perfect for Commands #### **Individual Developers** - Working on personal projects - Want immediate memory capabilities - Prefer direct command interfaces - Don't need complex MCP workflows #### **Quick Prototyping** - Testing memory service capabilities - Short-term project memory needs - Learning the memory service features - Demo and presentation scenarios #### **Context-Heavy Work** - Projects requiring automatic context detection - Git repository-aware memory operations - Session-based development workflows - Frequent project switching ### Perfect for MCP Server #### **Teams & Organizations** - Multiple developers sharing memory service - Complex multi-server MCP workflows - Integration with other MCP tools - Standardized development environments #### **Power Users** - Advanced MCP server configurations - Custom tool integrations - Complex memory service setups - Maximum flexibility requirements #### **Production Deployments** - Server-based memory service hosting - Multi-client concurrent access - Enterprise security requirements - Scalable memory operations --- ## Migration & Compatibility ### Can I Use Both? ✅ **Yes!** Commands and MCP Server can coexist: - Commands for quick operations - MCP Server for deep integration - Switch between methods as needed - No conflicts or data issues ### Switching Between Methods #### From Commands to MCP Server ```bash # Your existing memories remain intact # Just add MCP server registration claude mcp add memory-service spawn -- /path/to/memory/command ``` #### From MCP Server to Commands ```bash # Install commands alongside existing setup python install.py --install-claude-commands ``` ### Data Compatibility 🟢 **Full Compatibility**: Both methods use the same underlying memory service and database. Memories stored via commands are accessible via MCP server and vice versa. --- ## Real-World Examples ### Commands Workflow ```bash # Start development session claude /memory-context --summary "Starting OAuth integration work" # Store decisions as you work claude /memory-store --tags "oauth,security" "Using Auth0 for OAuth provider" # Later, recall what you decided claude /memory-recall "what did we decide about OAuth last week?" # Check everything is working claude /memory-health ``` ### MCP Server Workflow ```bash # Start Claude Code session claude # In conversation with Claude: "Please store this OAuth integration decision in memory with tags oauth and security" "What did we decide about authentication last week?" "Show me all memories related to security decisions" ``` --- ## Making Your Choice ### Start with Commands if: - 🟢 You want to try the memory service quickly - 🟢 You're working on individual projects - 🟢 You prefer direct command interfaces - 🟢 You want automatic context detection ### Choose MCP Server if: - 🟢 You're already using other MCP servers - 🟢 You need maximum flexibility and control - 🟢 You prefer conversational interactions - 🟢 You're building complex multi-tool workflows ### Why Not Both? - 🚀 Install commands for quick access - 🔧 Set up MCP server for deep integration - 📈 Use the best tool for each situation - 🎯 Maximum flexibility and capability --- **Remember**: Both methods provide the same powerful memory capabilities - the choice is about interface preference and workflow integration! 🎉