ClickUp MCP Server

A Model Context Protocol (MCP) server for ClickUp. Manage tasks, track time, change status, and post daily standup updates to ClickUp Chat — all from Claude Code, Cursor, Claude Desktop, or any MCP-compatible AI tool.

Tell your AI: "Create Test task in AI Role Play, log 2 hours, mark delivered, and post my daily update to the channel" → done in seconds, no context-switching.

Companion Chrome extension

This repo also ships a Chrome extension that builds the same daily standup format from your tracked time, no AI needed. Pick a date and folder, hit Copy, paste into ClickUp Chat.

→ extension/README.md for install + usage. Pre-built zips are on the Releases page.

Features

• Log tasks — auto-assigns to you, finds the right space/list (including lists inside Sprint folders)
• Track real time — log actual hours spent (not just estimates) as a real time entry
• Update status — Open → In Progress → Delivered with one line
• Discover — list spaces, folders, lists, and chat channels in your workspace
• Daily standup updates — formatted message to any ClickUp Chat channel:
  • Done Today (with task links + time spent)
  • Planned for Tomorrow
  • AI Usage
  • Challenges / Blockers

Setup

1. Get Your ClickUp API Key

1. ClickUp → Settings → Apps
2. Click Generate under API Token
3. Copy the pk_... key — you'll need it below

2. Install the Server

Recommended — install globally (works from anywhere on your system):

npm install -g clickup-task-mcp

After install, the clickup-task-mcp command is available system-wide. Verify:

which clickup-task-mcp     # should print a path
clickup-task-mcp --help    # (or just runs the server on stdio)

To upgrade later:

npm update -g clickup-task-mcp

Alternative — build from source (for contributors):

git clone git@github.com:arslan8122/clickup-mcp.git
cd clickup-mcp
npm install
npm run build

No .env file needed for normal use. You'll pass your API key directly to your AI client below.

3. Connect to Your AI Client

Pick the section that matches your tool. The API key is passed as an environment variable by the client when it launches the server.

Claude Code

After global install:

claude mcp add clickup -s user -e CLICKUP_API_KEY=pk_your_key_here -- clickup-task-mcp

If built from source:

claude mcp add clickup -s user -e CLICKUP_API_KEY=pk_your_key_here -- node /absolute/path/to/clickup-mcp/dist/index.js

Restart Claude Code, then run /mcp to confirm it's connected.

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "clickup": {
      "command": "clickup-task-mcp",
      "env": {
        "CLICKUP_API_KEY": "pk_your_key_here"
      }
    }
  }
}

Or if built from source, use:

{
  "mcpServers": {
    "clickup": {
      "command": "node",
      "args": ["/absolute/path/to/clickup-mcp/dist/index.js"],
      "env": {
        "CLICKUP_API_KEY": "pk_your_key_here"
      }
    }
  }
}

Restart Claude Desktop.

Cursor / Other MCP Clients

Same JSON shape as Claude Desktop, in the client's MCP config file. After a global install, the command is just clickup-task-mcp with no args needed.

Environment Variables

... View full README on GitHub