clickup-mcp
# clickup-mcp
A thin [Model Context Protocol (MCP)](https://modelcontextprotocol.io) server that exposes the full [ClickUp REST API v2](https://developer.clickup.com/reference/) as MCP tools.
Connect any MCP-compatible client (Claude Desktop, Cursor, etc.) to manage your ClickUp workspaces through natural language.
## Features
- **Workspaces & Teams** — list workspaces, get workspace members
- **Spaces** — CRUD operations on spaces
- **Folders** — CRUD operations on folders
- **Lists** — CRUD operations on lists, folderless lists
- **Tasks** — full task lifecycle: create, read, update, delete, move, duplicate
- **Task Fields** — custom fields, assignees, tags, checklists, attachments
- **Members** — workspace and list members
- **Comments** — task and list comments
- **Goals & Key Results** — create and track goals
- **Views** — workspace, space, folder, and list views
- **Webhooks** — create and manage webhooks
- **Time Tracking** — log and query time entries
## Setup
### 1. Get a ClickUp API Token
Go to **ClickUp → Settings → Apps** and generate a personal API token.
### 2. Install
```bash
npm install -g clickup-mcp
```
### 3. Configure Claude Desktop
Add to `claude_desktop_config.json`:
```json
{
"mcpServers": {
"clickup": {
"command": "clickup-mcp",
"env": {
"CLICKUP_API_TOKEN": "your_token_here"
}
}
}
}
```
### 4. Run directly
```bash
CLICKUP_API_TOKEN=your_token clickup-mcp
```
## Environment Variables
| Variable | Required | Description |
|---|---|---|
| `CLICKUP_API_TOKEN` | Yes | Personal API token from ClickUp Settings → Apps |
| `CLICKUP_TEAM_ID` | No | Default team/workspace ID (used when not specified in tool calls) |
## Development
```bash
git clone https://github.com/MohanadAlrefaai/clickup-mcp.git
cd clickup-mcp
npm install
npm run dev
```
## License
MIT
TDQS
Scored across 97 tools
Most tools target distinct resource-action pairs (e.g., create_space vs create_list vs create_folder are clearly different). A few potential overlaps exist: get_time_entries vs create_time_entry vs start_timer manage similar data, and get_task_watchers/add_task_watcher overlap with task membership. Overall boundaries are mostly clear.
The vast majority follow a consistent verb_noun pattern (e.g., create_space, update_task, delete_comment, get_lists). Minor deviations exist: get_folderless_lists, get_filtered_team_tasks, and set_custom_field_value break the simple verb_noun form but are still readable and logical.
97 tools is far too many for most agentic use cases, despite ClickUp's broad surface. The count exceeds the heavy threshold (25+) by a wide margin, and the score reflects that the surface is bloated even if ClickUp genuinely offers this many operations.
The coverage is remarkably comprehensive: full CRUD across workspaces, spaces, folders, lists, tasks, comments, time entries, goals, key results, checklists, tags, views, webhooks, guests, and custom fields. There are essentially no dead ends—everything from creation through deletion is covered.