No user-submitted related servers found.
Scored across 15 tools
Most tools have crisp, distinct purposes (ingest vs query vs list_items, link_project vs current_project, session_update vs session_list), and the confirm/correct/forget trio is explicitly scoped to freshness-check results. The main overlaps are tasks_list vs tasks_what_next (both surface pending tasks) and the catch-all cf_tools, which makes agents uncertain whether a capability lives in the visible list or behind the gateway.
A clear namespace_prefix_verb_noun convention runs through memory_*, tasks_*, and session_* (memory_list_items, memory_check_freshness, tasks_list, session_update). Deviations are minor: cf_tools breaks the namespaced verb pattern entirely, and a few names are noun-only or state-like (memory_current_project, memory_help).
15 top-level tools sit at the top of the comfortable range and each maps to a real workflow (memory lifecycle, tasks, sessions, project scoping). The count is kept sane by pushing 55 capabilities behind cf_tools, though memory_confirm/correct/forget could plausibly collapse into one parameterized tool.
The memory surface covers list/create/search/delete, but general update and delete are absent from the visible list — descriptions reference memory_update and memory_delete as if they were callable, which is a dead end agents will hit. Task creation/completion and session teardown are also missing, forcing agents through cf_tools for routine CRUD.