Log inSubmit server
Clickup MCP logo

Clickup MCP

Manage ClickUp workspaces, lists, tasks, tags, checklists, and dependencies through token-optimized MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Clickup MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "clickup-mcp": {
      "command": "npx",
      "args": [
        "@cavort-it-systems/clickup-mcp"
      ],
      "env": {
        "CLICKUP_API_TOKEN": "YOUR_VALUE_HERE",
        "CLICKUP_TEAM_ID": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

The clickup-mcp MCP server connects AI clients to ClickUp for workspace navigation and task management. It exposes tools for lists, tasks, custom fields, tags, checklists, dependencies, comments, members, attachments, and multi-list membership. Responses are trimmed to reduce unnecessary API fields and token usage. Use it when an agent needs to inspect or update ClickUp work without relying on the web interface; note that the repository is unmaintained.

Use cases

  • Browse ClickUp spaces, folders, and lists
  • Create and update ClickUp tasks
  • Search workspace tasks with compact responses
  • Manage tags, checklists, and dependencies
  • Add comments, replies, or attachments to tasks

Key features

  • ClickUp workspace and list navigation
  • Task CRUD and workspace-wide search
  • Token-optimized JSON responses
  • Tags, custom fields, and checklists
  • Task dependencies, comments, and attachments
  • Secondary list membership management

Tools40

What Clickup MCP lets your agent do. Expand a tool for its parameters.

Verified live~5.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

8/8 checks healthy over the last 45d

What it can do

From the 40 tools this server returned when we ran it.

Can delete or modify data · 9Read-only tools · 31
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age255 days
Maintainers1

Observed 2026-10-16 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @cavort-it-systems/clickup-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads588Package downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Tools exposed40Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Clickup MCP works

What clickup-mcp does

The clickup-mcp MCP server exposes ClickUp API operations through MCP tools for workspace navigation and task management. Agents can identify the current user and available workspaces, browse spaces, folders, and lists, and inspect list status settings. They can also create or delete lists, retrieve tasks, create tasks, update task fields, search across a workspace, and set custom field values.

Task organization features cover space tags, task tagging, checklists, dependencies, comments, workspace members, list members, and local file attachments. The repository also includes tools for adding or removing a task from an additional list, creating task links, and working with threaded comments and replies. The supplied task tools accept ClickUp custom task IDs such as DEV-1217 as well as internal IDs.

How it works

The server uses the ClickUp API v2 through an MCP stdio transport. An MCP client starts the process, passes the API token through the environment, and invokes named tools with their inputs. Responses are transformed before being returned to the model. The slimming logic removes fields such as visual user metadata, watcher details, internal permission data, empty task arrays, and version blobs from mutation responses, while compacting the resulting JSON.

The workspace ID is read from CLICKUP_TEAM_ID when set. If it is not set, the server obtains the ID from the token’s only accessible workspace once. Tokens that can access multiple workspaces must set CLICKUP_TEAM_ID so requests target the intended workspace.

Setup and configuration

Install the published package globally with npm, run it through npx, or build it from source with pnpm. Configure an MCP client to launch the package and provide CLICKUP_API_TOKEN, which is a ClickUp Personal API Token generated under ClickUp Settings > Apps. Claude Code can register the server with claude mcp add; Claude Desktop can use an MCP configuration containing the command, package arguments, and environment variables.

A source installation requires cloning the repository, running pnpm install && pnpm build, and launching the generated build/index.js with Node. Set CLICKUP_TEAM_ID for tokens associated with more than one workspace.

Tools and capabilities

The clickup-mcp MCP server supports these operational areas:

  • Navigate workspaces, spaces, folders, lists, and members.
  • Create, read, update, search, and permanently delete tasks.
  • Create, inspect, update, and permanently delete lists.
  • Set custom fields and manage task tags.
  • Create, edit, and delete checklists and checklist items.
  • Add and remove task dependencies, links, comments, replies, and attachments.
  • Add or remove secondary list membership for tasks.

Limitations and notes

The repository is marked unmaintained because ClickUp was retired at CAVORT on 2026-10-18, after a cutover to Console. It is retained as-is and is no longer developed.

Adding a task to another list creates an additional location; it does not move the task from its home list. Removing list membership applies only to an additional list, not the home list. Multi-list operations require ClickUp’s paid Tasks-in-Multiple-Lists feature. The ClickUp API does not provide a move-between-lists operation, so moving a task while preserving its custom ID and history requires the ClickUp web UI. Deleting lists, tasks, checklists, or checklist items is permanent where the tool descriptions specify it.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Clickup MCP

clickup-mcp is an MCP server that connects AI clients to ClickUp through the ClickUp API. Its main tools navigate workspaces, spaces, folders, and lists; create, read, update, search, and delete tasks; and manage tags, custom fields, checklists, dependencies, comments, members, and attachments.

Install it with npm or run it with npx: `npm install -g @cavort-it-systems/clickup-mcp` or `npx @cavort-it-systems/clickup-mcp`. You can also clone the repository, install dependencies with pnpm, and build it before configuring the generated Node entry point.

Set `CLICKUP_API_TOKEN` to a ClickUp Personal API Token and configure your MCP client to launch the package with stdio. Set `CLICKUP_TEAM_ID` as well when the token can access multiple workspaces; otherwise, the server discovers the token’s only workspace.

Yes, clickup-mcp works with Claude Desktop through its MCP configuration. Add an entry that launches `npx @cavort-it-systems/clickup-mcp` and supplies `CLICKUP_API_TOKEN` in the entry’s environment.

No, clickup-mcp cannot move a task between lists through the ClickUp API. Its multi-list tools add or remove an additional list location, while the task’s home list stays unchanged. Use ClickUp’s web UI to perform an actual move.

Related MCP servers

All in Workplace & Productivity All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewClickup MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/clickup-mcp?style=directory)](https://allmcps.com/mcp/clickup-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/clickup-mcp"><img src="https://allmcps.com/api/badge/clickup-mcp?style=directory" alt="Clickup MCP on AllMCPs" /></a>