Public API

The endpoint they delivered doesn't do what it promises: POST /api/v3/workspaces/ {ws} /custom_fields/ {field} /attachments returns HTTP 500 “context deadline exceeded” for any file over 15-20 MB, and the documented attachment limit is 1 GB. I tested Workspace Business Plus on 25/08, from two different networks (office and a VPS in a datacenter): 15 MB goes up, 20, 30, 60, 120 and 300 MB all fail, always about 3 seconds after the body finishes climbing. That is, it's not a connection timeout on my end, it's the backend of you giving up processing the file. And there is no outline through the API: the same file goes up normally through the interface and as a task attachment through v2 (I tested up to 600 MB), but the task attachment is rejected as a field value (FIELD_250) and is not uploaded via a signed URL to the field. In practice, for any real media file, especially video, the functionality does not exist via API. Provide visibility of the correction somewhere. Automation that needs to fill in a file field with rendering or video delivery is blocked until that endpoint respects the 1 GB limit.

Firts of all love the official Clickup MCP server. Our SDLC workflow has been trasnformed with it. One issue we seeing is it uses 34K tokens and that's roughly 17% of claude's 200K context window. Any optimisation that can be done ? Screenshot is from Claude code's "/context" command.

As ClickUp continues to grow and more teams develop against the API, it would be a really great feature for Admins in a Workspace to be able to see API request rate numbers. This way it's easily understood whether or not an integration is in danger of reaching the plan's limit (thus necessitating a plan upgrade)

API keys are still apparently tied to the user that created it. This generates a problem to custom applications if lists are not shared to that user. For example, trying to get a task with /api/v2/team/{self.workspace_id}/task will give you a [{'err': 'You do not have access to this list', 'ECODE': 'ACCESS_078'}] error message. Reminding users to always add the "Admin" account to their private lists doesn't sound like a sustainable solution as users can make mistakes and this may lead to inconsistent output in the custom apps that get data from the APIs

When creating or updating tasks via the API using markdown_description, extra vertical spacing (empty line) is added between different block types: heading to text, text to heading, text to bullet list, and bullet list to text. Consecutive bullet points and consecutive text lines render correctly without extra spacing. The same content typed manually in the editor does not produce this extra spacing. Confirmed with both direct REST API calls and the MCP connector, same behavior. It would be useful to either fix this so the API renders the same as the editor, or provide an option/parameter to control paragraph spacing in markdown_description (e.g. a compact_markdown flag or similar).

While making an API document, all the request and response are in JSON format, I have to Select language as JSON each and every time. So there should be an option to set language as default.

ClickUp's Personal List exists to keep personal tasks separate from team work, and it does that well. But today that separation has a cost: the Personal List is invisible to AI assistants connected through the MCP Server. When I ask Claude to open my Personal List, it can't see it at all — I can't list or search those tasks, and I can't create or update them from the assistant. Request: expose the Personal List through the MCP Server with full read and write support, like any other list: Read — list and search Personal List tasks so they surface alongside the rest of my work. Write — create and update tasks in the Personal List from the assistant.

The ClickUp API has no mechanism to suppress notifications when updating tasks. Every API call to PUT /task/{task_id} or POST /task/{task_id}/field/{field_id} generates a notification to all task watchers. There is no query parameter, header, or flag to prevent this. Why this is critical: Any organization automating workflows via the ClickUp API at scale hits this wall. Our example: we manage 200+ projects in Professional Services. A daily n8n automation propagates metadata (Customer Name, Project Code, Region, etc.) from a master task to hundreds of sibling tasks. Every field write notifies every watcher, creating a flood of irrelevant notifications that bury relevant updates.

Allow a team API token to be generated for integrations. This is to prevent loss of work if ever a user integrates anything and has to leave.

I am using Claude to add time entries for tasks via the MCP, it says it cant add tags to the time entries becuae the MCP doesnt have the option available. It requires manual tagging, which makes using the MCP pointless for time entries.