get_workspacesLABSCO SUMMARY
Path notation is the part that makes this usable in conversation.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
Run a container — build the image from the repository, then point your client at it
USE CASES
01
Getting the lay of an unfamiliar workspace
List the workspaces, then the spaces in the one you want, then read a space's full hierarchy in one call.
02
Jumping to the list you actually meant
Use the path — team, space, folder, list — and get the target and its full path back, without resolving ids yourself.
03
Setting up a new project's structure
Create the space, then the folders, then the lists inside them, in one pass.
04
Tidying a space that grew organically
Read the folders and lists as they stand, then move lists where they belong and rename the folders around them.
05
Retiring part of a workspace
Check what the folder holds, then delete it once you know what goes with it.
32 tools
Listed in project docs. Your client may show a different list.
navigate_workspaceget_spacescreate_spaceget_space_hierarchyget_folderscreate_folderupdate_folderdelete_folderget_listscreate_listorganize_listsget_tasksget_tasks_by_statuscreate_taskget_taskupdate_taskupdate_task_statusassign_taskget_task_subtasksdelete_taskmove_taskduplicate_taskcreate_subtaskadd_commentadd_attachmentbulk_update_tasksbulk_delete_tasksget_custom_fieldsset_custom_field_valueset_custom_field_value_by_nameremove_custom_field_valueBEFORE YOU INSTALL
What to know first
Tools you get
32 tools named in the project's documentation.
Requires
- Docker
- CLICKUP_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/imjoshnewton/clickup-mcp-server.git
cd clickup-mcp-server
docker build -t mcp/clickup .MCP Clients
Claude Desktop — Docker
CLAUDE DESKTOP — DOCKER · JSON
{
"mcpServers": {
"clickup": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"CLICKUP_API_KEY=<YOUR_CLICKUP_API_KEY>",
"mcp/clickup"
]
}
}
}VS Code — Docker
VS CODE — DOCKER · JSON
{
"servers": {
"clickup": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"CLICKUP_API_KEY=<YOUR_CLICKUP_API_KEY>",
"mcp/clickup"
]
}
}
}
