clickup-mcp
Related Servers
Alternatives to clickup-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA 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
- AlicenseNot gradedqualityDmaintenanceA self-hosted MCP server that enables AI agents to directly interact with your ClickUp workspace, including tasks, lists, folders, comments, time tracking, and more via 51 tools over SSE.229 npmMIT
- AlicenseNot 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.MIT
- AlicenseBqualityBmaintenanceA Model Context Protocol (MCP) server providing AI assistants with comprehensive ClickUp integration, covering the full API surface across 87 consolidated tools.87229 npm1MIT
- AlicenseAqualityAmaintenanceA token optimised ClickUp CLI with built in MCP server that provides an efficient way to get data from ClickUp without consuming large amounts of LLM context10052Apache 2.0
- AlicenseBqualityBmaintenanceA Model Context Protocol (MCP) server exposing the full ClickUp REST API v2 as MCP tools, enabling natural language management of ClickUp workspaces, spaces, folders, lists, tasks, custom fields, comments, goals, views, webhooks, and time tracking via any MCP-compatible client like Claude Desktop or Cursor.9728 npmMIT
TDQS
Scored across 40 tools
Most tools target a distinct resource+action, and descriptions actively disambiguate tricky pairs like clickup_add_task_to_list (multi-homing) vs. clicking delete, and clickup_update_task vs. clickup_set_custom_field. Minor potential confusion exists between clickup_get_task/clickup_get_tasks and clickup_get_tasks/clickup_search_tasks, but descriptions make the boundaries clear.
Nearly all tools follow a predictable clickup_verb_noun pattern (create_task, update_task, get_comments, delete_checklist_item). A few deviate slightly, e.g. plural list-verbs like clickup_get_spaces/get_folders/get_lists and the standalone clickup_whoami, but the convention is readable and consistent overall.
At 40 tools, the surface is heavy even for a rich domain like ClickUp, exceeding the 25+ threshold where each tool starts to struggle for its place. While the underlying product is genuinely large, the set is bloated enough to raise selection overhead.
Core lifecycle coverage is strong: full CRUD for tasks, lists, checklists, checklist items, space tags, dependencies, and links, plus comments and threaded replies. Notable gaps remain, such as no create/update/delete for spaces or folders (read-only) and no way to delete a comment.