Feature Requests

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.

Currently, the ClickUp API allows reading and assigning values to existing custom fields, but does not support creating or modifying custom fields themselves. For example, I'm building a script to automate workspace migrations, and this gap in the API creates significant manual overhead.

In the ClickUp API, we need to be able to pull incremental data for replication to our data warehouse. Currently for endpoints such as get task comments, it only supports date filters that work backwards (e.g. retrieve the latest 25 comments before X date), but we need the opposite functionality (retrieve the latest comments after X date). Additionally, it is preferred that we can filter these based solely on a date, and note a date + comment id combination like the get task comments requires currently. While this example is mentioned specifically for comments, I would like the same functionality for any endpoints that have timestamps for created/modified/etc.

In the ClickUp API, I would like a better way to retrieve all tasks across an entire workspace in ClickUp. Currently, I need to pull those from either get tasks in view or get tasks in list. For replication to our data warehouse, it would be much simpler if we can pull all tasks across all lists, along with their corresponding List ID. The issue with get tasks in list is that if a task is in multiple lists, it is only returned in the API response for the primary list, which is very difficult to code around when we have multiple lists that share tasks, and we want to make sure we get all tasks for a single list. We found a workaround for this by creating a view, then using the get tasks in view endpoint, but that has it's own challenges, such as no task description, plus someone needs to maintain that list and ensure it doesn't get deleted or altered to prevent the API response from being altered as well. Also worth noting that with an endpoint such as this, we also need the ability to do incremental filtering based on the last modified timestamps, that way we don't need to pull all tasks each time we refresh the data, we can focus on only retrieving tasks that have been modified since our last incremental extraction.

When using the API endpoint for get tasks in view, I noticed that the task description is not included in the response, however it is included on other endpoints, such as get tasks in list. Please add that column for get tasks in view as well.

When migrating data between ClickUp workspaces or spinning up new environments programmatically, there's currently no way to recreate custom fields via the API. While task data can be moved easily, critical components of workflow structure — like dropdowns and custom fields — must still be built manually in the UI. That breaks automation workflows and creates friction for teams managing complex workspace interactions through the API.

Right now, the ClickUp API doesn’t let developers create custom statuses, a frustrating gap in the API when trying to automate workspace setups. For example, I’m building a tool that transfers all data between workspaces. It works well, except users still have to manually recreate each status. That slows everything down and introduces unnecessary tedium. Exposing status creation via the API would be a game-changer for automation, migration tools, and anyone managing complex workflows from the ClickUp API.

We have integrations that run outside of ClickUp that need to do things that are not possible through the API (i.e. move or duplicate a task). We would like to be able to call an API to trigger an automation on a particular task (trigger=webhook). Currently, we set custom fields or add tags to indirectly trigger the automation, but this introduces a risk of someone manually setting this custom field or adding the tag at the wrong time or multiple times on the same task. We have validation steps in our integration platform that ensure the action should be taken and that it hasn't already been taken on that particular task, but triggering the automation through these strategies allows users to bypass those validations steps.

I just tried to create a new sprint folder and set the first sprint on the same index as our other sprints (Sprint 15 for 31/07/23 to 12/08/23) but ClickUp won't let me choose to start on Sprint 15, I'm forced to start on Sprint 1. I had to duplicate another sprint folder without the tasks to get what I want. I don't understand why it was possible before and not anymore. It is useful, we need this feature.

Description: Currently, while task descriptions support Markdown formatting through the API, long text Custom Fields do not. Implementing Markdown support for these fields would allow for consistent rich text formatting across tasks and Custom Fields, enhancing data presentation and user experience. ​I am working on replicating Azure DevOps' commit history view within ClickUp tasks for my team. To achieve this, I'm using a combination of Webhooks and the ClickUp REST API. Implementing Markdown support for long text Custom Fields via the API would greatly assist in this endeavor. Thanks!