Skip to main content
Glama
windalfin

ClickUp MCP Server

by windalfin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CLICKUP_API_KEYYesYour ClickUp API key from ClickUp Settings
CLICKUP_TEAM_IDYesYour Team ID from your ClickUp workspace URL

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_workspace_hierarchyB

Get the complete workspace hierarchy including spaces, folders, and lists.

create_taskA

Create a single task in a ClickUp list. Use this tool for individual task creation only. For multiple tasks, use create_bulk_tasks instead. Before calling this tool, check if you already have the necessary list ID from previous responses in the conversation history, as this avoids redundant lookups. When creating a task, you must provide either a listId or listName.

get_taskA

Retrieve detailed information about a specific task. Valid parameter combinations:

  1. Use taskId alone (preferred)

  2. Use taskName + optional listName (to disambiguate if multiple tasks have the same name)

get_tasksA

Retrieve tasks from a list with optional filtering. You MUST provide either:

  1. listId (preferred)

  2. listName

Use filters to narrow down results by status, dates, etc.

update_taskA

Modify an existing task's properties. Valid parameter combinations:

  1. Use taskId alone (preferred if you have it)

  2. Use taskName + optional listName (to disambiguate if multiple tasks have the same name)

At least one update field (name, description, status, priority) must be provided. Only specified fields will be updated.

move_taskA

Move a task to a different list. Valid parameter combinations:

  1. Use taskId + (listId or listName) - preferred

  2. Use taskName + sourceListName + (listId or listName)

WARNING: Task statuses may reset if destination list has different status options.

duplicate_taskA

Create a copy of a task in the same or different list. Valid parameter combinations:

  1. Use taskId + optional (listId or listName) - preferred

  2. Use taskName + sourceListName + optional (listId or listName)

The duplicate preserves the original task's properties.

delete_taskA

⚠️ PERMANENTLY DELETE a task. This action cannot be undone. Valid parameter combinations:

  1. Use taskId alone (preferred and safest)

  2. Use taskName + optional listName (use with caution)

create_bulk_tasksA

Create multiple tasks in a list efficiently. You MUST provide:

  1. An array of tasks with required properties

  2. Either listId or listName to specify the target list

Optional: Configure batch size and concurrency for performance.

update_bulk_tasksB

Update multiple tasks efficiently. For each task, you MUST provide either:

  1. taskId alone (preferred)

  2. taskName + listName

Only specified fields will be updated for each task.

move_bulk_tasksA

Move multiple tasks to a different list efficiently. For each task, you MUST provide either:

  1. taskId alone (preferred)

  2. taskName + listName

WARNING: Task statuses may reset if target list has different status options.

delete_bulk_tasksA

⚠️ PERMANENTLY DELETE multiple tasks. This action cannot be undone. For each task, you MUST provide either:

  1. taskId alone (preferred and safest)

  2. taskName + listName (use with caution)

create_listA

Create a new list directly in a ClickUp space (not in a folder). You MUST provide either spaceId or spaceName. For creating lists inside folders, use create_list_in_folder instead.

create_list_in_folderA

Create a new list within a ClickUp folder. You MUST provide either: 1) folderId alone, or 2) folderName WITH either spaceName or spaceId. Folder names may not be unique across spaces, which is why space information is required when using folderName.

get_listA

Retrieve details about a specific ClickUp list. You MUST provide either listId or listName. Using listId is more reliable as list names might not be unique.

update_listB

Update an existing ClickUp list's properties. You MUST provide either listId or listName, and at least one field to update (name, content, or status).

delete_listA

Permanently delete a ClickUp list and all its tasks. You MUST provide either listId or listName. WARNING: This action cannot be undone.

create_folderA

Create a new folder in a ClickUp space for organizing related lists. You MUST provide:

  1. A folder name

  2. Either spaceId (preferred) or spaceName

After creating a folder, you can add lists to it using create_list_in_folder.

get_folderA

Retrieve details about a specific folder including name, status, and metadata. Valid parameter combinations:

  1. Use folderId alone (preferred)

  2. Use folderName + (spaceId or spaceName)

Helps you understand folder structure before creating or updating lists.

update_folderB

Modify an existing folder's properties. Valid parameter combinations:

  1. Use folderId alone (preferred)

  2. Use folderName + (spaceId or spaceName)

At least one update field (name or override_statuses) must be provided.

delete_folderA

⚠️ PERMANENTLY DELETE a folder and all its contents. This action cannot be undone. Valid parameter combinations:

  1. Use folderId alone (preferred and safest)

  2. Use folderName + (spaceId or spaceName)

WARNING: This will also delete all lists and tasks within the folder.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 21 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. Tools are organized by resource (task, list, folder) and action (create, get, update, delete, move, duplicate), with clear boundaries between individual and bulk operations. Descriptions explicitly differentiate similar tools, such as create_task vs. create_bulk_tasks and move_task vs. move_bulk_tasks.

Naming Consistency5/5

Tool names follow a consistent verb_noun pattern throughout, with verbs like create, get, update, delete, move, and duplicate paired with nouns like task, list, folder, and workspace_hierarchy. Bulk operations are consistently prefixed with 'bulk_' (e.g., create_bulk_tasks, delete_bulk_tasks), maintaining a predictable and readable naming convention.

Tool Count4/5

With 21 tools, the count is slightly high but reasonable for a comprehensive project management server like ClickUp. It covers multiple resources (tasks, lists, folders, workspace) and actions (CRUD, move, duplicate), which justifies the breadth. However, it borders on being heavy, as some tools could potentially be consolidated (e.g., individual and bulk operations might be combined with parameters).

Completeness5/5

The tool set provides complete CRUD/lifecycle coverage for the ClickUp domain, including tasks, lists, folders, and workspace hierarchy. It supports creation, retrieval, updating, deletion, moving, and duplication operations, with both individual and bulk variants where applicable. There are no obvious gaps; agents can manage the full lifecycle of resources without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources