graph-mind
Related Servers
Alternatives to graph-mind
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceSaves the user's exact words as immutable, SHA-256-hashed captures before anything else, then derives events, entities, context cards, and causal hypotheses — every fact traceable to its verbatim source. Local-first personal memory for Claude Code, Codex, and any MCP client.133MIT
- AlicenseNot gradedqualityDmaintenanceCross-machine memory system for Claude Code that records sessions as searchable markdown, syncs across machines via Git, and exposes full-text search, semantic search, session summarization, and a knowledge graph through an MCP server.30 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code and other LLM agents to capture, consolidate, and retrieve memories from conversation history, building a local-first knowledge graph with semantic search and dream-state consolidation.42 npm1MIT
- AlicenseAqualityCmaintenancePersistent memory for Claude Code. Automatically indexes every conversation and provides production-grade hybrid search (BM25 + vectors + reranker) via MCP tools. 100% local, zero config, zero API keys, zero invoice.1637 npm7MIT
- AlicenseNot gradedqualityAmaintenanceA graph-based MCP server that provides AI coding agents with persistent memory to store patterns, track complex relationships, and retrieve knowledge across sessions. It leverages graph structures to handle temporal queries and relational paths that traditional vector stores often miss.251MIT
- AlicenseNot gradedqualityAmaintenanceTestGraph is a shared structured knowledge and review graph for AI agents. Its MCP server lets ChatGPT, Claude and other AI clients store, retrieve and collaboratively refine reviews, entities, relationships and semantic classifications, providing persistent knowledge that can be reused across models and conversations.AGPL 3.0
TDQS
Scored across 7 tools
Descriptions go out of their way to route the agent (recall vs context, folder vs checkpoint), so boundaries are mostly clear. However, brain_recall/brain_context are two views of the same memory data and brain_folder/brain_checkpoint both concern sharing, which are genuine overlaps that require reading long guidance to resolve.
Six of seven tools use a consistent brain_ + verb/noun pattern (brain_recall, brain_remember, brain_context, brain_folder, brain_checkpoint, brain_forget). code_activity breaks the convention (noun_noun, no prefix), a minor but visible deviation.
Seven tools is well within the sweet spot and each earns its place across memory lifecycle, sharing, team, and code domains. No redundant or filler tools.
Coverage is broad: store, retrieve, delete, share across devices, team checkpoints, export/import, and code activity, with update handled via supersedes_memory_id. Some capability is packed into overloaded mega-tools (brain_folder, brain_checkpoint) rather than discrete operations, but no major workflow dead ends appear.