Log inSubmit server
Clickup logo

Clickup

Connects AI agents to ClickUp for tasks, documents, comments, chat, goals, views, time tracking, and workspace administration.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Clickup

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-2": {
      "command": "npx",
      "args": [
        "-y",
        "@taazkareem/clickup-mcp-server@latest"
      ]
    }
  }
}

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

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y @taazkareem/clickup-mcp-server@latest

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 8d ago.

Overview

The clickup MCP server connects AI agents to ClickUp for managing tasks, documents, comments, chat, goals, views, time entries, and workspace structures. It exposes MCP tools that can resolve ClickUp entities through search, reducing the need to provide IDs for common operations. Authentication supports OAuth 2.1 as well as API key and team ID configurations, with multi-workspace support. Reach for it when an agent needs to read or modify ClickUp project data through natural-language requests.

Use cases

  • Create and update ClickUp tasks from natural-language requests
  • Search workspace items without supplying ClickUp IDs
  • Track timers and review time entries by date range
  • Maintain ClickUp Docs, comments, chat channels, and goals

Key features

  • Task CRUD, dependencies, subtasks, checklists, sprints, and attachments
  • Workspace-wide search and entity resolution
  • ClickUp Docs and page management
  • Time tracking and time-entry history
  • Comments, chat, goals, views, tags, and workspace hierarchy controls

Security & health

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

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @taazkareem/clickup-mcp-server@latest (npm)

Adoption & maintenance

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

GitHub stars52Stargazers on the source repository.
npm downloads28kPackage downloads in the last 30 days.
Last commit12d agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Clickup works

What clickup MCP server does

The clickup MCP server exposes ClickUp workspace operations through the Model Context Protocol. It covers work management objects such as tasks, checklists, sprints, comments, tags, spaces, folders, lists, views, files, documents, chat channels, goals, and time entries. The integration supports both reading and changing data, so an agent can coordinate project updates as well as retrieve information.

Its search and resolution features can locate tasks, lists, folders, spaces, members, statuses, tags, descriptions, and custom fields using names or other searchable information. This is useful when an agent has a human-readable reference but not a ClickUp ID.

How it works

The server receives MCP tool calls from a compatible client and applies them to ClickUp. Authentication can use OAuth 2.1, or the README’s backward-compatible API key and team ID approach. OAuth sessions use isolated caching, and the server supports multiple authorized workspaces in one session. Workspaces can also be switched during a conversation without reconfiguring the connection.

Operations include standard create, read, update, and delete actions where supported, along with bulk actions, relationship management, and natural-language date handling. The available functionality is organized around ClickUp’s hierarchy and collaboration features rather than a separate local data store.

Setup and configuration

The clickup MCP server is distributed as the npm package @taazkareem/clickup-mcp-server. It also describes OAuth-based access and API key/team ID compatibility.

The material provided does not specify required environment variable names or a single universal configuration file. Authentication and workspace selection therefore need to be configured according to the selected client setup and the access method used.

Tools and capabilities

The clickup MCP server supports capabilities including:

  • Creating, reading, updating, deleting, moving, duplicating, linking, and assigning dependencies between tasks.
  • Handling subtasks, checklists, sprints, custom task IDs and types, custom fields, templates, and attachments from URLs, local paths, or base64 data.
  • Starting and stopping timers, adding or editing manual time entries, reviewing timer history, and filtering entries by dates or ranges.
  • Creating, reading, and appending Markdown content in ClickUp Docs, including managing document pages.
  • Posting, editing, resolving, and replying to comments on tasks, lists, and views.
  • Managing chat channels and direct messages, including threaded replies, reactions, followers, rich text, and mentions.
  • Managing goals and nested key results, plus creating, updating, deleting, and archiving goals.
  • Creating and managing views at the space, folder, or list level and retrieving view-scoped tasks.
  • Managing spaces, folders, lists, webhooks, tags, and access-control permissions across the workspace hierarchy.

Limitations and notes

It also does not list required environment variables, so those details should be checked in the repository or package documentation before deployment.

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

clickup is an MCP server that connects AI agents to ClickUp workspaces. Its main tools manage tasks, checklists, sprints, comments, documents, chat, goals, views, time entries, spaces, folders, lists, tags, webhooks, and permissions. It supports workspace search and can resolve many entities without requiring their IDs in each request.

Install it from the npm package `@taazkareem/clickup-mcp-server` and follow the client-specific setup documented in the repository.

It supports OAuth 2.1 and also provides backward compatibility for API key and team ID authentication. The server is described as supporting multiple authorized workspaces in one session, with isolated session caching and workspace switching during a conversation.

Yes, the README includes a Cursor setup section. It also names VS Code, Claude Desktop, Claude Code, Codex, Windsurf, and Roo Code as setup targets.

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 AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/clickup-2?style=directory)](https://allmcps.com/mcp/clickup-2)
HTML Embed
<a href="https://allmcps.com/mcp/clickup-2"><img src="https://allmcps.com/api/badge/clickup-2?style=directory" alt="Clickup on AllMCPs" /></a>