Every ClickUp API call wants an id, and getting one normally means three lookups first. Being able to say team/space/folder/list is what lets an agent act on the place you named instead of spending its turns resolving what you meant.
A server over the ClickUp API. It reads the workspace hierarchy and creates, updates and deletes the structure inside it, and it can walk that hierarchy by path notation (team/space/folder/list) rather than by chained ids. Task, comment and attachment operations sit alongside the structural ones.
- Every workspace the account can reach, and the spaces inside one
- The full hierarchy of a space, folders included, in a single call
- Spaces and folders created, and folders updated or deleted
- Lists created inside a space or inside a folder, and the lists in either listed
- Lists reorganised between spaces and folders
- Navigation by path notation — team_id/space_name/folder_name/list_name — so you do not have to resolve ids by hand
- Markdown in descriptions and comments, converted to HTML so it renders properly in ClickUp
Access to a ClickUp workspace: the server calls the ClickUp API on your behalf, so what it can see and change follows the account you connect. Nothing is scoped more narrowly than that account is.
One command plus a key — pip install clickup-mcp-server, then supply credentials