Public API

SUMMARY The get_task_comments tool in the ClickUp MCP server fails entirely on any task containing comments authored by an integration bot or a deleted user. A single such comment causes the tool's output validation to reject the whole response, so MCP clients receive zero comments — including all the valid human ones. ROOT CAUSE The tool's output schema requires comments[]. user.id to be a number. Comments authored by bot/app identities or deleted users serialize with a user object that has no id, so validation fails and the entire response is discarded. EXAMPLE ERROR (task with 3 bot comments out of ~25): MCP error -32602: Output validation error: Invalid structured content for tool clickup_get_task_comments: [ { "expected": "number", "code": "invalid_type", "path": ["comments", 10, "user", "id"], "message": "Invalid input: expected number, received undefined" }, { "expected": "number", "code": "invalid_type", "path": ["comments", 15, "user", "id"], "message": "Invalid input: expected number, received undefined" }, { "expected": "number", "code": "invalid_type", "path": ["comments", 23, "user", "id"], "message": "Invalid input: expected number, received undefined" } ] WHY THIS IS SYSTEMIC, NOT AN EDGE CASE The failing comments in our workspace come from "ClickBot (from Front)" — Front's official ClickUp integration, which posts a "Front Conversation: <link>" comment on tasks. Bot/app identities like ClickBot have no ClickUp user account behind them, so their comments always lack user.id . Every workspace using the Front integration (and presumably any integration posting as an app bot) is affected, and new comments keep arriving in this state — no workspace hygiene avoids it. NO WORKAROUND EXISTS Bot comments are interleaved chronologically, so pagination cannot skip them. Any affected task's comment history is completely unreadable through MCP. THE BUG IS CONTAINED TO THE MCP LAYER The public REST endpoint GET /api/v2/task/{task_id}/comment returns these same comments without error. The ClickUp web UI renders them correctly, labeled "ClickBot (from Front)". Only the MCP tool's output schema rejects them, so the fix should be fully contained to the MCP server. STEPS TO REPRODUCE Connect Front's ClickUp integration and link a Front conversation to a task (this posts a comment as ClickBot) — or use any task that has a comment from a deleted user. Call the get_task_comments MCP tool for that task. Result: MCP error -32602, no comments returned. IMPACT AI/MCP clients (Claude, Claude Code, custom agents, etc.) cannot read comments on affected tasks. For teams using Front for support email, that is the majority of active tasks — comment history is effectively invisible to AI tooling. SUGGESTED FIX Make comments[].user nullable (or its id/username optional) in the tool's output schema, and ideally represent bot authors explicitly (e.g. a name with no id, or a bot: true flag). Gracefully degrading a single comment's author info is fine — failing the entire call is the real problem.

The ability to include mentions in comment text or task descriptions

Summary: We are requesting an API endpoint that allows us to retrieve all comments assigned to a specific user across tasks and lists, without the need to make thousands of requests manually. This feature is essential for businesses managing a large number of tasks and team members within ClickUp, where tracking assigned comments is a critical part of performance and task management. Current Challenge: Currently, there is no direct way to retrieve comments assigned to a user. The existing workaround—making thousands of API requests to retrieve all tasks and filter comments—creates performance bottlenecks, is highly inefficient, and is not scalable for businesses managing large numbers of tasks. This approach not only consumes an excessive amount of resources but also introduces significant delays in retrieving the data. We need a solution that allows us to: Efficiently retrieve all comments assigned to a specific user without looping through thousands of tasks. Have immediate access to this data for business-critical operations. Proposed Solution: A new API endpoint that can: Retrieve all comments assigned to a specific user across all tasks and lists within a space or workspace. Allow for filtering by user ID or email to gather the assigned comments. Ensure efficient data retrieval to avoid the need for making excessive requests or running into performance issues. Why This Matters: This feature would eliminate the need for inefficient workarounds and provide a streamlined solution to track user-specific comments. It would save significant time and resources, allowing businesses to focus on performance management and improve task handling. Given that member resources are already available in ClickUp, the lack of an endpoint for assigned comments seems like an oversight, especially for larger teams managing numerous tasks. Impact: This feature would benefit any organization using ClickUp at scale, enabling more efficient tracking of team performance and task management. By adding this endpoint, ClickUp could offer a much more robust and business-friendly API that better supports its users' needs without forcing reliance on third-party tools.

Add the ability to update threaded comments via the API.

Currently the data returned by the ClickUp API for a task's comment is plain text. All HTML markup has been removed, inserted images are lost, etc. Is there any chance in near future the original comment is returned? Thanks!

Hi! When writing text in a task description, each section is formatted as a movable block. After clicking the block icon on the left side, a small context menu appears with options like Turn into, Block color, Duplicate, Copy block link, and Delete. I’d like to suggest adding a new option: Copy block text. Right now, if I want to copy the text from a block, I have to manually select all the content and copy it. A dedicated “Copy block text” option would make this much quicker and more convenient, especially for longer blocks. Thanks for considering this improvement!

It is currently not possible to create or update a comment and provide a historical datetime, as would be the case for a custom importer, for example. Please add support for allowing the comment datetime to be provided.

Currenty Threaded Comments API returns the latest 25 comments. If there are more than 25 it seems there is no way to fetch older ones. Tried with start, startId, date parameters but no luck.

Please update comment API to send email The API of the WEB application https://frontdoor-prod-us-west-2-3.clickup.com/comments/v1/{task_id}/comment already has this function