Feature Requests

This request refers to the ClickUp MCP server (Model Context Protocol), used to connect AI agents and assistants to ClickUp programmatically. The scenario is an AI agent tasked with posting structured updates — such as email summaries, meeting notes, or status digests — directly to ClickUp tasks as comments, without manual intervention. Current behavior The clickup_create_task_comment tool exposed by the ClickUp MCP server currently only accepts a comment_text parameter, which sends the comment content as a plain string to the ClickUp API. As a result, any Markdown-like syntax (e.g. bold , italic , @mentions) is treated as literal text and rendered without formatting in the ClickUp UI. Expected behavior Comments created via the MCP tool should support rich text formatting — at minimum bold, italic, headings, and @mention resolution — in the same way that comments typed directly in the ClickUp web editor are rendered. Root cause The ClickUp API supports two distinct modes for comment content: comment_text — plain string, no formatting comment — an array of rich text blocks in ClickUp's proprietary format, which the web editor uses internally The ClickUp MCP server currently only wraps comment_text. Exposing the comment parameter (or an intermediate Markdown-to-ClickUp-rich-text conversion layer) would allow formatted output through the MCP tool as well. Proposed solution Add support for rich text input in the clickup_create_task_comment MCP tool, either by: Accepting a markdown_comment parameter and converting it server-side to ClickUp's rich text block format before calling the API, or Exposing the raw comment array parameter for advanced use cases where the caller constructs the block structure directly. Option 1 is preferred for ease of use, as it would be consistent with the markdown_description parameter already available in the clickup_update_task MCP tool — meaning the pattern is already partially established within the MCP server itself. Impact This limitation affects any AI agent workflow using the ClickUp MCP server where comments are generated programmatically. Without rich text support, the output is harder to read and loses the structure that makes it actionable in context — undermining one of the core use cases for integrating an AI agent with ClickUp via MCP.

Make comment private and share only with selected people.

Would like to know who has seen and presumably read comments

A function to pin comments to the activity, to be displayed at the top of the comment area, would be of great help, since we have important information that needs to be read by everyone and ends up being lost and difficult to find in activities with a large number of comments

We use Email in ClickUp to respond to customer emails directly from tasks. When replying using the threaded Reply option (replying to an existing email in the task activity), ClickUp includes the full previous email content in the reply body, and there is no option to remove or collapse the quoted history before sending. This creates a poor experience for recipients in Gmail because the outgoing email becomes very cluttered with repeated prior messages, and Gmail does not consistently minimize/collapse the old content the way it typically does with native Gmail replies. Current behavior: Replying from a task via the threaded “Reply” action automatically includes the full prior email chain in the email body. The composer does not provide a way to trim/remove the quoted text, or to send only the new reply content. Expected behavior / requested enhancement: Please add one or more of the following options for threaded email replies: A toggle to hide/collapse quoted text in the reply composer (and send only the new content). An option to remove quoted history from the reply body (similar to standard email clients). A setting at the Workspace or user level such as “Include quoted text in replies: On/Off.” (Optional) A “Show quoted history” expandable section in the composer UI so it’s available for reference but not sent as clutter by default. Impact: Makes external communication harder to read (especially for Gmail users). Adds noise and can look unprofessional, particularly over long threads. 3 . Forces us to avoid threaded replies, which reduces the value of keeping email conversations neatly threaded in ClickUp.

Often I will have a change in a project that will affect multiple tasks assigned to different people. It would save a lot of time if I could select all these affected tasks and then add the same comment to all the tasks at once rather than having to add the same comment to each task individually.

It's so easy to miss the threaded reply as it's currently collapsed by default... could there be an option to keep them expanded? Thanks!

Print comments or activity history. Need to be able to print comment and activity history for our records. Can only print ClickUp dashboard with items in frame included in print.

When disabling the clickApp for threaded comments all the current comments are removed! This means there is no way back anymore and we really want to disable the feature. It should still show the current comments but disable the option to make new!

It would be cool if you had the ability to pin important comments to the top of the comments thread. Asana does it in a nice way.