ClickUp Chat Feedback

Right now, we can manually create channels outside of a list and delete them with no problem. But when we create a channel inside a list using Channel View, there is no way to delete it. This causes a buildup of extra channels on the backend. We can only hide them, which clutters everything, especially if a channel is created by mistake. Please make it possible to delete channels that are created through a List → Channel View.

I’d like to quickly open a chat within ClickUp, without having to leave a list or navigate away from the current page. It should be easy to check for new messages and respond to them seamlessly. Previously, I could jump between Slack and ClickUp without leaving the ClickUp window, which was very convenient. Now, it’s more difficult because I have to switch between entire pages. Like for example in the same floating window when you open Clickup AI. Also (sound) notifications are extremely important.

Seems only the creator of a channel is able to add members and change settings, like rename it. We also can't see who created the channel to ask them - and they may have left the business. Need to be able to have admins change/take ownership so we don't keep needing to replace channels with new ones.

As far as I can see, there is no way to actually jump to a message in the original thread you find in search. All you can do is reply to it. It's often that you need to go back to the original conversation from a message you remember and in click you literally have to manually scroll back all the way to that conversation, which sometimes can be months. (And the "jump to last month" button doesn't ever work to make this quicker")

It would be great to merge chat channels, with merged messages being ordered within the target channel according to their timestamp as if there were never 2 channels.

At the moment, I always open Clickup in two windows so that one window is always open for chats. Otherwise, you have to jump back and forth between the task you're currently working on and the chat window. A pop-up window, such as the AI help chat window or, for example, the chat window on Facebook or LinkedIn, would be more practical, that the corresponding chat pops up at the bottom with a “1" for an unread message without the entire window being filled out by the chat.

We really want to differentiate the sounds of a task and chat since our "tasks" sound is related negative since it's reminders for dues or that something needs to be fixed. We need this before we change over to chat so the notifications for chat is something that's new, positive and does not physiologically makes them stressed. And also makes them understand what is a message and what is a task.

Adding nuance to this feature is important so that we aren't limited to just threads for our ability to reply to message: https://feedback.clickup.com/chat-feedback/p/send-threaded-message-to-chat-and-thread 90% of the time all I want to do is quickly reply to a message for the sake of context. There is no need 90% of the time to create an entire thread around a reply, just a simple yes/no answer to a question and showing the connection of that yes/no to the original ask is all that is needed. Look at Discord, NOT slack as a point of reference for Replies and Threads. Please please please do not emulate Slacks' terrible implementation as if it was some sort of standard to follow, Discord is infinitely more useable and better of an experience

The ClickUp MCP currently has no way to retrieve inbox notifications. The inbox is a core part of how users manage what needs their attention in ClickUp, but it is entirely inaccessible to AI agents and automations built on the MCP. Current behaviour: There is no MCP tool that returns inbox notifications. The only workaround is search_reminders, which returns a different and much narrower set of items. Desired behaviour: A get_inbox_notifications tool that returns the authenticated user's inbox, with at minimum: Notification content and type Source (task, chat message, mention, assignment, etc.) Link to the source item Timestamp Read/unread state Why this matters: The inbox is where ClickUp surfaces everything that needs a user's attention. Without MCP access to it, any AI agent trying to act as a personal assistant or comms triage layer has a critical blind spot. Exposing the inbox via MCP would make ClickUp a first-class data source for AI-powered productivity workflows. Related: https://feedback.clickup.com/feature-requests/p/expose-read-unread-state-for-chat-messages-via-mcp

The ClickUp MCP currently has no way to surface whether a chat message or inbox notification has been read. When building AI agents or automations on top of ClickUp chat, this is a significant gap — without read/unread state, there's no reliable way to filter "what the user hasn't seen yet." Current behaviour: The MCP exposes chat messages and inbox notifications but returns no read/unread flag on any of them. Desired behaviour: Each chat message and inbox notification returned by the MCP includes a boolean is_read field (or equivalent), reflecting whether the authenticated user has read it. Why this matters: Without this, any agent or automation that tries to surface "what needs your attention" has to use heuristics — timestamp cutoffs, action-based filtering, one-time triage rules — as proxies for unread state. These are workarounds, not solutions. A simple is_read flag would unlock accurate, reliable filtering and make ClickUp a much stronger foundation for AI-powered inbox management. Proposed addition: is_read: boolean on chat message objects is_read: boolean on inbox notification objects a filter parameter on get_chat_channel_messages to return only unread messages Related: https://feedback.clickup.com/feature-requests/p/add-get-inbox-notifications-tool-to-mcp