clickup-custom-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLICKUP_TEAM_ID | No | Pin a workspace. Without it the first workspace the token can see is used. | |
| CLICKUP_API_TOKEN | Yes | Personal API token. Required; the server exits with a message if unset. | |
| CLICKUP_RATE_LIMIT | No | Requests/minute the client allows itself. Defaults to 90. | 90 |
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_workspace_mapA | The workspace's spaces, folders, lists (with their status names) and members, plus your own numeric user id. Call this first when you need an id for any other tool. Cached for 15 minutes, so repeat calls are free. |
| get_my_workA | Every open task assigned to you across the whole workspace, grouped by overdue / today / this week / later. This is the one to call for a standup, a 'what's on my plate' question, or a backlog sweep. |
| search_tasksA | Filtered task query across the entire workspace in one request — the tool to build any report or analytics on. Every filter is optional and they combine. Paginates automatically and says so if it hits the cap. |
| get_taskA | Full detail for one task: description, custom field values, subtasks, and optionally its comments. Use it after search_tasks or get_my_work has narrowed things down to a single task. |
| create_taskA | Create one or many tasks in one go — pass the whole array when breaking a discussion into a backlog, rather than calling this repeatedly. Each task is reported individually; one failure does not abort the rest. |
| update_taskA | Update one or many existing tasks — status changes, re-assignment, due dates, renames. Pass the whole array for a bulk change. Each update is reported individually. |
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 6 tools
Each tool targets a distinct operation: create, update, workspace mapping, personal work list, search, and single-task detail. There is no overlap in purpose or ambiguity about which tool to use for a given action.
All tool names follow a consistent verb_noun pattern in snake_case (create_task, update_task, get_workspace_map, get_my_work, search_tasks, get_task). The naming is predictable and uniform.
Six tools is a well-scoped set for a task management integration. Each tool covers a distinct aspect of task handling without redundancy or unnecessary bloat.
The set covers create, update, query, search, and single-task retrieval, which handles most task workflows. The main gap is the lack of a delete_task tool, but this is a minor omission given the core lifecycle is otherwise present.