About clickup-mcp
clickup-mcp is an MCP server for managing ClickUp workspace tasks. It is intended for users who want to operate ClickUp through MCP, and reduces the size of API responses; the project is unmaintained.
Key features
- 01Create, read, update, and delete tasks
- 02Search tasks and manage custom fields
- 03Manage tags, checklists, and dependencies
- 04Add comments, replies, and attachments
- 05Slim down API responses
Use cases
- 01Manage ClickUp tasks through MCP
- 02Find workspace tasks and update their fields
- 03Add tags, checklists, or comments to tasks
MCP support
It connects to the ClickUp API using MCP's stdio transport and exposes tools for workspace, list, task, and related management. A ClickUp API token is required.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @cavort-it-systems/clickup-mcpCLICKUP_API_TOKENSecretClickUp Personal API Token (Settings > Apps)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
40Saved tool list · updated 2w ago
This tool takes no parameters.
Details
From the project READMEclickup-mcp
Unmaintained. ClickUp is retired at CAVORT (2026-10-18, cutover to Console complete). This server is kept as is and no longer developed.
Lightweight ClickUp MCP server focused on task management. 40 tools with token-optimized responses - API responses automatically slimmed from thousands of characters to essentials.
Why This Server?
ClickUp's API returns extremely verbose JSON. This server strips it down:
| Response | Before | After | Reduction |
|---|---|---|---|
clickup_whoami | ~3,500 chars | ~160 chars | 95% |
clickup_create_comment | ~1,500 chars | ~38 chars | 97% |
Less tokens = faster responses, lower costs, more context for your AI.
Installation
npm install -g @cavort-it-systems/clickup-mcp
Or run directly:
npx @cavort-it-systems/clickup-mcp
Configuration
Claude Code CLI
claude mcp add clickup -e CLICKUP_API_TOKEN=your-token -- npx @cavort-it-systems/clickup-mcp
Claude Desktop / Manual
Add to your MCP config (~/.claude.json or Claude Desktop settings):
{
"mcpServers": {
"clickup": {
"command": "npx",
"args": ["@cavort-it-systems/clickup-mcp"],
"env": {
"CLICKUP_API_TOKEN": "your-token"
}
}
}
}
From Source
git clone https://github.com/cvrt-jh/clickup-mcp.git
cd clickup-mcp
pnpm install && pnpm build
Then configure with the built path:
claude mcp add clickup -e CLICKUP_API_TOKEN=your-token -- node /path/to/clickup-mcp/build/index.js
Custom task IDs
Every tool that takes a task_id accepts the custom ID as well (DEV-1217), not only
the internal one (86caqr85m). The server adds custom_task_ids=true&team_id=... itself.
The workspace id comes from CLICKUP_TEAM_ID, or, if unset, from the token's only
workspace (looked up once). A token with access to several workspaces must set
CLICKUP_TEAM_ID.
Get Your API Token
- Go to ClickUp Settings > Apps
- Generate a Personal API Token
- Set as
CLICKUP_API_TOKEN
Response Slimming
All responses are automatically trimmed to save tokens. The ClickUp API returns extremely verbose JSON - this server strips it down to what matters.
clickup_whoami - from ~3,500 chars to ~160:
// Before (ClickUp API raw)
{"user":{"id":12345678,"username":"Jane Doe","email":"[email protected]","color":"#0388d1",
"profilePicture":"https://attachments.clickup.com/...","initials":"JD",
"week_start_day":1,"global_font_support":true,"timezone":"Europe/Berlin"},
"teams":{"teams":[{"id":"99999999","name":"My Workspace","color":"#40BC86",
"avatar":"https://attachments2.clickup.com/...?Expires=...&Key-Pair-Id=...&Signature=...",
"members":[{"user":{"id":11111111,"username":"Bob Smith","email":"[email protected]",
"color":"#aa2fff","profilePicture":null,"initials":"BS","role":4,"role_subtype":2,
"role_key":"guest","custom_role":null,"last_active":"...","date_joined":"...",
"date_invited":"..."},"invited_by":{"id":22222222,...},
"can_see_time_spent":true,...}, ...]}]}}
// After (slimmed)
{"id":12345678,"username":"Jane Doe","email":"[email protected]",
"timezone":"Europe/Berlin","workspaces":[{"id":"99999999",
"name":"My Workspace","member_count":4}]}
clickup_create_comment - from ~1,500 chars to 38:
// Before
{"id":90150191300876,"hist_id":"...","date":1770053982842,
"version":{"object_type":"comment","object_id":"...","workspace_id":99999999,
"operation":"c","data":{"context":{"root_parent_type":1,"is_chat":false,
"audit_context":{"userid":12345678,"current_time":...,"route":"*"},...},...},...}}
// After
{"id":90150191300876,"date":1770053982842}
What gets stripped:
| Field | Where | Why |
|---|---|---|
features{} | spaces | ~50 lines of boolean flags per space |
sharing{}, permission_level | tasks | Internal access config, not useful |
watchers[] | tasks | Usually same as assignees |
| Full user objects | everywhere | Reduced to {id, username, email} |
profilePicture, initials, color | users | Visual metadata, not useful for LLMs |
version{} blobs | comment/reply creates | Internal versioning data |
invited_by, profileInfo | members | Invitation metadata |
| Pretty-print JSON | all responses | Compact single-line output |
| Empty arrays | tasks | checklists, dependencies, custom_fields omitted when empty |
Tools (40)
Navigation (7)
clickup_whoami- Current user + workspacesclickup_get_spaces- Spaces in workspaceclickup_get_folders- Folders in spaceclickup_get_lists- Lists in folder or spaceclickup_get_list- Single list detailsclickup_create_list- Create list in folder or spaceclickup_delete_list- Delete a list (permanent)
Task CRUD (5)
clickup_get_task- Get task by IDclickup_create_task- Create task with all fieldsclickup_update_task- Update any task fieldclickup_get_tasks- List tasks in a listclickup_search_tasks- Search tasks across workspace
Custom Fields (1)
clickup_set_custom_field- Set custom field value
Tags (6)
clickup_get_space_tags- List space tagsclickup_create_space_tag- Create tagclickup_edit_space_tag- Edit tagclickup_delete_space_tag- Delete tagclickup_add_tag_to_task- Tag a taskclickup_remove_tag_from_task- Untag a task
Checklists (6)
clickup_create_checklist- Create checklistclickup_edit_checklist- Edit checklistclickup_delete_checklist- Delete checklistclickup_create_checklist_item- Add itemclickup_edit_checklist_item- Edit itemclickup_delete_checklist_item- Delete item
Dependencies (4)
clickup_add_dependency- Add dependencyclickup_delete_dependency- Remove dependencyclickup_add_task_link- Link tasksclickup_delete_task_link- Unlink tasks
Comments (5)
clickup_create_comment- Add commentclickup_get_comments- Get commentsclickup_update_comment- Edit/resolve commentclickup_create_reply- Threaded replyclickup_get_replies- Get replies
Delete Task (1)
clickup_delete_task- Delete a task
Multi-List Membership (2)
clickup_add_task_to_list- Add a task to an additional list (multi-homing)clickup_remove_task_from_list- Remove a task from an additional list
These do not move a task. The ClickUp v2 API has no move-between-lists endpoint. Verified against the live API 2026-08-12:
POST /list/{list}/task/{task}adds a secondary location and leaves the home list unchanged, while alist_idinPUT /task/{id}returns HTTP 200 and is silently ignored. To genuinely move a task and keep its custom ID and history, use the ClickUp web UI (right-click -> Move). Multi-list membership also requires the paid Tasks-in-Multiple-Lists feature.
Attachments (1)
clickup_upload_attachment- Upload a local file (screenshot, PDF) to a task
Workspace Members (2)
clickup_get_workspace_members- All workspace membersclickup_get_list_members- List-specific members
Architecture
src/
index.ts # Entry: McpServer + StdioServerTransport
client.ts # ClickUp API v2 fetch wrapper
types.ts # Shared Zod schemas + jsonResult helper
slim.ts # Response slimming transformers
tools/
navigation.ts # 7 tools
tasks.ts # 9 tools (CRUD + custom fields + delete + multi-list)
tags.ts # 6 tools
checklists.ts # 6 tools
dependencies.ts # 4 tools
comments.ts # 5 tools
members.ts # 2 tools
attachments.ts # 1 tool (multipart upload)
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.