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.