Public API

I need to be able to use the internal API to extract the history of a task as it is displayed on the web. After some research, I found that this functionality already exists, but it is not exposed via the public API and can be extracted from the internal web API.

Subject: Bug Report: Official MCP Server Schema Incompatibility with AntiGravity IDE (Gemini) Hi ClickUp Team, I'm writing to report a bug with your official MCP server that prevents it from functioning with AntiGravity IDE, which is listed as a supported MCP client in your documentation. --- Issue Summary When connecting to https://mcp.clickup.com/mcp via AntiGravity IDE, the connection fails immediately with HTTP 400 Bad Request due to an invalid tool schema. Error received: GenerateContentRequest.tools[26].function_declarations[0].parameters.properties[max_depth].enum: only allowed for STRING type GenerateContentRequest.tools[26].function_declarations[0].parameters.properties[max_depth].enum[0]: cannot be empty GenerateContentRequest.tools[26].function_declarations[0].parameters.properties[max_depth].enum[1]: cannot be empty GenerateContentRequest.tools[26].function_declarations[0].parameters.properties[max_depth].enum[2]: cannot be empty Root Cause The max_depth parameter in one of your tool definitions (tools[26]) declares an enum on an INTEGER type field. The Gemini API — which powers AntiGravity IDE — only allows enum on STRING types. This is a schema incompatibility that causes a hard failure before any tool can be invoked. Steps to Reproduce Open AntiGravity IDE Add the following MCP server config: ```json { "mcpServers": { "clickup": { "serverUrl": " https://mcp.clickup.com/mcp " } } } ``` Attempt to initialize the MCP connection Observe HTTP 400 error Expected Behavior The MCP server should load successfully and tools should be available in AntiGravity IDE, as per your documentation which explicitly lists AntiGravity as a supported client. Suggested Fix Convert the max_depth parameter (and any other integer enum fields) to STRING type with a runtime conversion on your server side, or remove the enum constraint and validate the value programmatically instead. Environment MCP Client: AntiGravity IDE MCP Server: https://mcp.clickup.com/mcp (official, first-party) Underlying model: Gemini (Google) Since AntiGravity is listed as a supported client in your documentation ( https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server ), I'd appreciate a prompt resolution. Thank you,

It would be nice to access the inbox and new reminders via the API in the future.

Using the API GET TASKS to search for Tasks with specific words in the Title, and also in the description as a bonus.

Hello, I saw that there's the possibility to update/delete a custom field value from ClickUp API, but there's no chance to edit/update the options of a dropdown. That's my use case: I have another platform with its own list of users, that increase on a daily base I have a ClickUp list, with a custom field that holds the user to whom the task is related I wish that the custom field was a dropdown, restricting the access only to the existing users, but cannot mantain it manually whenerever a new user is added on the other platform

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.

Example scenario: A (non-ClickUp)-form submission automation creates a ClickUp task A confirmation email sent to the submitter A response to the confirmation email should be recorded as a comment (for more details, questions, corrections, etc.)

We need the ability to set and get sharing permissions on individual tasks via the API. Use case: When programmatically duplicating tasks, the new task should inherit the same user-level permissions (view, comment, edit) as the source task. Currently, GET /task/{id}/member returns members, but there is no corresponding endpoint to set permissions. This is a blocker for any automated task duplication workflow involving private tasks with individual access rights.

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.

To better oversee tasks, it would be beneficial to be able to utilize the fields "date created," "date updated," and "date closed" in automation processes and have these fields available through the API for integrations. This would allow for more precise task tracking and management, and offer enhanced visibility into task timelines and progress.