No user-submitted related servers found.
Scored across 27 tools
Most tools have clearly distinct targets: checks vs rules vs specs vs docs vs graph vs skills vs memory. The main ambiguities are the aggregator `get_context` (which overlaps the individual `get_*` retrievers, though its description explains the ranking/token-budget role) and `get_plan_board` vs `get_planning_context`, plus the explicitly-deprecated `get_guardrails`/`create_guardrail` aliases that duplicate `get_checks`/`create_check`.
Almost all tools follow a snake_case verb_noun pattern (get_*, create_*, publish_*, list_*, install_*, sync_*). The only deviations are the legacy `guardrail` names kept for compatibility, which still fit the pattern but add a second name for the same concept.
27 tools is above the comfortable range, and two are deprecated duplicates that inflate the count. The surface is genuinely broad (context retrieval, graph, checks, specs, skills, setup, memory), so the volume is partly justified, but several retrieval tools could be consolidated.
Read coverage is strong (tech stack, checks, specs, docs, graph, boards, team setup, memory) and writes exist for checks, rules, prompts, decisions, and spec updates. However, there is no update/delete for checks, rules, or prompt templates, no create/delete for specs (only update of drafts), and no way to unpublish skills or setup parts, leaving notable lifecycle gaps.