Public 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,

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.

Ship an official ClickUp CLI as a deterministic alternative to MCP for agent workflows Problem We are building AI-driven workflows where agents run locally or in CI and need a tool surface that is: deterministic and cheap at runtime self-describing (so agents do not guess capabilities) stable across time (versioned contracts) MCP introduces overhead and token cost due to tool discovery and repeated schema/context exchange. We want a CLI-first interface that is always up to date and can be invoked by agents and automation systems. Request Please ship an official ClickUp CLI that wraps core ClickUp APIs and Automation Webhooks, with the following requirements: Help-first, machine-readable contracts clickup --help and clickup <cmd> --help must be complete and structured include input flags, examples, output schemas, and exit codes JSON by default All commands output strict JSON by default (--human optional) Stable schemas with versioning Stable exit codes 0 success 2 needs_input/validation error 3 blocked/permission/auth/rate limit 4 failed/unexpected Authentication OAuth device flow (ideal), plus optional support for personal tokens for power users Clear scoping to a workspace Core commands (v1) tasks get|search|create|update comments create|list lists get|search webhooks create|test (or automation webhook helpers) docs get|search (if feasible) Safety controls --dry-run to show mutations without applying explicit confirmation flag for destructive operations Auto-update / version pinning ability to force update before run (agent-friendly) ability to pin versions for CI reproducibility Why this matters This enables a “ClickUp as coordination layer” architecture where: ClickUp is the UI + state machine external agents/CLIs do deterministic work in codebases updates are written back to ClickUp reliably This is lower cost and higher control than MCP-style tool calling for many teams. Related Automation webhooks already exist and work well; a CLI would complement them as the execution surface.

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).

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

We can update the details of a list (name, dates, etc.) but can't move the List to another folder using the API. { "name": "Updated List Name", "content": "Updated List Content", "due_date": 1567780450202, "due_date_time": true, "priority": 2, "assignee": "none", "unset_status": true } It would be great to add a folder_id that would move the list and it's tasks to another parent folder.

Get the Time Estimates per assignee in the API. When you enable the ability to set the estimate per assignee, the task endpoint is delivering the total estimate only. To be consistent, It should show the estimate per assignee.

I want to add fields that I can update with the API, like Email, ratings, etc.

Right now you cannot export the time logged into a format which you can send to a client. We built a Laravel App that uses ClickUp API to export a timesheet based on a selected period. The App goes trough all open and archived lists and fetches the data, then orders it into a timesheet like the one attached, which we can send to our clients. This is not ideal, also ClickUp API limits API calls and if you have a lot of tasks, it takes a while to generate it. It would be also cool to export timesheets per tags or per person as it happens that design is charged differently for us. All time tracking services are really expensive and do not integrate properly with clickup. The native clickup functionality works fine. If a timer would be available without an extension, but right now it works. We just need our data in a digestible format like the one below.

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