Support Rich Text Formatting in clickup_create_task_comment
Andrea Colajacomo
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.
Log In
Patrick Paskaris
Another option would be supporting the embed-style Markdown syntax that GitHub and other tools use, where you prefix a Markdown link with an exclamation mark to embed it. That would be a great way to render existing rich-text blocks back out for agents to read, and it gives them a way to write them too. Uploading an attachment through the MCP already returns its URL, and putting that URL in a comment renders as a plain clickable link. It would be super straightforward to put a bang in front of it and have it render in place. Right now
actually produces an attachment card, but it comes out empty and broken, so it feels like most of the plumbing is already there.