Public API

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.

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.

Use Case I'm developing MKiTFlow, a Figma plugin designed for creative agencies in the DACH region (Germany, Austria, Switzerland). The plugin integrates with ClickUp via n8n middleware to streamline the workflow between design tools and project management. Current Problem Creative agencies need to automatically set cover images for ClickUp tasks when assets are created or updated in Figma. Currently, there is no public API endpoint to programmatically set or update task cover images. The only way to set a cover image is through the ClickUp UI, which breaks automation workflows and requires manual intervention. Technical Requirements We need an API endpoint (similar to the internal frontend endpoint) that allows: Setting a cover image for a task using an attachment ID or filename Updating cover image position (x, y coordinates) Setting cover image color/overlay options Removing a cover image Example payload structure (based on internal frontend API): { "coverimage": "attachment-id-or-filename.png", "cover_image_color": "none", "cover_position_x": 0, "cover_position_y": 0 } Business Impact Automation: Enables fully automated workflows between design tools (Figma) and project management (ClickUp) Efficiency: Saves creative agencies significant time by eliminating manual cover image setup Consistency: Ensures all tasks have proper visual representation in Board View Scalability: Allows agencies to manage hundreds of tasks with proper visual assets Current Workarounds (Insufficient) Manual UI interaction: Users must manually set cover images after attachment upload - breaks automation First attachment rule: Board View shows first image as cover, but this is unreliable and can't be controlled programmatically Internal frontend API: Exists but requires browser session cookies, not suitable for server-side integrations There was already a feature request for this functionality: https://feedback.clickup.com/public-api/p/api-set-cover-image-pin

All APIs are tied to a specific user, but would be more convenient to have a section for ADMINs to create API keys to manage the workspace better.

the ClickUp API's PUT /task/{task_id} already supports a parent field for parenting, but the MCP's clickup_update_task tool doesn't expose it.

The V2 OpenAPI spec at https://developer.clickup.com/openapi/clickup-api-v2-reference.json has incorrect type definitions for several task response fields. This causes JSON deserialization errors in any code generated from the spec. **Issue 1: time_spent and time_estimate declared as string|null , API returns integer ** Affected endpoints: GET /v2/task/{task_id}, PUT /v2/task/{task_id}, POST /v2/list/{list_id}/task, and others. Spec declares: {"type": ["string", "null"]} API actually returns: "time_spent": 3600000 (integer, milliseconds) Error when using generated code: json: cannot unmarshal number into Go struct field UpdateTaskJSONResponse.time_spent of type string Fix: Change to {"type": ["integer", "null"], "description": "Time in milliseconds"} **Issue 2: assignees and tags declared as string[] , API returns object[] ** Spec declares: {"type": "array", "items": {"type": "string"}} API actually returns: assignees: [{"id": 123, "username": "isaac", "email": " isaac@example.com ", ...}] tags: [{"name": "bug", "tag_fg": "#fff", "tag_bg": "#f00"}] Fix: Change items to proper object schemas with the fields the API actually returns. These mismatches affect all task-related endpoints. The V3 spec does not have these issues. Verified against spec version last-modified 2026-04-02.

Add an API endpoint to link a Document & Task. This allows the Document to be viewed in the "Doc Links" sidebar in the right-hand sidebar of tasks, and "Relationships" sidebar in the right-hand sidebar of documents.

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.

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

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,