mcp · handle sqlite_graph_memory
engram_5 · job 82%Ulysses Obsidian MCP · job 81%Brain Blueprint · job 79%journal-search · job 81%Graphmory · job 84%Maverick Bank · job 80%myMemory · job 80%zen_mcp_2 · job 82%Samong · job 79%Awareness Local · job 79%KMP · job 77%Agent Knowledge Memory Wiki · job 79%Vaults Hub · job 81%Episoda Alpha MCP · job 79%pseudolife_mcp · job 77%A2RG Obsidian MCP · job 81%RemainAI · job 77%CentricMem · job 80%DSH MemWiki · job 81%Obsidian Semantic MCP · job 80%enscribe · job 85%Agent Memory MCP · job 78%Loomkeep · job 77%Context Layer · job 81%Brain Graph · job 81%Ember-4 Memory · job 76%MCP Server for Obsidian · job 78%Memlio · job 78%codex_memory · job 77%snip · job 80%meshnote · job 76%okc-mcp · job 79%ha-agent-memory · job 75%engram_engram_memory · job 80%Zymor · job 79%remindb · job 79%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series