Related Servers

Most tools map to a distinct resource+action, and the descriptions go out of their way to separate easily-confused pairs (add_comment vs add_work_note, log_time vs stop_working, add_assignee vs update_task's assignee_user_id). The remaining overlaps are mild: resume_working duplicates start_working's resume behavior by the author's own admission, and log_time / quick_log / stop_working all touch time recording, requiring careful reading to pick correctly.

Nearly every name is snake_case verb_noun with a predictable verb vocabulary (create_/get_/list_/update_/add_/remove_/set_/start_/stop_/pause_/resume_/close_), making resource and action readable at a glance. Deviations like quick_log, report_bug, and update_task_status are still idiomatic and unambiguous within the same convention.

36 tools is heavy and sits above the comfortable band, but the domain genuinely spans products, projects, tasks, sprints, work sessions, assignments, verification, and support, so most tools earn a place. There is still consolidation headroom (log_time vs stop_working, resume_working vs start_working, record_verification_feedback), which pushes it to borderline rather than well-scoped.

Core workflows are covered end to end: product/project/task CRUD-ish surfaces, sprint lifecycle with cadence, measured work sessions, assignments, and AI verification. Notable gaps remain, though: no delete anywhere (tasks, projects, products, sprints), no update_product, no list_comments or way to read a task's comment thread, and no way to list or correct existing time entries other than the initial write.