No user-submitted related servers found.
Scored across 9 tools
Most tools have clearly distinct purposes: recall searches, save writes, get_archive fetches full archives, draft_save/publish manage pipeline drafts. The only ambiguous pair is memory_recall and memory_context, which both retrieve relevant knowledge but differ in trigger scenario, so an agent might occasionally choose the wrong one.
All tools share a consistent memory_ prefix and most use a verb_noun pattern (get_archive, save, recall, archive_upsert, draft_publish, submit_response). memory_context breaks the pattern by using only a noun, and memory_save is a bit vague without an object, but the overall convention is predictable.
Nine tools is well-scoped for a team memory server covering search, save, archives, drafts, feedback, context, and response submission. Each tool serves a distinct part of the memory lifecycle without excessive granularity or missing core operations.
The tool surface covers the main workflows: saving, recalling, retrieving full archives, managing archive upserts, pipeline draft handling, feedback, and context. Minor gaps exist—there is no explicit delete or update operation for saved knowledge experiences, and no direct get-by-id for non-archive entries—but agents can work around these via recall and archive upsert.