No user-submitted related servers found.
Scored across 55 tools
Most tools have distinct purposes (git, fs, review, memory), but there is significant conceptual overlap: ck_memory_search vs ck_experience_search both perform freeform search over findings/tasks; ck_context vs ck_context_pack are adjacent and rely on descriptions to separate; several ck_experience_* tools overlap with ck_memory_search. Multi-mode tools like ck_task and ck_session pack many actions into one tool, making boundaries fuzzier.
Strong consistent ck_<domain>_<action> pattern (ck_fs_read, ck_git_diff, ck_memory_record, ck_review_submit). Minor deviations exist where domain is dropped (ck_validate, ck_route, ck_delegate, ck_copilot, ck_loop), but these are still readable and follow the ck_ prefix convention.
55 tools is heavy, well beyond the 15-tool sweet spot, and the surface spans many sub-domains (git, fs, memory, review, budget, delegate, deploy, skills, checkpoints, worktrees, copilot). This breadth makes selection costly and increases the chance of picking the wrong tool.
Coverage is broad and deep, with CRUD/lifecycle for memory, findings, reviews, goals, checkpoints, sessions, and git. Read-only exploration is well covered. Some operations are missing or indirect (e.g., no direct memory update tool—only re-record with source_id; no push tool), but most workflows can be completed.