Is there an official ClickUp MCP server?

We could not confirm one when we last checked. The workable routes are community servers built on the ClickUp API and the connector platforms that expose ClickUp as a tool.

Why is ClickUp MCP so slow to do anything?

Because the assistant is walking workspace, space, folder and list before it reaches your task. Name the exact list in your request, or keep list IDs handy, and it becomes a single lookup.

Can an assistant write to ClickUp custom fields?

Sometimes. Many community servers implement reads and not writes for custom fields. Test the specific write you need before relying on it.

Will bulk edits hit ClickUp's rate limits?

Yes, easily. Rate limits are per token and each task is usually its own call, so large rewrites stall partway. Work in small batches and check the result.

ClickUp MCP — Setup, Hierarchy Traps, Custom Field Limits

ClickUp's depth is its selling point in the app and its main problem over MCP. Workspace, space, folder, list, task, subtask: to act on one task an assistant may need several calls just to find it. Every setup that feels slow is a scoping problem, not a performance problem.

Scope first, then ask

Give the assistant the list you mean. "In the Marketing space, Q4 folder, Launch list" turns a tree walk into a single lookup. If you work mostly in two or three lists, keep their IDs somewhere you can paste; it changes the experience completely.

Custom fields are the honest weak spot

Teams that use ClickUp seriously live in custom fields, and community MCP servers implement them unevenly. Plenty can read a custom field and cannot write one. Before building any routine on top of this, test the exact write you care about — do not infer support from the README.

What it is good at

Intake and triage. A paragraph becomes a correctly placed task with an assignee and a due date. Cleanup, too: finding tasks with no assignee or no due date across one list is a question ClickUp's own filters answer, but it is faster to ask, and the assistant can fix them in the same breath.

Where LemTask stands today

LemTask does not ship an MCP server yet, and we are not going to pretend otherwise on a page developers will read. What LemTask has working right now is outbound and inbound webhooks, Zapier, Make and Apple Shortcuts, which covers "when a task is created, do X" and "create a task from anything that can send an HTTP request". An MCP connection is on the roadmap; when it ships and we have tested it end to end with Claude, this page will say so with the config block, and not a day earlier.

Setup, step by step

Generate a personal API token

Create a token in your ClickUp settings under Apps. It carries your own permissions, so it only sees the spaces you can see.

Add a maintained server to your config

Pick a community server with recent activity, add it to your MCP client config with the token as an environment variable, and restart the client.

Note the IDs of your working lists

Ask the assistant to list your spaces and lists once, then keep the two or three list IDs you use daily. Naming them removes the hierarchy walk.

Test the exact custom field write you need

If your workflow depends on custom fields, confirm a write succeeds before building anything on it. Read support does not imply write support.

ClickUp MCP: hierarchy, custom fields, and setup

What it can do

What it can't do