Claude ClickUp community connectorWhat the desktop extension by an independent developer can do in your ClickUp account.
This Claude ClickUp community connector exposes 13 tools. 6 read tasks, lists, time and docs, 7 change something in your workspace, and 0 lack a description. Below: how this desktop extension differs from ClickUp's official connector, and the settings that decide what it can touch.
Verified Trustpilot reviews · AI, automation & growth agency
Why pick this ClickUp extension for Claude
The directory lists two ClickUp entries, and they are not the same product. This one is a desktop extension written by an independent developer and installed on Claude Desktop with a personal ClickUp API key. Its publisher pitches its minimal read mode at coding assistants and context gathering, where rich task detail matters more than breadth.
A task with its whole story. getTaskById returns a task together with its comments, threaded replies, images and metadata in one call, which is what a developer wants before fixing the bug described in it.
Time logged without leaving the chat. createTimeEntry books hours on a task, and getTimeEntries shows where the week went, handy for freelancers who bill by the hour.
Docs you can read and extend. Claude can read a ClickUp Doc page by page, add a new page or edit an existing one.
What it cannot do, per its publisher: search only covers recent tasks with fuzzy matching, not ClickUp's full search database, and there is no Chat and no search across connected apps. It installs locally, runs only on Claude Desktop and relies on community support. The publisher points to ClickUp's official remote connector for sign-in security, Chat and official support. Nothing fires on its own either; for workflows that react to ClickUp events, see the Integrations hub.
Five words before you install
The terms that matter for this extension, 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.
- Desktop extension
- A connector that installs and runs on your own computer inside Claude Desktop, instead of being hosted by the service online.
- Tool
- One named action the connector gives Claude. Claude decides which ones to call, and the directory lists all of them by name.
- 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 talk to an outside service such as ClickUp.
Install the ClickUp extension in three steps
- 01
Find it in Claude Desktop
In Claude Desktop, open Customize then Connectors and look for the ClickUp entry published by an independent developer, not by ClickUp. On a Team or Enterprise workspace, an Owner or Primary Owner has to allow it first.
- 02
Start the installation
Launch it from its row. There is no ClickUp sign-in window here: the publisher says a configuration screen asks for your ClickUp API key and team ID instead. To cut the link later, Disconnect it or remove the key.
- 03
Mind what the key opens
No ClickUp authorization screen appears: the API key you paste is what decides the reach, since the publisher offers no other sign-in. Treat that key like a password.
The 13 tools, split by what they do
ClickUp gives Claude 13 tools: 6 that read your account, 7 that change something in it.
The publisher documents each tool in a table, so everything falls into two groups. Names stay exactly as Claude shows them.
- 6 read
- 7 write
What Claude reads (6)
6 toolsTasks, spaces, lists, time and documents, consulted and left as they are.
getTaskById
Returns everything about one task in a single call: description, comments with their threaded replies, images and metadata. The publisher describes it as complete task details.
searchTasks
Finds tasks from their content, keywords, assignees or project context, with fuzzy matching.
searchSpaces
Walks through the structure of your workspace, how projects are organised and which documents sit where. Claude uses it to find its way before opening anything.
getListInfo
Reads a list's description and its available statuses. Claude needs it to know which statuses exist before placing or reporting on tasks in that list.
getTimeEntries
Shows the time logged across projects, so Claude can total hours and spot where the week actually went, project by project, which the publisher calls analysing time spent.
readDocument
Opens a ClickUp Doc with its details, page structure and content, and lets Claude go from page to page as it reads.
What Claude changes (7)
7 toolsComments, tasks, list descriptions, time entries and doc pages. No source spells out a confirmation, so the general rule below applies.
addComment
Approval: see the rulePosts a comment on a task, or a reply inside an existing comment thread. Replies are attached to the thread through the parent comment, per the publisher.
updateTask
Approval: see the ruleChanges a task's status, priority, assignees and other fields, and its description too, which the publisher says can be appended to or replaced entirely.
createTask
Approval: see the ruleCreates a new task with a markdown description, in the list you name, with full markdown support, per the publisher.
updateListInfo
Approval: see the ruleAdds text to a list's description without erasing what is already there; the publisher labels it append-only and safe.
createTimeEntry
Approval: see the ruleRecords a time entry on a task, so the hours land in ClickUp without opening it.
updateDocumentPage
Approval: see the ruleUpdates the content or the name of an existing page in a ClickUp Doc, in replace or append mode according to the publisher.
createDocumentOrPage
Approval: see the ruleStarts a fresh Doc with its first page, or adds pages and sub-pages to a Doc that already exists.
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, and they can narrow a connector for the whole organization, for example reading allowed and writing blocked. Nobody lifts that from a personal account. Claude works with the rights of the person who connected; here that means whatever the ClickUp API key can reach. The publisher adds a lever of its own: three modes, from a minimal read-only set to full writing, with writing on by default.
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 like this one install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members use it. Neither the publisher nor Anthropic says more about this extension. For the live state, open its sheet in the official directory.
Where the Claude ClickUp community connector stops
A connector is not an automation. Claude calls these tools while it replies, so nothing happens when a task is created or completed.
Everything here comes from the directory sheet and the publisher's README on GitHub; neither ClickUp nor Anthropic documents this extension. The partner badge is not a security audit, and Anthropic says on every sheet that it does not control a publisher's tools or vouch for them. The README also describes two tools, editComment and searchDocuments, that the sheet does not list: this page does not count on them. For a case where two official sources disagree, see the Claude gmail connector page.
Can updateTask overwrite a task's existing description?
- Publisher's README, safety features section ↗Read September 2026, undatedOut of dateDescriptions are append-only: they are never overwritten, and new content is added with a timestamp.
- Publisher's README, tool table ↗Read September 2026, undatedupdateTask can append to a description or replace it entirely.
What this page followsThe same README says both. We follow the tool table, the more detailed and tool-specific of the two, and assume an update can replace a description. Ask Claude to append when the existing text matters.
Need help connecting ClickUp to Claude?
A person reads every message.
