No user-submitted related servers found.
Scored across 34 tools
Most tools target distinct resources or actions, but several families have subtle boundaries: recall, recall_with_context, and reconstruct all retrieve memories, while check_health, deep_check, and get_session_findings all report diagnostics. The detailed descriptions explicitly steer between them, but an agent must read carefully to choose correctly.
All tool names use snake_case and most follow a verb_noun pattern such as get_profile, update_memory, delete_episode, and check_health. A few are bare verbs (store, recall, reconstruct, traverse) or noun-like (persistence_status), so the convention is readable but not perfectly uniform.
At 34 tools, the surface is well above the typical well-scoped range, mixing core memory operations with many niche admin, diagnostic, and maintenance tools such as check_update, get_queue_status, migrate_channel_axis, and pause/resume persistence. The breadth may reflect a mature backend, but it is heavy for an MCP server and increases selection cost.
The core memory lifecycle is well covered: store, update, delete, lock/unlock, list, recall/reconstruct, profiles, episodes, declared associations, import/export/merge, and health diagnostics. Minor gaps remain, such as no dedicated get/update for a single episode and no queue-management operations, but agents can work around them.
