ClickUp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLICKUP_API_KEY | Yes | ClickUp API key | |
| CLICKUP_TEAM_ID | Yes | Team (workspace) ID | |
| CLICKUP_DEFAULT_LIST_ID | No | Default list ID |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_teamsA | ClickUpのチーム（ワークスペース）一覧を取得します。 |
| get_spacesB | チーム内のスペース一覧を取得します。 |
| get_foldersA | スペース内のフォルダー一覧を取得します。 |
| get_listsA | スペース内のフォルダーに属さないリスト一覧を取得します。 |
| get_folder_listsB | フォルダー内のリスト一覧を取得します。 |
| create_taskC | ClickUpでタスクを作成します。 |
| get_tasksC | リスト内のタスク一覧を取得します。 |
| update_task_statusB | タスクのステータスを更新します。 |
| update_taskC | タスクの各フィールドを更新します（汎用更新）。 |
| delete_taskA | タスクを削除します（この操作は取り消せません）。 |
| get_task_detailB | タスクの詳細情報を取得します。 |
| search_tasksD | タスクを検索します。 |
| get_weekly_summaryC | タスクサマリーをAPIから取得します。 |
| add_commentC | タスクにコメントを追加します。 |
| get_task_commentsB | タスクのコメント一覧を取得します。 |
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 15 tools
Some tools have overlapping purposes, such as update_task and update_task_status, and get_lists vs get_folder_lists. While descriptions clarify the differences, an agent could still misselect between the generic update and specialized status update, or between the two list retrieval methods.
All tools follow a consistent verb_noun pattern using snake_case (e.g., get_teams, create_task, update_task_status, delete_task). The naming is predictable and uniform across the entire set.
With 15 tools, the server is well-scoped for a project management MCP. It covers the essential operations without being bloated, fitting comfortably within the ideal 3-15 range.
Task lifecycle is well covered (create, read, update, delete, search, comments), but the broader workspace hierarchy (teams, spaces, folders, lists) is read-only with no create/update/delete operations. This limits the server to task-centric workflows rather than full workspace management.