clickup-mcp
Related Servers
Alternatives to clickup-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceA comprehensive MCP server for the ClickUp API exposing 166 tools to manage Spaces, Folders, Lists, Tasks, Docs, and more, enabling LLMs to read and drive a ClickUp Workspace.1001Apache 2.0
- AlicenseBqualityBmaintenanceA Model Context Protocol (MCP) server providing AI assistants with comprehensive ClickUp integration, covering the full API surface across 87 consolidated tools.87174 npmMIT
- FlicenseNot gradedqualityDmaintenanceComplete Model Context Protocol server for ClickUp, enabling interaction with tasks, spaces, lists, docs, goals, time tracking, and more through 93 tools and 18 React MCP apps.-
- AlicenseBqualityBmaintenanceLightweight ClickUp MCP server for task management with 37 tools and token-optimized responses to reduce API verbosity.3741 npm3MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables integration with ClickUp project management platform through a Model Context Protocol server, providing tooling for task management, workspace operations, and team collaboration with flexible authentication and deployment options.174 npm-
- AlicenseNot gradedqualityBmaintenanceMCP server enabling AI assistants to interact with ClickUp workspaces, including task management, comments, time tracking, and document operations.12 npmMIT
TDQS
Scored across 97 tools
Most tools target distinct resource-action pairs (e.g., create_space vs create_list vs create_folder are clearly different). A few potential overlaps exist: get_time_entries vs create_time_entry vs start_timer manage similar data, and get_task_watchers/add_task_watcher overlap with task membership. Overall boundaries are mostly clear.
The vast majority follow a consistent verb_noun pattern (e.g., create_space, update_task, delete_comment, get_lists). Minor deviations exist: get_folderless_lists, get_filtered_team_tasks, and set_custom_field_value break the simple verb_noun form but are still readable and logical.
97 tools is far too many for most agentic use cases, despite ClickUp's broad surface. The count exceeds the heavy threshold (25+) by a wide margin, and the score reflects that the surface is bloated even if ClickUp genuinely offers this many operations.
The coverage is remarkably comprehensive: full CRUD across workspaces, spaces, folders, lists, tasks, comments, time entries, goals, key results, checklists, tags, views, webhooks, guests, and custom fields. There are essentially no dead ends—everything from creation through deletion is covered.