ClickUp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_taskC | Create a new task in a specific list |
| get_taskC | Get task details by ID (supports various ID formats including project codes) |
| update_taskC | Update task properties |
| delete_taskC | Delete a task |
| list_tasksC | List tasks in a list, folder, or space |
| search_tasksB | Search tasks across workspace |
| get_subtasksC | Get all subtasks of a parent task |
| get_task_commentsC | Get comments on a task |
| create_task_commentC | Create a comment on a task |
| get_task_statusC | Get current status of a task |
| update_task_statusC | Update task status |
| get_assigneesC | Get assignees of a task |
| assign_taskC | Assign users to a task |
| list_spacesB | List all spaces in workspace |
| list_foldersC | List folders in a space |
| list_listsB | List all lists in a folder or space |
| find_list_by_nameC | Find a list by name |
| bulk_update_tasksC | Update multiple tasks at once |
| bulk_move_tasksC | Move multiple tasks to a different list |
| get_time_trackedC | Get time tracked for tasks |
| log_timeC | Log time spent on a task |
| create_task_from_templateC | Create a task from a template |
| create_task_chainC | Create a chain of dependent tasks |
| get_team_workloadC | Get workload distribution across team members |
| get_task_analyticsC | Get analytics for tasks (velocity, completion rate, etc.) |
| list_usersC | List all users in the workspace |
| get_current_userA | Get details of the currently authenticated user |
| find_user_by_nameC | Find a user by name or email |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 28 tools
Most tools have distinct purposes, but some overlap exists, such as 'update_task' and 'update_task_status' (which could be seen as a subset), and 'list_tasks' and 'search_tasks' (both retrieve tasks but with different scopes). Descriptions help clarify, but agents might occasionally misselect between these pairs.
Tool names follow a highly consistent verb_noun pattern throughout, with clear actions like 'create', 'get', 'list', 'update', 'delete', and 'find'. There are no deviations in style, such as mixing camelCase or snake_case, making the set predictable and readable.
With 28 tools, the count is borderline high for a task management server, potentially feeling heavy and overwhelming. While it covers many operations, it might benefit from consolidation or scoping down to avoid complexity, as typical well-scoped servers have 3-15 tools.
The tool set provides comprehensive CRUD and lifecycle coverage for the ClickUp domain, including task management (create, get, update, delete, search), user and list operations, analytics, time tracking, and comments. There are no obvious gaps, and agents can handle full workflows without dead ends.