ClickUp MCP Server

Overview

This page documents the official ClickUp-hosted MCP server at https://mcp.clickup.com/mcp. It lets MCP-compatible AI assistants work with ClickUp workspace data — tasks, lists, folders, docs, time tracking, and chat — using natural language, and is available on all ClickUp plans.

Key Features

Available Tools

Quick Reference

ClickUp's docs name tools by display name rather than by a code identifier. The names and definitions below are taken from ClickUp's supported tools reference.

Detailed Usage

ClickUp's docs describe each tool and example prompts, but do not publish argument schemas; the assistant discovers them from the server at connect time.

Installation

The server endpoint is https://mcp.clickup.com/mcp. There is no package to install or API token to create — you add the remote URL to your client and complete ClickUp's OAuth flow.

{
  "mcpServers": {
    "clickup": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.clickup.com/mcp"]
    }
  }
}

Setup Guide

1. Add the Remote Server

Use the endpoint https://mcp.clickup.com/mcp in your client's remote MCP / connector settings. Your client must support OAuth 2.1 with PKCE over HTTP to pass ClickUp's authorization flow.

2. Authorize the Workspace

Sign in to ClickUp when prompted and select the Workspace you want the assistant to use. ClickUp's server authenticates with OAuth only; API keys and personal access tokens cannot be used.

3. Confirm Permissions

Your assistant can only perform actions in ClickUp that you have permission to do. ClickUp's FAQ states that deletion tools have not been added as a safety measure, while its supported tools reference lists a Delete task tool — check which tools your client actually exposes.

Common Use Cases

1. Sprint Planning and Task Creation

Create tasks and place them in the right List. ClickUp's docs do not publish argument schemas, so the assistant supplies arguments based on the tool definitions the server returns:

use_mcp_tool({ server_name: "clickup", tool_name: "Search Workspace" });
use_mcp_tool({ server_name: "clickup", tool_name: "Create Task" });

2. Daily Standup Report Generation

Retrieve task comments and task details for a standup summary:

use_mcp_tool({ server_name: "clickup", tool_name: "Get Task Comments" });
use_mcp_tool({ server_name: "clickup", tool_name: "Get Task" });

3. Automated Task Status Updates

Update a task when a workflow trigger fires:

use_mcp_tool({ server_name: "clickup", tool_name: "Update Task" });

4. Workspace Documentation and Organization

Read Docs and organize work into folders and lists:

use_mcp_tool({ server_name: "clickup", tool_name: "Get Document Pages" });
use_mcp_tool({ server_name: "clickup", tool_name: "Create Folder" });
use_mcp_tool({ server_name: "clickup", tool_name: "Create List" });

5. Time Tracking

Log work and check the current timer:

use_mcp_tool({ server_name: "clickup", tool_name: "Add Time Entry" });
use_mcp_tool({ server_name: "clickup", tool_name: "Get Current Time Entry" });

ClickUp Hierarchy

Understanding ClickUp's organizational structure:

Workspace (Team)
└── Space
    ├── Folder (optional)
    │   └── List
    │       └── Task
    │           ├── Subtask
    │           └── Checklist
    └── List (folderless)
        └── Task

Get Workspace Hierarchy returns the Spaces, Folders, and Lists in a Workspace.

Custom Fields

The server exposes a Set Custom Fields tool. Per ClickUp's docs, the assistant understands the custom fields, options, and supported values that are available on tasks.

Best Practices

1. Create tasks in the right List: Create Task requires a target List, so resolve the hierarchy first with Get Workspace Hierarchy
2. Set realistic due dates: Include due dates so priority filtering and calendar views stay useful
3. Keep Workspace structure clear: Use Spaces, Folders, and Lists to organize related work
4. Use tags for cross-cutting concerns: Priority, category, or client labels can be applied with Add Tag to Task
5. Resolve assignees first: Use Resolve Assignees before assigning a task so the assistant picks the correct user IDs
6. Use bulk tools for group changes: Update Bulk Tasks changes status, assignee, or due date for many tasks in one call

Rate Limits

ClickUp's MCP server rate limits depend on the Workspace plan and on whether the Workspace has purchased the Everything AI add-on.

With the Everything AI add-on, MCP rate limits match the Public API rate limits, which vary by plan.

Without the add-on, MCP calls per rolling 24 hours are:

• Limits are per Workspace and per client; each client gets its own allowance.
• Each tool call counts as 1; initialize and tools/list do not count.
• When the limit is reached, the call returns RATE_LIMIT_EXCEEDED with retryAfter.
• Limits cannot be reset, and sending requests while limited does not extend the window.

Community Alternative

nsxdavid/clickup-mcp-server is an MIT-licensed, community-maintained local server that uses a ClickUp API token via the CLICKUP_API_TOKEN environment variable. It is not ClickUp-maintained; use it only if you need a local stdio server instead of ClickUp's hosted endpoint. Its tool set differs from the official server and is not documented here.

Sources

• https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server
• https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server-1
• https://developer.clickup.com/docs/mcp-tools
• https://github.com/nsxdavid/clickup-mcp-server