How to
How to connect Claude to ClickUp
ClickUp's available Claude connection can surface tasks and details. What it tends not to do is the part that saves time: creating tasks, moving them across statuses, and editing custom fields. That is what a custom connector adds.
Connect Claude to ClickUp with a custom MCP connector when you need writes, not just reports. The available connection tends to be read-leaning or to cover a thin slice of the API, so a custom build lets Claude create tasks in the right list, set assignees and due dates, move items across statuses, and update custom fields, with deletes gated for your approval.
Key takeaways
- ClickUp's available Claude connection tends to be read-leaning: surfacing tasks and details works, but creating tasks, changing status, and editing custom fields are limited.
- A custom ClickUp connector adds the writes: create a task in a specific list, move it across statuses, update custom fields, priority, and tags, and add comments or checklist items.
- Claude can also find every task matching a query and propose batched updates for your review before anything changes.
- The connector authenticates as your ClickUp account through OAuth, and delete stays a separate, gated action that waits for your approval.
Can Claude connect to ClickUp today?
Yes, but the available connection tends to be read-leaning or to cover a thin slice of the API. Claude can surface tasks and details, which handles status questions. In-app updates like creating tasks, changing status, or editing custom fields are limited, which is the gap a custom ClickUp connector fills.
The honest version first: if your team uses Claude to report on ClickUp, what is in this sprint, which tasks are overdue, what changed this week, a read-leaning connection may cover you. Try it before building anything.
The limit appears when the conversation should end in an updated workspace. Claude triages a batch of requests, decides which list each belongs in and who should own it, and then a human clicks through ClickUp re-entering all of it. A custom connector lets Claude do that last mile itself, with your approval where it matters.
The wider pattern holds beyond this one tool: in our June 2026 review of 264 business tools, 77 percent had no Claude connector at all, and none shipped full read-write out of the box.
How do I set up a custom ClickUp connector for Claude?
A custom ClickUp connector is built for you as a small MCP server that authenticates with OAuth using the narrowest scopes the work needs. Read tools like search, list tasks, and read task are separated from write tools like create, update, and comment, and delete requires your confirmation.
The path from request to working connector:
- 1Describe the ClickUp work Claude should handle, including the spaces, lists, statuses, and custom fields your team runs on.
- 2We build a small MCP server with read tools (search, list tasks, read task) separated from write tools (create, update, comment).
- 3You authenticate through OAuth as your own ClickUp account, so Claude inherits your existing permissions across spaces and lists.
- 4Claude starts creating and updating tasks in conversation, and destructive actions like delete run only after you confirm them.
Access is revocable at any time, and the connector never holds broader scopes than the work requires.
What can Claude do in ClickUp with write access?
With full read-write access, Claude creates a task in a specific list with description, assignees, and due date, moves tasks across statuses as work progresses, updates custom fields, priority, and tags, adds comments or checklist items, and creates subtasks under an existing parent task.
The tool set maps to the triage and updating most teams do by hand:
- Create a task in a specific list with description, assignees, and due date.
- Move a task across statuses as work progresses.
- Update custom fields, priority, and tags on existing tasks.
- Add a comment or checklist item to keep a task current.
- Create a subtask under an existing parent task.
Claude can also find every task matching a query and propose batched updates, which turns a Friday cleanup pass across a space into one reviewed change set instead of fifty individual edits.
Will Claude delete or change ClickUp tasks without asking?
No. Delete is a separate, gated write action that only runs after you approve it. Create, update, and comment can be allowed directly, and you decide which actions run automatically and which require a confirmation step before anything changes in ClickUp.
Most teams let searches and comments flow freely, keep task creation and status moves fast, and reserve confirmations for deletes and batched updates. Batched changes in particular are always proposed for review first, so a query that matches more tasks than you expected never rewrites a space silently.
Claude only has your access
The connector authenticates as your account through OAuth and inherits your existing permissions across spaces and lists. Anything Claude can touch is something you could already reach yourself, and access is revocable at any time.
When is a read-leaning ClickUp connection enough?
It is enough when your usage is genuinely reporting: sprint summaries, overdue lists, status digests. It stops being enough the first time Claude identifies work that needs a task, a status change, or a field edit, because a read-leaning connection makes you do every one of those by hand.
A quick self-test: write down the last five things you wished Claude had done in ClickUp. If they were all questions, keep the connection you have. If any of them was create this task, move these to done, or retag everything from that client, those are writes, and a purpose-built connector is what carries them.