No user-submitted related servers found.
Scored across 35 tools
Several tools overlap meaningfully: log_work(kind=change/learning/problem/todo) duplicates log_change, log_learning, problem, and todo; ask/search/get_learnings/get_recent_changes all retrieve records; and start_here vs get_context both return session context. Descriptions do help an agent pick correctly, but boundaries are genuinely blurred in the write path.
Two clear conventions coexist: verb_noun tools (create_project, log_learning, review_approve, get_recent_changes) and bare resource nouns that dispatch via an action parameter (todo, session, file, git, variable, method, rules, problem). Each family is internally predictable, but the split is roughly half-and-half rather than a minor deviation.
35 tools is above the 25+ heavy threshold for a project-memory server. While many consolidate multiple operations behind an action parameter, the surface is still large and the count alone makes selection cost high.
Coverage is broad and coherent: projects, components, learnings, changes, problems, attempts, todos, sessions, files, git, variables, methods, links, review workflow, rules, history/undo, import, and cleanup. The main gap is explicit deletion for projects, components, learnings, and changes (partially mitigated by history undo), which agents can work around.