Relay
Related Servers
Alternatives to Relay
No user-submitted related servers found.
Related Servers
- 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-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to store, search, and resolve shared memories with full provenance, conflict detection, and an audit trail across MCP-compatible clients.-
- AlicenseNot gradedqualityBmaintenanceGives any MCP client (Claude, ChatGPT, Cursor, and others) one shared knowledge-graph memory where agents record decisions, problems, and approaches together with their reasoning, then retrieve them by meaning rather than keyword. Spreading activation pulls in linked context and decay lets unused knowledge fade without deleting it.14Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables teams of AI coding agents (Claude Code, Cursor, Codex) to share persistent, time-aware graph memory and coordinate their work via MCP, so agents recall verified fixes at the moment of failure, learn procedures automatically, avoid file conflicts, claim tasks race-free, and hand off facts and decisions between sessions.MIT
- AlicenseAqualityCmaintenanceProvides a local-first, provenance-aware memory layer that enables MCP-capable AIs to store, recall, validate, and reason over facts with contradiction detection, trust weighting, deduplication, and encryption, supporting offline private operation without GPUs or API keys.9Apache 2.0

server-noonienofficial
AlicenseAqualityAmaintenanceShared, serverless, conflict-free memory for AI agents — a multi-machine drop-in for the MCP memory knowledge graph.14824 npm2Mozilla Public 2.0
TDQS
Scored across 9 tools
Each tool has a distinct analytical lens (ancestry via get_context, recency via get_current_state, PageRank via get_important_facts, components via get_clusters, descendants via get_impact), and descriptions make these boundaries fairly clear. Minor overlap exists between get_current_state and get_briefing (both surface recent facts) and between get_context and get_impact (ancestors vs descendants), but the text disambiguates them.
All tools share the relay_ prefix and follow a consistent verb_noun pattern (save_fact, get_context, detect_conflicts, resolve_conflict, get_briefing). No mixing of conventions or stray verbs.
Nine tools is well-scoped for a graph-based shared-memory server: one write, several read/analytics lenses, and a conflict detect/resolve pair. Every tool earns its place without redundancy.
The surface covers the full lifecycle: write, contextual/recency/graph reads, conflict detection, and conflict resolution with staleness propagation, which is strong given the intentional append-only, no-delete design. The notable gap is content/keyword search — facts can only be retrieved by graph position or recency, not by text.