Related Servers

Most tools target distinct operations, but there is notable overlap among retrieval/exploration tools: recall, hybrid_recall, nearby, discover_connections, corpus_bridges, journey, and wander all return semantically related memories with only subtle differences in scope. The descriptions help distinguish them, but an agent could easily select the wrong one, especially for recall vs. hybrid_recall and discover_connections vs. corpus_bridges.

Names are consistently lowercase snake_caseaine and readable, but they do not follow a single verb_noun convention; many are bare verbs (forget, recall, reinforce), while others are nouns or noun phrases (regions, stats, namespaces, corpus_bridges). This mix of imperative actions and declarative nouns is predictable enough to navigate but lacks the tight pattern of the highest-calibration servers.

At 25 tools, the server sits at the heavy end of the borderline range; the spatial memory domain can justify many operations, but the count feels inflated by a cluster of overlapping search and exploration tools. A tighter set closer to 18-20 tools would likely be just as capable and easier for an agent to navigate.

The surface covers the core memory lifecycle well: create (remember, remember_batch, extract), read/retrieve (recall, hybrid_recall, nearby), delete (forget, forget_batch, delete_namespace), plus namespace management, import/export, analytics, and maintenance. The main gap is the lack of a direct get_memory-by-ID tool and an update tool for editing memory content; users must work around this with forget-and-remember or importance-only mutation tools.