Support rich text / ClickUp editor formatting in Docs API and MCP
Thibaut
When reading or writing Doc pages via the API or MCP server, only text/md (Markdown) and text/plain are supported as content formats. This means that any rich formatting applied in the ClickUp editor — such as colored text, callout blocks, banners, column layouts, and other editor-specific elements — is lost when a page is written back via the API or MCP.
This creates a real problem for AI assistant workflows (e.g. using the official MCP server with Claude or other LLMs): if a Doc page has been carefully formatted in the ClickUp editor, any AI-assisted update to that page will strip all of that formatting, since the only write path available is Markdown.
What I'd like:
Either (or all) of the following:
* idea 1: A richer content format option (e.g. text/html or a ClickUp-native rich text AST) for both reading and writing Doc pages, so that formatting round-trips cleanly.
* idea 2: A read-only rich format so that the original formatting can be fetched and preserved when writing back — even if writes remain Markdown-only.
* idea 3: An API / MCP tool to insert in a doc at a certain position, so we can just update selected part without rewriting the whole doc (added value: likely to save tokens)
Use case:
Using the ClickUp MCP server with an AI assistant to append or update content in Doc pages that were formatted in the ClickUp editor. Currently, doing so risks destroying the existing visual structure of the document.
Log In
J
Josh Nackenson
Adding a vote, plus a point I haven't seen made here. The strip isn't the worst of it. The write is destructive and silent, and the read is lossy in the exact same way the write is, so a tool can't even see the rich blocks before it overwrites them. It reads a page, gets back flat markdown with the banners and toggles already gone, concludes the page is plain, and wipes them. No warning, no error. The only recovery is a manual page-history restore, if you catch it in time. (See Hugo's comment above: 50 tasks reverted by hand.)
We build our SOPs and reference docs in Docs and automate revisions through the API. Right now the only safe option is to not use the API for the write at all and paste changes in by hand, which defeats the point of having the API.
Of the three ideas above, idea 3 (partial/positional insert) helps most in the near term. If a one-line change didn't require rewriting the whole page, the destruction wouldn't be possible in the first place. Idea 2 (a read-only rich format so formatting can be preserved on write) would be the next best. Please prioritize this!!!!
Matheus Alexandre
Pleeease! We really need it ASAP!
Paweł Witek
We need this asap!
Hugo
This is needed for tasks too!
Just got 50 tasks to revert manually after MCP erased the rich content. This would be very nice to allow updating!