MCP connectorsClickUp

ClickUp MCP: connect ClickUp to Claude and ChatGPT

Ask Claude or ChatGPT what’s overdue in the Website List, what was decided in a task’s comments or what your onboarding Doc says. The answer comes straight from ClickUp, with a link to the task. No clicking through Spaces and Folders.

With Deployed OS everyone connects their own ClickUp login and ticks the Workspaces to share. The AI sees what that person sees, and it only creates a task when someone asks for one and confirms the text.

7 read actions · 1 write action · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with ClickUp in Claude and ChatGPT

Project lead

Ready for stand-up

Every task in the sprint List that’s overdue or stuck in review, with assignees and the latest comments. Two minutes of reading instead of clicking through five views.
Team member

Your week in one answer

The tasks assigned to you that fall due in the next seven days, across the whole Workspace. Then open the one that matters and get its description and comments summarised.
Operations

Docs that answer back

Your processes live in ClickUp Docs. Ask how a return is handled or who signs off a purchase, and the AI reads the Doc and answers from it.
Any team

From meeting notes to tasks

Paste the notes from a meeting and ask for the follow-ups as tasks in the right List, with due dates. You check the text, the AI creates them. Assigning stays with you in ClickUp.
Examples

Ask it like this

  • “What’s overdue in the Website relaunch List? Show the assignee and due date for each task.”

  • “Which tasks assigned to me are due before Friday, across the whole Workspace?”

  • “Summarise the task ‘Migrate blog to new CMS’: where it stands and what the last comments say.”

  • “What does our Onboarding Doc say about a new hire’s first week?”

  • “Which tasks in the Q4 campaign List are still in Review, and when were they last updated?”

  • “Create a task in the Bugs List: ‘Checkout button missing on mobile Safari’, due 14 November, with these steps in the description.”

The connector

What the ClickUp MCP connector does today

  • Readsclickup_list_workspaces

    List the ClickUp Workspaces you shared when you connected.

  • Readsclickup_list_spaces

    List a Workspace’s Spaces: name, whether the Space is private, and the task statuses it uses.

  • Readsclickup_list_lists

    List a Space’s Folders with their Lists, plus the Lists that sit outside any Folder.

  • Readsclickup_list_tasks

    List tasks in one List or across a Workspace, 100 a page, latest updated first: only yours, by status, by due or updated dates, or with closed ones. It filters, it does not search by words.

  • Readsclickup_get_task

    Read one task: description, status, dates, assignees, where it lives, tags, subtasks, attachments by name, the latest comments and its link.

  • Readsclickup_list_docs

    List a Workspace’s Docs, 50 a page, with name and dates.

  • Readsclickup_read_doc

    Read a whole Doc as text, every page under its own heading.

  • Writesclickup_create_task

    Create a task in a List, with a description and due date if you want. Nobody is assigned or mentioned, and it only happens after you confirm the text.

Need it to do more? We extend connectors for the companies that use them.

Security

Who sees what

Read, plus new tasks
The connector reads Workspaces, Spaces, Lists, tasks with their comments, and Docs. It can create a task in a List with a description and due date. It cannot edit, close, assign or comment on anything in ClickUp.
Each person’s own Workspaces
Everyone connects their own ClickUp login and ticks which Workspaces to share. The AI sees what that person sees there, so a private Space they aren’t in stays out of reach.
You choose who gets it
Admins decide which groups at the company get the ClickUp connector, and which of them may create tasks. Everyone else never sees it.
Every call logged
Who asked, which connector, when. Deployed OS shows reads and writes per connector and per person, the log can be exported, and access is removed centrally the day someone leaves.
Setup

Set up the ClickUp connector in three steps

01
A ClickUp Workspace owner or admin creates an app under Settings → Apps and adds the redirect URL from Deployed OS. Your company owns the app, not us.
02
The admin adds the app’s Client ID and Client Secret to Deployed OS and chooses which groups get ClickUp, and who may create tasks.
03
Each person connects with their own ClickUp login and ticks the Workspaces to share. From then on they just ask.
Compared

ClickUp’s own MCP server or Deployed OS?

ClickUp runs its own hosted MCP server, and each person connects it with their own ClickUp login. It is a good fit for one person, or a developer wiring ClickUp into the tools they use.

Deployed OS is built for the whole company. One company connection for ClickUp and your other tools, each person’s own login, admins choosing which groups get what, and a log of every call. The same connection works in Claude, ChatGPT and Copilot, next to your company’s skills and guardrails.

Their documentation: ClickUp’s MCP server

Questions

ClickUp MCP: common questions

Yes. ClickUp hosts its own MCP server, which a person connects to their own AI tool. Deployed OS gives the whole company one connection, with each person’s own login, access per group and a log of every call.

It can create a task in a List, with a description and due date, once you have confirmed the text, and your company’s guardrails apply. The task gets no assignee and nobody is mentioned. The ClickUp connector cannot edit, close or comment on tasks. If you need it to do more, we can extend it for you.

Yes. Deployed OS is your company’s own MCP, so the same ClickUp connection works in Claude, ChatGPT and Copilot. People keep the assistant they prefer.

Not by words. It narrows tasks down by List or Workspace, status, due or updated dates and whether they are yours, then reads the names. Ask for “my open tasks in the Design List” and you get them in one go.

A Workspace owner or admin creates the app in ClickUp’s settings and adds its two keys to Deployed OS. Then each person connects their own account. We walk you through the steps.

It depends on the size of your team. Get in touch and we will walk you through it.

More connectorsAll connectors
Let’s talk

See it on your own tools.

Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.

Poyan Karimi
You’ll hear from Poyan Karimi
Co-founder · Deployed AI