Connect Claude to ClickUp

List the Workspaces this token can see, each with its members. ClickUp's API calls a Workspace a `team`, and the id returned here is the team_id every other operation takes. Call it first when you do not know which Workspace to act on, and to find out whether the connection reaches anything at all - an empty list means the token is valid and belongs to nothing. This is also the only place ClickUp exposes Workspace-wide membership; there is no space or folder member endpoint.

List the Spaces in a Workspace. Each Space record carries its own `statuses` array, which is where the statuses available to everything under it come from. Archived Spaces are excluded unless you ask for them.

List the Folders in a Space. Each Folder carries the Lists inside it, plus `statuses` and `override_statuses` - an empty statuses array means the Folder inherits from its Space rather than that it has none. Sub-folders come back flat, each tagged with its parent_folder.

List the Lists inside one Folder. A ClickUp Space can also hold Lists that sit in no Folder at all, and those never appear here - use list_folderless_lists for them. The list_id returned is what list_tasks and create_task take.

List the Lists that sit directly in a Space with no Folder around them. ClickUp serves these from a different endpoint than the Folder ones, so a walk that only calls list_lists silently misses them - which is how a list an agent can see in the ClickUp UI turns out to be unreachable.

Report the statuses a List actually accepts, so create_task and update_task can be given a status ClickUp will take rather than one that is rejected. ClickUp has no statuses endpoint - statuses are a property of the List, Folder and Space records - so this reads the List itself and returns its status set alongside its name and task count. `override_statuses` false means the set is inherited from the Folder or Space above it.

List the people with explicit access to a List. ClickUp's own documentation is precise about what this leaves out: it does not include anyone whose access comes from the Workspace, the Folder or the Space above the List, so an empty result does not mean nobody can see it. For Workspace-wide membership, read the members array on list_workspaces. The ids returned here are what create_task takes as assignees.

List the tasks in one List, with every filter ClickUp offers. Three defaults are easy to trip over and are stated here rather than discovered: closed tasks are excluded, subtasks are excluded, and `page` starts at 0. A page holds at most 100 tasks and `last_page` on the response says whether there are more. Tasks whose home List is elsewhere but which also appear in this one are excluded unless include_timl is set. Every date filter is a Unix timestamp in milliseconds.

Fetch one task in full: description, status, assignees, watchers, dates, priority, tags, custom field values and its List, Folder and Space. IMPORTANT: to address a task by the short custom id your Workspace shows (ABC-123) rather than by its internal id, you must set custom_task_ids to true AND pass team_id - ClickUp documents both together, and sending the custom id without the Workspace id is not a supported call.

Read a task's comments, newest first. Paging here is a cursor rather than a page number and needs BOTH parts: `start` is the `date` of the last comment you saw and `start_id` is that same comment's `id`. Sending one without the other does not page - it returns the first page again, which reads like the task has fewer comments than it does.

Create a task in a List. Only `name` is required. `status` must be one the List actually has - call list_statuses first - and assignees are numeric user ids from list_members, not names or emails. Dates are Unix timestamps in milliseconds; pass due_date_time or start_date_time as true when the timestamp carries a meaningful time of day rather than just a date. If both description and markdown_content are given, ClickUp uses markdown_content and ignores the other.

Change fields on an existing task, or archive it. Pass only what you want changed. Assignees and watchers are NOT replaced the way every other field is - ClickUp takes them as an add-and-remove pair on update, so add_assignees and remove_assignees are separate arguments here and leaving both out changes neither. Set archived true to archive the task, which is reversible and is not the same as deleting it.

Post a comment on a task. `notify_all` decides whether everyone watching the task is emailed, and it defaults to false here so an agent leaving a note does not mail a team by accident - pass it as true when the comment is meant to reach people. `assignee` turns the comment into an assigned comment for that user.