No user-submitted related servers found.
Scored across 61 tools
Most tools target distinct ClickUp resources, but several boundaries are fuzzy: create_list vs create_list_in_folder, attach_task_file vs request_attachment_upload, get_task_comments vs get_threaded_comments, and search vs filter_tasks all require careful reading. The deprecated clickup_create_task_comment alongside clickup_create_comment adds avoidable confusion, and member resolution is split across get_workspace_members, find_member_by_name, and resolve_assignees.
Names overwhelmingly follow clickup_verb_noun in snake_case, which is predictable and readable. Minor deviations exist, such as find_member_by_name and resolve_assignees using different verbs, plus the legacy clickup_create_task_comment, but the overall convention is stable.
At 61 tools, the surface is very heavy for an agent to navigate reliably, exceeding the 25-tool threshold where selection errors become likely. ClickUp is broad, but the count includes deprecated tools and generic operator indirection, making the set feel overgrown rather than tightly scoped.
Core task, comment, list, folder, document, chat, time-tracking, reminder, tag, dependency, and attachment workflows are covered. However, obvious lifecycle gaps remain for a ClickUp server: no dedicated space creation/update/delete, no folder/list deletion, no document/page deletion, and limited time-entry management. The generic execute_operator may fill some gaps, but only when enabled, so the dedicated tool surface is notably incomplete.