Related Servers

The functional tools are carefully delineated (recall vs recall_at_time, store_memory vs upload_document, update_fact vs end_fact vs unlink_entities all have explicit 'use X instead of Y' guidance). However, seven tools are exact duplicate aliases (health, recall, stats, entity, link, schema, unlink) that shadow their replacements, so an agent must disambiguate between two identically-described tools on nearly every call.

The active surface follows a clean knowmind_verb_noun snake_case pattern (get_health, store_memory, link_entities, recall_at_time). The deprecated aliases break that convention with bare single-word names (health, entity, link, schema, unlink, stats, recall), leaving two naming styles side by side. Readable, but not the single predictable pattern a 5 requires.

23 tools is at the heavy end, and 7 of them are deprecated duplicates retained for a year, so the effective surface is ~16 with 7 legacy clones inflating the count. The functional set is reasonably scoped for a memory/graph store, but the aliases make it feel bloated.

Coverage is strong: write (store, upload, update, end), graph build (upsert entity, link, unlink), review lifecycle (list_inferred, review_inferred), and read (recall, recall_at_time, list_recent, list_relations, stats, health, schema). Minor gaps exist — no direct get-by-id for a single memory or entity, and no way to look up an entity by name other than the idempotent upsert — but these are workable.