Claude ClickUp connectorWhat ClickUp's official connector lets Claude do in your workspace.
The Claude ClickUp connector exposes 35 tools. 14 read your workspace, 20 change something in it, and 1 is described by no source. Below: what Claude can create, the daily call cap every client shares, and how this official version differs from the community extension.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude works in your ClickUp
Keeping ClickUp tidy eats time: turning meeting notes into tasks, chasing status updates, logging hours at the end of the week. With ClickUp's own connector, you describe the work to Claude and it searches the workspace, creates or updates tasks, logs time or posts in Chat, then reports back in the conversation.
From notes to tasks in one message. Paste the action items of a meeting and Claude files them in the right List with clickup_create_bulk_tasks, with assignees found through clickup_resolve_assignees.
A status report without the digging. Claude searches tasks, comments and Docs with clickup_search, reads the relevant pages, and drafts release notes or a weekly update from what it found.
Time tracked while you talk. It can start or stop a timer, or add a block of hours afterwards, so the timesheet is done before Friday.
What it does not do: the directory lists no tool to delete a task, even though ClickUp's developer table describes one, and the same goes for custom fields and task dependencies. Nothing runs by itself either; Claude calls these tools only while you talk to it. The directory also lists a separate, community-built ClickUp desktop extension with its own API key setup; this page covers ClickUp's official remote connector. For triggers that fire on every new task, see the ClickUp n8n integration page.
Five words before you connect
The vocabulary around this connector, explained once.
- Connector
- A link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector gives Claude. Claude chooses which ones to call on its own, and the directory lists them by name.
- Authorization
- ClickUp's sign-in and consent screen, where you grant the access Claude will use. Given once per person, and revocable.
- Approval
- The confirmation Claude waits for before doing something that changes your account, shown in the conversation when it matters.
- MCP
- The open standard connectors are built on: it is what lets an assistant like Claude call an outside service such as ClickUp.
Connect ClickUp to Claude in three steps
- 01
Find ClickUp in Claude
In Claude's settings, open Customize then Connectors, and look for ClickUp published by ClickUp itself. On a Team or Enterprise workspace, an Owner or Primary Owner must enable it for the organization first.
- 02
Sign in to ClickUp
Click Connect on its row and sign in within the window ClickUp opens. ClickUp says nothing has to be set up inside ClickUp beforehand. If the link breaks later, Disconnect and connect again.
- 03
Review ClickUp's consent screen
Read what ClickUp asks before you accept. The screen belongs to ClickUp, not to Claude, and it sets what the access covers. You can revoke that access later from the ClickUp side too.
The 35 tools, split by what they do
ClickUp gives Claude 35 tools: 14 that read your account, 20 that change something in it, and 1 no official source describes.
Three groups: what Claude reads, what it changes, and one name no source describes. Names stay exactly as Claude shows them.
- 14 read
- 20 write
- 1 not documented
What Claude reads (14)
14 toolsSearch, structure, tasks, comments, time, members, Chat channels and Docs, looked at and left alone.
clickup_search
Searches across the whole ClickUp workspace, tasks, Lists, Folders and Docs included, and returns what matches. It is usually the first thing Claude does when you mention a project by name.
clickup_get_workspace_hierarchy
Returns the full structure of your workspace: every Space, Folder and List. Claude uses it to know where things belong before filing anything. It is the map it relies on.
clickup_get_task
Retrieves everything about one task from its unique ID: description, status, assignees, dates and more. Claude reads it before answering a question about that task.
clickup_get_task_comments
Pulls all the comments on a task so Claude can summarise the discussion, pick out decisions and list what is still open.
clickup_get_task_time_entries
Retrieves every time entry logged against one task, so Claude can total the hours or see who worked on it and when.
clickup_get_current_time_entry
Checks whether you have a timer running at this moment and, if so, returns its details. Claude can then remind you what you are currently tracking.
clickup_get_list
Reads the settings of one List, including its custom statuses. Claude uses it to know which statuses exist in that List before it reports on progress.
clickup_get_folder
Returns the details of a single Folder, including the Lists it contains. It gives Claude a narrower view than the whole workspace map. Nothing outside that Folder appears.
clickup_get_workspace_members
Returns everyone in the workspace, members and guests alike. Claude uses it to answer who is on a team or who could take on a task.
clickup_find_member_by_name
Looks up one workspace member from a name or an email address and returns their user record, including the ID ClickUp needs behind the scenes.
clickup_resolve_assignees
A helper that confirms and retrieves the user records for a list of people you name, usually right before Claude assigns them to a task.
clickup_get_chat_channels
Lists all the Chat channels in the workspace. Claude reads it to find the right place before posting anything there.
clickup_list_document_pages
Returns the structure of a Doc, meaning its table of contents with all its pages. Claude uses it to find the page that answers your question.
clickup_get_document_pages
Retrieves the content of one or several pages of a Doc, so Claude can quote, summarise or compare what is written there.
What Claude changes (20)
20 toolsTools that create, edit, tag, time or post. No source spells out their confirmation, so the general rule below applies.
clickup_create_task
Approval: see the ruleAdds a new task to a given List, with a name, a description, assignees, a due date and a priority if you give them.
clickup_update_task
Approval: see the ruleChanges the properties of an existing task: name, description, status, assignees or due date. ClickUp's table lists those fields as examples.
clickup_create_task_comment
Approval: see the rulePosts a new comment on a task, to ask a question, share an update or mention a teammate so they get notified.
clickup_attach_task_file
Approval: see the ruleUploads a file, such as a document, an image or a ZIP archive, and attaches it to a specific task.
clickup_create_bulk_tasks
Approval: see the ruleCreates several tasks at once in one List, in a single call rather than one by one.
clickup_update_bulk_tasks
Approval: see the ruleModifies several tasks at once, typically their status, assignee or due date, which saves a lot of clicking on a group of tasks.
clickup_start_time_tracking
Approval: see the ruleStarts a timer on a task for the current user, exactly as if you had pressed the button in ClickUp.
clickup_stop_time_tracking
Approval: see the ruleStops the timer currently running for you, the one started on a task earlier.
clickup_add_time_entry
Approval: see the ruleAdds a block of time to a task after the fact, with a start and end time or a duration.
clickup_create_list
Approval: see the ruleCreates a new List inside a Folder or a Space, ready to hold tasks.
clickup_create_list_in_folder
Approval: see the rulePlaces a fresh List specifically inside a named Folder, the variant ClickUp documents for that exact placement.
clickup_update_list
Approval: see the ruleUpdates the settings of an existing List, such as its name or its color.
clickup_create_folder
Approval: see the ruleOpens a new Folder within a Space, to group related Lists together.
clickup_update_folder
Approval: see the ruleModifies the settings of an existing Folder, for instance its name.
clickup_add_tag_to_task
Approval: see the ruleApplies an existing tag to a task, the labels your team uses to sort and filter work.
clickup_remove_tag_from_task
Approval: see the ruleTakes a specific tag off a task, for when a label no longer applies.
clickup_send_chat_message
Approval: see the ruleSends a message to a ClickUp Chat channel you name, visible to everyone in that channel.
clickup_create_document
Approval: see the ruleStarts a new Doc in the workspace, as ClickUp's table puts it, ready for pages to be added.
clickup_create_document_page
Approval: see the ruleAppends a page, or a sub-page, to an existing Doc.
clickup_update_document_page
Approval: see the ruleEdits the content of an existing page in a Doc.
Undocumented (1)
1 toolOn the directory sheet, with no matching line in ClickUp's tool table. We do not guess its role.
clickup_get_workspace_tasks
This name appears on the directory sheet, but no line of ClickUp's tool table matches it without ambiguity, and no Claude page describes it. So this page says nothing about what it covers.
What Claude checks with you first
By default, Claude pauses and asks before each action it takes on an account for someone, inside the conversation.
On Team and Enterprise workspaces, owners decide whether members may let some actions through without a prompt each time, and they can narrow a connector for the whole organization, for example search allowed and task creation blocked. Nobody lifts that from a personal account. Claude works with the rights of the person who connected, and ClickUp says the same thing in its own words: an assistant can only do in ClickUp what you already have permission to do. The official per-tool label lives only in a signed-in account's settings.
Which Claude plans include it
None of the 819 sheets in the official directory states plan availability. That answer is published nowhere, connector by connector.
The published rule is general: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organization before members connect. ClickUp's setup guide adds its own reading of Claude plans; the limits section puts it next to Anthropic's rule. For the live state, open the connector's sheet in the directory.
Where the Claude ClickUp connector stops
A connector is not an automation. Claude calls these tools while replying, so nothing fires when a task is created or a status changes.
The tool list is an observed floor, not a promise: an administrator can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic says on every sheet that it neither chooses a publisher's tools nor vouches for them. What this page says comes from the directory sheet, ClickUp's help center and its developer portal; no Claude help article covers this connector. For an example of two official sources in open conflict, see the Claude gmail connector page.
Which Claude plans can connect ClickUp this way?
- Claude help center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise, an Owner enables each connector first.
- ClickUp developer portal, MCP setup guide ↗Read September 2026, undatedClickUp tells Pro, Team and Enterprise users to add the connector from Claude's settings, and Free users to set it up through the Claude desktop app's developer config instead.
What this page followsThe two texts do not line up, and it is the publisher describing Claude's plans, not Anthropic. Neither settles it for your account: check the connector's sheet in the directory on your own account.
Need help connecting ClickUp to Claude?
A person reads every message.
