Context Hub
Related Servers
Alternatives to Context Hub
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceUnifies cited transcript search, auto-compressed session context, and hand-curated notes behind a single MCP server, letting AI coding agents look up past discussions, check what was just happening, and store or recall durable facts across projects.7MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search scattered notes and docs, ask cited questions, store or retract durable memories, explore links, and inspect or refresh the local index through shared MCP tools.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to discover and create agents, durably submit messages with verifiable replies, and search source-linked local memory. Exposes eight authenticated tools with owner-approved OAuth, transcript-backed verification, and explicit control over history import and embedding.MIT
- AlicenseNot gradedqualityCmaintenanceProvides coding agents with persistent, queryable repository memory over MCP, enabling code search, cited question answering, repo maps, decision logs, and cross-session notes through local-first tools.394 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables two local coding agents to read each other's user-visible history, search past decisions with source tracing, and save confirmed conclusions into a shared memory. Also supports credential-status checks and limited task handoff between Codex and Antigravity over MCP stdio.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI clients to search and ask questions over local notes, docs, and agent memories with cited answers, while also storing or retracting durable memories, exploring links, and refreshing indexes through shared MCP tools.-
TDQS
Scored across 12 tools
Most tools target distinct actions: create/list matters, read/search context, save notes, register sources, and refresh status. However, link_context and relate_matters both create associations, and continue_matter/search_context/read_notes/read_record overlap conceptually around retrieval, requiring careful description reading.
Names are predominantly snake_case with a verb_noun pattern such as continue_matter, list_matters, create_matter, and search_context. Minor deviations are remember (verb-only) and context_status (noun phrase), which are still clear but break the convention.
The server has 12 tools, squarely within a reasonable range, and each maps to a distinct part of the context/memory lifecycle. No obvious padding or missing essential utility.
The set covers creation, listing, reading, searching, association, source registration, and refresh/status. It lacks delete/unlink/update operations for matters and associations, and note retraction/editing is not explicitly available, which are notable lifecycle gaps.