server-noonien
OfficialRelated Servers
Alternatives to server-noonien
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to maintain a shared, serverless, conflict-free knowledge graph across multiple machines by syncing append-only per-node shards. It provides drop-in compatibility with the official MCP memory tools while converging automatically without merge conflicts.Mozilla Public 2.0
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to store, search, and resolve shared memories with full provenance, conflict detection, and an audit trail across MCP-compatible clients.-
- AlicenseAqualityBmaintenanceMCP memory server for AI agents that gets better with use105Apache 2.0
- AlicenseNot gradedqualityAmaintenanceSemantic memory for AI agents — local-first MCP server with hybrid search, knowledge graph, contradiction detection, and plan-then-commit consolidation.243 npm4AGPL 3.0
- FlicenseNot gradedqualityBmaintenanceProvides a self-hosted shared memory service that lets AI agents capture and recall durable facts, decisions, and context across multiple tools and MCP-capable clients.3-
- AlicenseNot gradedqualityAmaintenanceSelf-hosted, local-first knowledge graph and memory server for AI agents. Enables agents to persist, recall, and organize knowledge through MCP with automatic distillation, deduplication, and cross-linking.MIT
TDQS
Scored across 14 tools
Each tool pairs a distinct resource (entity, observation, relation) with an action, and the update/merge tools clearly differentiate in-place edits from merges. The main soft spot is the read trio (read_graph, open_nodes, search_nodes), which are all retrieval operations and could occasionally be confused, though descriptions distinguish whole-graph paging, exact-name lookup, and query search.
Every tool follows a clean verb_noun pattern (create_entities, delete_observations, update_relations, merge_entities, read_graph, search_nodes). Conventions are uniform across all 14 tools with no mixing of styles.
14 tools is well within the sweet spot and each earns its place by covering a distinct resource-action pair across entities, observations, and relations plus graph-level reads. Nothing feels redundant or padded.
Full lifecycle coverage exists for all three resource types (create, update, delete on entities/observations/relations), supplemented by merge, rename-via-update, search, paged read, and conflict inspection. No obvious dead ends for a knowledge-graph workflow.