Name: ClickUp MCP Server by Diversio
Author: DiversioTeam

LABSCO SUMMARY

Task management only, and it says so.

The README names what it does not cover — Docs, whiteboards, dashboards, automations, goals, attachments, webhooks, calendar views — and puts coverage at roughly 30-40% of the ClickUp API. That trade buys a tool surface aimed at the daily loop, with bulk operations and flexible id parsing that make agent-driven edits practical. There is no built-in rate limiting against ClickUp's 100 requests per minute, so a large bulk run is the place to be careful.

What it is

An MCP server over the ClickUp API v2 that deliberately covers task management rather than all of ClickUp. It handles tasks, lists, comments, assignments, time tracking and team analytics, and accepts task references in whatever form you already have them — a standard id, a custom id like gh-123, a #123 hash, or a pasted ClickUp URL.

What you get

Task CRUD plus two shortcuts that are awkward in the UI: create_task_from_template for bug-report, feature-request and code-review shapes, and create_task_chain for a sequence of dependent tasks
Finding work: list_tasks, search_tasks, get_subtasks, and find_list_by_name so a list can be named rather than looked up by id
Bulk edits in one call — bulk_update_tasks and bulk_move_tasks across many tasks at once
Time tracking with log_time and get_time_tracked, and two reporting tools: get_team_workload for distribution across members and get_task_analytics for velocity and completion rates
People handling that does not need ids: find_user_by_name resolves a name or email, then assign_task attaches them
Comments through get_task_comments and create_task_comment

Requirements

A ClickUp personal API token, generated under Settings → Apps → API and shown only once. Store it for every client with uvx --from git+https://github.com/DiversioTeam/clickup-mcp clickup-mcp set-api-key YOUR_API_KEY; exporting CLICKUP_MCP_API_KEY only reaches a client started from that same terminal. Python 3.10+. The package is clickup-mcp (version 0.1.0), run with uvx --from git+https://github.com/DiversioTeam/clickup-mcp clickup-mcp. The token carries the same permissions as your own account. MIT licensed.

Setup effort

One command plus a key — uvx --from git+https://github.com/DiversioTeam/clickup-mcp clickup-mcp, then supply credentials

See installation options

USE CASES

01

Filing a bug without leaving the conversation

Create the task from the bug-report template into a named list, add the reproduction as a comment, and assign it by the person's name.

create_task_from_templatefind_list_by_namecreate_task_commentassign_task

02

Cleaning up after a sprint

Find the completed tasks, then move or update them all in one call instead of dragging cards one at a time.

search_tasksbulk_move_tasksbulk_update_tasks

03

Checking who is overloaded

Read task distribution across the team and completion rates for the period, then reassign the tasks that stand out.

get_team_workloadget_task_analyticsassign_task

04

Logging time against a task you only know by its custom id

Reference the task as gh-123 or by its ClickUp URL and log the hours directly.

log_timeget_time_tracked

05

Setting up a staged piece of work

Create a chain of dependent tasks — design, implement, test, deploy — in a single request rather than four with manual links.

create_task_chain

28 tools

Listed in project docs. Your client may show a different list.

create_task

get_task

update_task

delete_task

create_task_from_template

create_task_chain

list_tasks

search_tasks

get_subtasks

get_task_comments

create_task_comment

get_task_status

update_task_status

get_assignees

assign_task

BEFORE YOU INSTALL

What to know first

Tools you get

28 tools named in the project's documentation.

Requires

uvx on PATH
CLICKUP_MCP_API_KEY in your environment

Where it runs

All 5 documented setups run the server on your machine.

INSTALLATION

Connect your client

Server setup

TERMINAL

uvx --from git+https://github.com/DiversioTeam/clickup-mcp clickup-mcp

MCP Clients

Claude Code, Claude Desktop

JSON

{
  "mcpServers": {
    "clickup": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/DiversioTeam/clickup-mcp.git",
        "clickup-mcp"
      ]
    }
  }
}

The configuration on this page does not set CLICKUP_MCP_API_KEY. The project stores it for every client with its set-api-key command, run through the same install: uvx --from git+https://github.com/DiversioTeam/clickup-mcp clickup-mcp set-api-key YOUR_API_KEY. An export line only reaches a client started from that same terminal, so it does not reach Claude Desktop.

VS Code

JSON

{
  "servers": {
    "clickup": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/DiversioTeam/clickup-mcp.git",
        "clickup-mcp"
      ]
    }
  }
}

The configuration on this page does not set CLICKUP_MCP_API_KEY. The project stores it for every client with its set-api-key command, run through the same install: uvx --from git+https://github.com/DiversioTeam/clickup-mcp clickup-mcp set-api-key YOUR_API_KEY. An export line only reaches a client started from that same terminal, so it does not reach Claude Desktop.

Claude Code — local build

For testing a local checkout. First clone and sync it — git clone https://github.com/DiversioTeam/clickup-mcp, cd clickup-mcp, uv sync — then run this from inside that folder:

CLAUDE CODE — LOCAL BUILD · TERMINAL

claude mcp add clickup-local -- uv run clickup-mcp

uv run finds clickup-mcp only in the project folder, so start Claude Code from your clone.

ClickUp MCP Server by Diversio