A
licenseA
qualityD
maintenanceA Model Context Protocol server that enables AI agents to interact with ClickUp workspaces, allowing task creation, management, and workspace organization through natural language commands.
21
13,055 npm
2
MIT
ClickUp MCP Integration
by Leanware-io
Related Servers
Alternatives to ClickUp MCP Integration
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceAn enhanced Model Context Protocol server that enables AI assistants to interact with ClickUp workspaces, supporting task relationships, comments, checklists, and workspace management through natural language.02-
- 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.268 npm-
- AlicenseBqualityBmaintenanceA Model Context Protocol (MCP) server providing AI assistants with comprehensive ClickUp integration, covering the full API surface across 87 consolidated tools.87268 npmMIT
- AlicenseAqualityFmaintenanceA Model Context Protocol server that bridges Claude with Google Tasks, allowing users to manage task lists and tasks directly through Claude interface.1557 npm49MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that connects AI assistants to your TickTick tasks, enabling task management through natural language.81MIT
TDQS
B3.1/5.0
Scored across 19 tools
Disambiguation4/5
Most tools have distinct purposes targeting specific ClickUp resources (docs, tasks, lists, folders, spaces), but there is some overlap between task-related tools (e.g., clickup_update_task and clickup_update_task_by_custom_id) and custom field tools that could cause confusion if not carefully distinguished by ID type. The descriptions help clarify, but the duplication in functionality for tasks and custom fields creates minor ambiguity.
Naming Consistency3/5
The naming is mixed: most tools use a consistent 'clickup_verb_noun' pattern (e.g., clickup_create_task, clickup_get_doc_pages), but some tools deviate with a simpler 'verb_noun' format (e.g., create_list, get_folders) without the 'clickup_' prefix. This inconsistency breaks the pattern and makes the set less predictable, though the names remain readable and descriptive overall.
Tool Count4/5
With 19 tools, the count is on the higher side but reasonable for a comprehensive ClickUp integration covering docs, tasks, lists, folders, and spaces. It feels slightly heavy due to some redundancy (e.g., multiple task and custom field tools), but each tool serves a specific purpose, and the scope justifies the number to handle various operations in the domain.
Completeness4/5
The tool set provides good coverage for core ClickUp operations, including CRUD for docs, pages, tasks, lists, folders, and spaces, as well as custom field management and search. Minor gaps exist, such as no direct tools for deleting resources or managing comments/attachments, but agents can likely work around these with the available tools for basic workflows in the domain.
Maintenance
ActivityInactive
ResponsivenessNo issues