Clickup MCP Cdf23b21

MCPAI代理

提供方 hauptsacheNet

AI代理 未标注 OAuth 授权 社区 / 第三方 Claude DesktopClaudeCursorWindsurf

ClickUp MCP协议服务,使AI助手能够与ClickUp工作空间交互,提供完整的任务上下文、搜索、创建和更新任务、协作和时间跟踪功能。

一句话选型结论

按资料字段整理

Clickup MCP Cdf23b21 属于AI代理类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式未标注 鉴权OAuth 授权 部署方式未标注
GitHub 星标 44 仓库热度,无公开仓库时显示未标注
工具数 14 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量14暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

AI助手TypeScript本地部署任务管理协作工具时间跟踪文档管理

安装与配置

未标注 OAuth 授权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 14 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 14 个工具,覆盖面较广,能满足多种调用。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Clickup MCP Cdf23b21当前 14 未标注 未标注 无 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方hauptsacheNet上游标注的维护方 hauptsacheNet
分类AI代理本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

16.6 KB
来自项目仓库与上游目录的原文,未做删改

ClickUp MCP for AI Assistants

Model Context Protocol (MCP) server enabling AI assistants to interact with ClickUp workspaces. Get complete task context with comments and images, search across projects, create and update tasks, collaborate through comments, and track time - all through natural language.

This MCP vs Official ClickUp MCP

> See also: Official ClickUp MCP Documentation

Feature This MCP Official ClickUp MCP
Setup Local npm/npx install Remote MCP (no install)
Authentication API key only OAuth only
Task Context Complete with comments, status history, inline images Requires mutiple tool calls for full contxt
Image Support Read and write: inline images with smart size budgeting, and `` uploads automatically Upload via separate tool calls; base64 capped at ~200KB
Search Fuzzy search on recent tasks (limited scope) Full ClickUp search database
Documents CRUD operations CRUD + document search
Time Tracking View and create entries Timers and entries
Chat Integration Not supported Supported
Connected Apps Not supported Connected Search
Best For Coding tools, automation, context gathering Chat apps, task management
Support Community (open source) Official ClickUp

Choose this MCP when:
- You need rich task context with inline images for AI coding tools
- You want to write screenshots into tickets by local file path (running locally, it reads the file itself instead of taking base64)
- You need API key authentication for automation or CI/CD pipelines
- You want the read-minimal mode optimized for development workflows

Choose Official MCP when:
- You need OAuth authentication for enterprise security compliance
- You need Chat integration or Connected Search features
- You want official support and no local installation

What You Can Do

Turn natural language into powerful ClickUp actions:

Agentic Coding & Development:
- "Look at CU-abc123, can you find the relevant code?"
- "Can you build the dashboard like described in https://app.clickup.com/t/12a23b45c?"
- "Check task CU-xyz789 and fix the bugs mentioned in the comments"
- "Implement the API endpoints described in the integration task"

Time Tracking & Productivity:
- "Book 2 hours for the client meeting on the XYZ project"
- "How much time did I spend on development tasks this week?"
- "Log 30 minutes for code review on the authentication feature"

Smart Search & Discovery:
- "What task did I mention the CSV import in?"
- "Find all tasks related to the payment gateway integration"
- "Show me tasks where users reported login issues"

Daily Workflow Management:
- "What do I need to do today?"
- "Create a task for fixing the dashboard bug in the frontend list"
- "Update the API documentation task to 'in review' status"
- "What tasks are blocking the mobile app release?"

Rich Context & Collaboration:
- "Show me all comments on the user authentication task"
- "What's the latest update on the database migration?"
- "Add a comment to the design task about the new wireframes"

Document Management:
- "Find documents about job posting in hauptsache.net space"
- "Search for API documentation across all spaces"
- "Read the API documentation in the development space"
- "Create a new requirements document for the mobile app project"
- "Update the meeting notes with today's decisions"
- "What documents are in the product strategy space?"

Key Features

🔍 Intelligent Search

  • Fuzzy matching across task names, descriptions, and comments
  • Filter by assignees, projects, status, and metadata

💬 Complete Context

  • Comment histories and team discussions (up to 250 top-level comments), including threaded comment replies
  • Task descriptions with embedded images
  • List descriptions and project guidelines
  • Document content with page navigation
  • Access to complete task history and decisions

⏱️ Time Tracking

  • Log time entries with descriptions
  • View historical time logs and entries
  • Query time entries by task or date range

📋 Task & Document Management

  • Create and update tasks with markdown descriptions
  • Create, read, and update documents and pages
  • Add comments and collaborate with team members
  • Manage priorities, due dates, assignees, and tags
  • Handle time estimates and custom field values

🔒 Safety Features

  • Append-Only Descriptions: Description fields are never overwritten - new content is safely appended with timestamps
  • Normal Field Updates: Status, priority, assignees, tags, and dates can be updated normally (easily revertible through ClickUp's history)

Installation

Prerequisites

For all installation methods, you'll need:
- Your CLICKUP_API_KEY (Profile Icon > Settings > Apps > API Token ~ usually starts with pk_)
- Your CLICKUP_TEAM_ID (The 7–10 digit number in the URL when you are in the settings)

Option 1: MCPB Bundle (Recommended for Claude Desktop)

Download the pre-built bundle from our releases page. This method requires no Node.js installation.

You'll get a configuration screen where you are prompted to enter your API key and team ID.

Option 2: NPX Installation

This method automatically updates to the latest version and is preferred for users who want the newest features.

For Claude Desktop, Windsurf, Cursor and others:

Add the following to your MCP configuration file:```json
{
"mcpServers": {
"clickup": {
"command": "npx",
"args": [
"@hauptsache.net/clickup-mcp@latest"
],
"env": {
"CLICKUP_API_KEY": "your_api_key",
"CLICKUP_TEAM_ID": "your_team_id"
}
}
}
}


Replace `your_api_key` and `your_team_id` with your actual ClickUp credentials.

**Where to add this configuration:**
- **Claude Desktop**: Settings > Developer > Edit Config
- **Windsurf**: Add to your MCP configuration file
- **Cursor**: Configure through the MCP settings panel

### Option 3: Coding Tools Integration

**Claude Code (CLI):**```bash
claude mcp add --scope user clickup \
  --env CLICKUP_API_KEY=YOUR_KEY \
  --env CLICKUP_TEAM_ID=YOUR_ID \
  --env CLICKUP_MCP_MODE=read-minimal \
  --env MAX_IMAGES=16 \
  --env MAX_RESPONSE_SIZE_MB=4 \
  -- npx -y @hauptsache.net/clickup-mcp

> Claude Code can handle a lot of images, thus the recommended increased limits.

> Note the CLICKUP_MCP_MODE=read-minimal. This is my usage recommendation, but feel free to use one of the other modes.

OpenAI Codex:
Add these lines to your ~/.codex/config.toml file:```toml
[mcp_servers.clickup]
command = "npx"
args = ["-y", "@hauptsache.net/clickup-mcp@latest"]
env = { "CLICKUP_API_KEY" = "YOUR_KEY", "CLICKUP_TEAM_ID" = "YOUR_ID", "CLICKUP_MCP_MODE" = "read-minimal" }


> Codex seems to not be able to handle images from MCP's. See this issue for more details.

> Note the `CLICKUP_MCP_MODE=read-minimal`. This is my usage recommendation, but feel free to use one of the other modes.

## MCP Modes & Available Tools

The ClickUp MCP supports three operational modes to balance functionality, security, and performance:

- **🚀 `read-minimal`**: Perfect for AI coding assistants and context gathering
- **📖 `read`**: Full read-only access for project exploration and workflow understanding
- **✏️ `write`** (Default): Complete functionality for task management and productivity workflows

| Tool                   | read-minimal | read | write | Description                                                                             |
|------------------------|:------------:|:----:|:-----:|-----------------------------------------------------------------------------------------|
| `getTaskById`          |      ✅       |  ✅   |   ✅   | Get complete task details including comments (with threaded replies), images, and metadata |
| `addComment`           |      ❌       |  ❌   |   ✅   | Add comments to tasks, or reply inside a comment thread via `parent_comment_id`         |
| `editComment`          |      ❌       |  ❌   |   ✅   | Correct your own comment within 24h instead of posting a follow-up                      |
| `updateTask`           |      ❌       |  ❌   |   ✅   | Update tasks (status, priority, assignees, etc.); descriptions can be appended to or replaced entirely |
| `createTask`           |      ❌       |  ❌   |   ✅   | Create new tasks with full markdown support                                             |
| `searchTasks`          |      ✅       |  ✅   |   ✅   | Find tasks by content, keywords, assignees, or project context                          |
| `searchSpaces`         |      ❌       |  ✅   |   ✅   | Browse workspace structure, project organization, and documents                         |
| `getListInfo`          |      ❌       |  ✅   |   ✅   | Get list details and available statuses for task creation                               |
| `updateListInfo`       |      ❌       |  ❌   |   ✅   | **SAFE APPEND-ONLY** updates to list descriptions (preserves existing content)          |
| `getTimeEntries`       |      ❌       |  ✅   |   ✅   | View time entries and analyze time spent across projects                                |
| `createTimeEntry`      |      ❌       |  ❌   |   ✅   | Log time entries for task tracking                                                      |
| `readDocument`         |      ❌       |  ✅   |   ✅   | Get document details, page structure, and content with navigation                       |
| `searchDocuments`      |      ❌       |  ✅   |   ✅   | Search documents by name and space with fuzzy matching and space filtering              |
| `updateDocumentPage`   |      ❌       |  ❌   |   ✅   | Update existing page content or name with replace/append modes                          |
| `createDocumentOrPage` |      ❌       |  ❌   |   ✅   | Create new documents with first page, or add pages/sub-pages to existing documents      |

### Setting the Mode

Add the mode to your MCP configuration:```json
{
  "mcpServers": {
    "clickup": {
      "command": "npx",
      "args": ["-y", "@hauptsache.net/clickup-mcp@latest"],
      "env": {
        "CLICKUP_API_KEY": "your_api_key",
        "CLICKUP_TEAM_ID": "your_team_id",
        "CLICKUP_MCP_MODE": "read"
      }
    }
  }
}

Configuration

This MCP server can be configured using environment variables. In the desktop extension (.mcpb) installer, the API key, team ID, primary language, upload size limit and comment edit window are offered as form fields; the remaining variables have to be set on the server environment directly.

  • CLICKUP_API_KEY: (Required) Your ClickUp API key.
  • CLICKUP_TEAM_ID: (Required) Your ClickUp Team ID (formerly Workspace ID).
  • CLICKUP_MCP_MODE: (Optional) Controls which tools are available. Options: read-minimal, read, write (default).
  • MAX_IMAGES: (Optional) The maximum number of images to return for a task in getTaskById. Defaults to 4.
  • MAX_RESPONSE_SIZE_MB: (Optional) The maximum response size in megabytes for getTaskById. Uses intelligent size budgeting to fit the most important images within the limit. Defaults to 1.
  • MAX_UPLOAD_SIZE_MB: (Optional) The maximum size of a single image uploaded when writing comments or descriptions. Defaults to 10.
  • CLICKUP_COMMENT_EDIT_WINDOW_HOURS: (Optional) How long after creation editComment may still rewrite a comment. Defaults to 24. Set to 0 to disable comment editing entirely.
  • CLICKUP_PRIMARY_LANGUAGE: (Optional) A hint for the primary language used in your ClickUp tasks (e.g., "de" for German, "en" for English). This helps the searchTask tool provide more tailored guidance in its description for multilingual searches.
  • LANG: (Optional) If CLICKUP_PRIMARY_LANGUAGE is not set, the MCP will check this standard environment variable (e.g., "en_US.UTF-8", "de_DE") as a fallback to infer the primary language.

Language-Aware Search Guidance

The searchTask tool's description will dynamically adjust based on the detected primary language:
- If CLICKUP_PRIMARY_LANGUAGE or LANG suggests a known primary language (e.g., German), the tool's description will specifically recommend providing search terms in both English and that detected language (e.g., German) for optimal results.
- If no primary language is detected, a more general recommendation for multilingual workspaces will be provided.

Markdown Formatting Support

Task descriptions and list documentation support full markdown formatting:

Examples

Task Creation with Markdown:```
Create a task called "API Integration" with description:

API Integration Requirements

Authentication

  • Implement OAuth 2.0 flow
  • Add JWT token validation
  • Priority: High security standards

Endpoints

  1. /api/users - User management
  2. /api/data - Data retrieval
  3. /api/webhook - Event notifications

Testing

  • [ ] Unit tests for auth flow
  • [ ] Integration tests
  • [ ] Load testing with 1000+ concurrent users

> Note: This replaces the legacy REST implementation

See related task: https://app.clickup.com/t/abc123


**Append-Only Updates (Safe):**
When updating task descriptions, content is safely appended:```markdown
[Existing task description content]

---
**Edit (2024-01-15):** Added new acceptance criteria based on client feedback:
- Must support mobile responsive design
- Performance requirement: < 2s load time

This ensures no existing content is ever lost while maintaining a clear audit trail.

Writing Images Into Tickets

addComment, editComment, createTask and updateTask accept images as ordinary markdown. Because
this server runs locally, it reads the file itself - so a local path is enough:```markdown
Ist umgesetzt. So sieht es aus:

1. Login öffnen – der Kunde gibt nur seine E-Mail-Adresse ein.


```

Accepted sources: local file paths, data: URIs, http(s) URLs (downloaded, then
re-uploaded), and existing ClickUp attachment URLs (embedded without re-uploading).

Notes:

  • Prefer paths over base64. A path costs a few tokens; the same screenshot as a
    data: URI costs roughly 4/3 of its file size in the request.
  • The caption becomes the attachment filename, and that filename is what ClickUp
    displays beneath the image - so write a caption that reads well.
  • An image inside a numbered list breaks ClickUp's numbering. Write walkthrough
    steps as bold lines with the image between them, as above.
  • Only real PNG/JPEG/GIF/WebP files are uploaded - the content is checked, not the
    extension. A file that fails aborts the write: addComment, editComment and
    updateTask report every broken reference and change nothing, so the markdown can be
    fixed and the call retried without creating duplicates. createTask validates its
    images before creating the task; only an upload failing afterwards is reported as a
    warning, since the task already exists at that point.
  • Attachments always belong to a task, so document pages cannot embed uploads this way.

Performance & Limitations

Optimized for AI Workflows:
- Smart Image Processing: Intelligent size budgeting prioritizes the most recent images while respecting both count (MAX_IMAGES, default: 4) and total response size limits (MAX_RESPONSE_SIZE_MB, default: 1MB)
- Search Scope: Searches within the most recent 1000-3000 tasks to prevent running into rate limits (exact number varies by endpoint)
- Search Results: Returns up to 50 most relevant matches to prevent flooding the agent with too many results

Current Scope:
- Focused on task-level operations rather than bulk workspace management
- Optimized for conversational AI workflows rather than data migration
- Designed for productivity enhancement, not administrative operations

These limitations ensure reliable performance while covering the most common use cases for both development context and productivity management.

License

MIT

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Clickup MCP Cdf23b21 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Clickup MCP Cdf23b21 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Clickup MCP Cdf23b21 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Clickup MCP Cdf23b21 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Clickup MCP Cdf23b21 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、Windsurf;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Clickup MCP Cdf23b21 能提供哪些能力?

资料显示约 14 个工具;能力标签包括 时间跟踪、文档处理、TypeScript、Claude、协作工具。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。