Lightweight ClickUp MCP server - 37 tools, token-optimized (95% smaller responses)
Lightweight ClickUp MCP server focused on task management. 39 tools with token-optimized responses - API responses automatically slimmed from thousands of characters to essentials.
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.
npm install -g @cavort-it-systems/clickup-mcp
Or run directly:
npx @cavort-it-systems/clickup-mcp
claude mcp add clickup -e CLICKUP_API_TOKEN=your-token -- npx @cavort-it-systems/clickup-mcp
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"
}
}
}
}
git clone https://github.com/cvrt-jh/clickup-mcp.git
cd clickup-mcp
npm install && npm run 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
CLICKUP_API_TOKENAll 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":"jane@example.com","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":"bob@example.com",
"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":"jane@example.com",
"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 |
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)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 workspaceclickup_set_custom_field - Set custom field valueclickup_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 taskclickup_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 itemclickup_add_dependency - Add dependencyclickup_delete_dependency - Remove dependencyclickup_add_task_link - Link tasksclickup_delete_task_link - Unlink tasksclickup_create_comment - Add commentclickup_get_comments - Get commentsclickup_update_comment - Edit/resolve commentclickup_create_reply - Threaded replyclickup_get_replies - Get repliesclickup_delete_task - Delete a taskclickup_add_task_to_list - Add a task to an additional list (multi-homing)clickup_remove_task_from_list - Remove a task from an additional listThese 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.
clickup_get_workspace_members - All workspace membersclickup_get_list_members - List-specific memberssrc/
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
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @cavort-it-systems/clickup-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-cvrt-jh-clickup-mcp": {
"command": "npx",
"args": [
"-y",
"@cavort-it-systems/clickup-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@cavort-it-systems/clickup-mcpnpmio.github.cvrt-jh/clickup-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.