No user-submitted related servers found.
Scored across 11 tools
Most tools have clear, distinct roles: memory ingest/query/freshness tools, task list/next tools, session list, and the catch-all cf_tools. There is mild overlap between tasks_list and tasks_what_next, and cf_tools can serve as an alternate entry point for capabilities, but the descriptions provide strong usage triggers.
The tools mostly follow a clear prefix-plus-verb pattern like memory_ingest, memory_query, tasks_list, and session_list. The main inconsistency is cf_tools, which breaks the naming convention, and memory_help/tasks_what_next are slightly less verb-oriented, but the overall pattern is still readable.
With 11 primary tools, the visible surface is well-scoped and within the ideal range for an MCP server. The cf_tools meta-tool cleverly keeps the count manageable while exposing 59 additional capabilities, so the apparent tool count matches the server's core workflows.
The memory lifecycle is well covered with ingest, query, freshness checking, confirm, correct, and forget, and task/session reading is present. General memory updates/deletes and task editing are not first-class tools but are accessible through cf_tools, which creates a minor discoverability gap rather than a true dead end.