How Memory MCP integrates with our five-component memory system
- Document navigation - Clicking between [[memory-human]], [[memory-ai]], etc.
- Static references - Links that don't change often
- Human reading flow - When you want linear, narrative connections
- Dynamic relationships - Connections that evolve over time
- Complex associations - Multi-way relationships between concepts
- Searchable knowledge - Finding patterns across all memory
- AI analysis - When AI needs to understand relationship networks
# Add major project concepts to knowledge graph
mcp_memory_create_entities([
{name: "CEIS-NIA-2025", entityType: "project", observations: ["Net Impact Analysis implementation for 2025"]},
{name: "TWaNG-methodology", entityType: "method", observations: ["Propensity score weighting approach"]},
{name: "Phase-1-complete", entityType: "milestone", observations: ["Memory hub established with wiki-links"]}
])
# Connect decisions over time
mcp_memory_create_relations([
{from: "Memory-System-Evaluation", to: "Phase-1-Implementation", relationType: "led-to"},
{from: "Phase-1-Implementation", to: "Wiki-Link-Network", relationType: "created"},
{from: "Wiki-Link-Network", to: "Enhanced-Navigation", relationType: "enables"}
])
# Find all project decisions
mcp_memory_search_nodes("decision implementation phase")
# Find methodology connections
mcp_memory_search_nodes("TWaNG methodology propensity score")
- Use MCP for relationships, wiki-links for navigation
- Don't duplicate - if it's in [[project-memory]], just reference it in MCP
- Focus on concepts and connections, not detailed content
- MCP for discovery ("What connects to X?")
- Wiki-links for navigation ("Go to document Y")\
- VS Code search for content ("Find all mentions of Z")
- Document in [[memory-human]] or [[memory-ai]]
- Navigate with wiki-links
- Connect concepts with Memory MCP when needed
- Search with VS Code or MCP depending on need
This approach keeps each tool focused on what it does best while integrating with our five-component memory system.