Public API

When adding a custom external MCP server in the App Center (MCP Servers → Add Custom MCP Server), the OAuth authentication method fails to connect to servers that use public OAuth 2.1 with PKCE and no client secret. Steps to reproduce: Go to App Center → MCP Servers → Add Custom MCP Server Set connection type to "For all members" Enter server URL: xxxx Select OAuth as the authentication method In Advanced Configuration, enter Client ID: xxxx, leave Client Secret blank Attempt to connect Result: "Authorization failed: Invalid Request — The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed. Error code: invalid_request" Expected behavior: ClickUp's OAuth flow should support public clients using PKCE (code_challenge / code_challenge_method parameters) without requiring a client secret, per the MCP specification's OAuth 2.1 requirement. Impact: Any MCP server that follows the spec's recommended public OAuth 2.1 + PKCE pattern (Lovable, and likely others as this becomes the standard) cannot be connected to ClickUp as an external MCP server. This is a growing pattern across the MCP ecosystem.

Model Context Protocol (MCP) is basically a must-have feature for all SaaS now. ClickUp providing an official, first-party server would allow users to interact with ClickUp API directly through their agentic AI tool of choice (Claude, GitHub Copilot, Cursor, etc.) https://modelcontextprotocol.io/introduction Most of ClickUp's competitors already offer their own first-party, official MCP server. ClickUp is falling behind in this space, unless it is just not announced yet. Several people have created unofficial ClickUp MCP servers, but they are never going to be as good as what a first-party server could provide. Note: This is not related to MCP support in ClickUp AI ( https://feedback.clickup.com/feature-requests/p/support-mcp-model-context-protocol-in-clickup-ai ), which is requesting support for other provider's servers in ClickUp.

We currently use custom files to organise and title file attachments within a task, especially when viewing tasks in the Table view. It would be ideal for the API to support uploading files to these Custom Fields so I can create a script to automatically download the text documents our writing team creates via Google Docs, run them through our automation tools and upload them to ClickUp automatically for the rest of the team. Hope this is enough information, Oscar Six Senior Technical Officer, Crimson Sky oscar@crimsonsky.games

More endpoints for tasks, users, spaces, etc. Addition of Webhooks

Everything is so slow and takes a long time for even a page to load.

From support ticket: I'd like to have formatting options when it comes to posting a comment through the API. Markdown, HTML, etc.

Context: We needed a custom tool fetching time entries from the API for billing. It lists all times tracked from all users to manage them by tags for creating invoices (for example set them "billed" and other tags). This and other specifics are not possible in ClickUp so far. Problem: For such time entry applications it's currently not possible to retrieve all time entries from all users without iterating over the user list (with additional api calls) before! The behaviour described at https://jsapi.apiary.io/apis/clickup20/reference/0/time-tracking-20/get-time-entries-within-a-date-range.html is problematic as long as there is no way to leave out assignee=XXX to get all users time entries. I guess there are two options: Add antoher GET request without that assignee= restriction returning the results for all users Add a placeholder for assignee= like "ALL" - which would not conflic with the current solution, as it expects an integer. But I'm not sure if that's clean. Anyway the current solution is not good and API consuming because you need a lot more API calls for the simple result. Ohter ClickUp APIs behave differently here!

[from support ticket]

Custom task id takes a long time (according to technical support team - up to 5 mins) to be generated in the back end and to become retrievable via api. This is not acceptable as a work productivity tool - imagine creating a task and having to sit in front of your screen for 5 mins to wait for your custom task id to be generated (and subsequently downstream webhook automations such as folder creation with custom task id prefix to be created). Much like many other posts here, native task IDs are not suitable because they are a jumble of random characters which is not helpful to end-users to organize their tasks chronologically.

Please update API to allow linking via API using relationships