Full read-write Claude connector for ClickUp
Make Claude create tasks and move work across statuses in ClickUp
Stop clicking through ClickUp to triage and update tasks by hand. Claude creates tasks in the right list, sets assignees and due dates, moves items across statuses, and updates custom fields where the work already lives, with deletes left for you to approve.
ClickUp is a work management platform where teams run tasks, docs, sprints, and goals across spaces and lists. People want Claude to do more than report on it: to create and update tasks, move work across statuses, and keep assignees and due dates current.
What is a ClickUp MCP server?
A ClickUp MCP server is a small hosted service that exposes ClickUp's data and actions to Claude over the Model Context Protocol, so Claude can tasks, projects, and docs inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.
What can ClickUp's current connector do today?
Today, ClickUp's available Claude connection tends to be read-leaning or to cover a thin slice of the API, so Claude can surface tasks and details but in-app updates like creating tasks, changing status, or editing custom fields are limited. A custom connector adds those write actions with scoped, human-in-the-loop controls.
What does full read-write ClickUp access unlock?
Full read-write ClickUp access lets Claude create tasks in the right list, set assignees and due dates, move items across statuses, update custom fields, and post comments, then leave deletes for you to approve. The triage and updating that used to mean clicking through ClickUp happen where the work already lives.
- 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
- Find every task matching a query and propose batched updates
- Create a subtask under an existing parent task
Can Claude create and update tasks in ClickUp?
Yes, Claude can create and update tasks in ClickUp with a full read-write connector. It creates a task in a specific list with description, assignees, and due date, then edits priority, tags, and custom fields on existing tasks. The default connection is often read-leaning, so in-app creation and editing need a purpose-built connector.
Can Claude move a ClickUp task across statuses?
Yes, Claude can move a ClickUp task across statuses as work progresses, add a comment or checklist item to keep it current, and create a subtask under an existing parent. It can also find every task matching a query and propose batched updates for you to review before anything changes.
Will Claude delete a ClickUp task without my approval?
No, Claude will not delete a ClickUp task without your approval. Delete is a separate, gated write action, while create, update, and comment flow freely. The connector authenticates as your account through OAuth and inherits your existing permissions, so it never reaches more than you already can.
How a ClickUp connector works
We build a small MCP server that authenticates to ClickUp with OAuth and the narrowest scopes the work needs. Read tools (search, list tasks, read task) and write tools (create, update, comment) are separated, and destructive actions like delete require your confirmation. Claude only ever has the access your own ClickUp account already has.
Frequently asked questions
Can Claude create and update tasks in ClickUp, not just read them?
Will Claude delete a ClickUp task without my approval?
Does the ClickUp connector get more access than I have?
Related connectors
Tell us what you run. We'll build the connector.
Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.