Clickup Mcp

io.github.cvrt-jh由 GitHub 账号 cvrt-jh 发布v1.1.0更新于 Oct 27, 2026

Lightweight ClickUp MCP server - 37 tools, token-optimized (95% smaller responses)

已验证STDIO仅桌面效率与工作流沟通与协作

概览

AI 生成的概览

本地运行的 ClickUp MCP 服务器,提供约 40 个任务管理工具,并对响应做精简以节省 token。

可以做什么
  • 浏览工作区结构:当前用户与工作区、空间、文件夹、列表,并可创建或删除列表
  • 管理任务:获取、创建、更新、列出、搜索和删除任务,设置自定义字段值,把任务加入或移出附加列表
  • 用标签和检查清单整理:创建、编辑、删除空间标签,给任务加标签或去标签,管理检查清单及其条目
  • 处理依赖与关联:添加或移除任务依赖和任务链接
  • 处理评论:创建、读取、编辑或解决评论,发布或读取线程回复
  • 上传本地文件作为任务附件,并查询工作区或列表成员
适用场景
适合让助手在对话中读取和修改 ClickUp 的任务、列表、标签、检查清单和评论;如果在意 token 成本尤其合适,因为 ClickUp 原始 API 响应非常冗长。
运行要求
通过 npx 或全局 npm 安装以 stdio 在本地运行(需要 Node.js)。需要在 CLICKUP_API_TOKEN 环境变量中提供 ClickUp 个人 API Token。若 Token 可访问多个工作区,还需设置 CLICKUP_TEAM_ID。需要能访问 ClickUp API 的网络。
安装前请注意
README 标明该项目已不再维护、停止开发。API Token 可访问你的 ClickUp 工作区,请勿放入共享配置。许多工具会写入或永久删除数据(任务、列表、标签、检查清单、依赖、评论),上传附件会把本地文件发送到 ClickUp。多列表归属需要 ClickUp 付费功能,且任务无法真正在列表间移动。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Clickup Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

clickup-mcp

Unmaintained. ClickUp is retired at CAVORT (2026-10-18, cutover to Console complete). This server is kept as is and no longer developed.

[npm version] [License: MIT] [MCP SDK]

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:

ResponseBeforeAfterReduction
clickup_whoami~3,500 chars~160 chars95%
clickup_create_comment~1,500 chars~38 chars97%

Less tokens = faster responses, lower costs, more context for your AI.

Installation

bash
npm install -g @cavort-it-systems/clickup-mcp

Or run directly:

bash
npx @cavort-it-systems/clickup-mcp

Configuration

Claude Code CLI

bash
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):

json
{  "mcpServers": {    "clickup": {      "command": "npx",      "args": ["@cavort-it-systems/clickup-mcp"],      "env": {        "CLICKUP_API_TOKEN": "your-token"      }    }  }}

From Source

bash
git clone https://github.com/cvrt-jh/clickup-mcp.gitcd clickup-mcppnpm install && pnpm build

Then configure with the built path:

bash
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

  1. Go to ClickUp Settings > Apps
  2. Generate a Personal API Token
  3. 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:

json
// 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:

json
// 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:

FieldWhereWhy
features{}spaces~50 lines of boolean flags per space
sharing{}, permission_leveltasksInternal access config, not useful
watchers[]tasksUsually same as assignees
Full user objectseverywhereReduced to {id, username, email}
profilePicture, initials, colorusersVisual metadata, not useful for LLMs
version{} blobscomment/reply createsInternal versioning data
invited_by, profileInfomembersInvitation metadata
Pretty-print JSONall responsesCompact single-line output
Empty arraystaskschecklists, dependencies, custom_fields omitted when empty

Tools (40)

Navigation (7)

  • clickup_whoami - Current user + workspaces
  • clickup_get_spaces - Spaces in workspace
  • clickup_get_folders - Folders in space
  • clickup_get_lists - Lists in folder or space
  • clickup_get_list - Single list details
  • clickup_create_list - Create list in folder or space
  • clickup_delete_list - Delete a list (permanent)

Task CRUD (5)

  • clickup_get_task - Get task by ID
  • clickup_create_task - Create task with all fields
  • clickup_update_task - Update any task field
  • clickup_get_tasks - List tasks in a list
  • clickup_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 tags
  • clickup_create_space_tag - Create tag
  • clickup_edit_space_tag - Edit tag
  • clickup_delete_space_tag - Delete tag
  • clickup_add_tag_to_task - Tag a task
  • clickup_remove_tag_from_task - Untag a task

Checklists (6)

  • clickup_create_checklist - Create checklist
  • clickup_edit_checklist - Edit checklist
  • clickup_delete_checklist - Delete checklist
  • clickup_create_checklist_item - Add item
  • clickup_edit_checklist_item - Edit item
  • clickup_delete_checklist_item - Delete item

Dependencies (4)

  • clickup_add_dependency - Add dependency
  • clickup_delete_dependency - Remove dependency
  • clickup_add_task_link - Link tasks
  • clickup_delete_task_link - Unlink tasks

Comments (5)

  • clickup_create_comment - Add comment
  • clickup_get_comments - Get comments
  • clickup_update_comment - Edit/resolve comment
  • clickup_create_reply - Threaded reply
  • clickup_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 a list_id in PUT /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 members
  • clickup_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

来源:README.md,提交 fdb52d1

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

2
  1. v1.1.0最新Oct 8, 2026
  2. v1.0.3Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分