Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CLICKUP_API_TOKENYesYour ClickUp API token generated from the ClickUp user settings
CLICKUP_WORKSPACE_IDYesYour ClickUp Workspace ID (found in the URL: https://app.clickup.com/{workspace_id}/home)

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
clickup_get_task_by_custom_idC

Get a task by its custom ID

clickup_get_taskC

Get a task by its ID

clickup_create_taskC

Create a new task in ClickUp

clickup_update_taskC

Update a task by its ID

clickup_update_task_by_custom_idC

Update a task by its custom ID

get_spacesB

Get all spaces in the workspace

get_foldersB

Get all folders in a space

get_listsB

Get all lists in a folder

create_listC

Create a new list in a folder

clickup_get_list_custom_fieldsC

Get all accessible custom fields for a list

clickup_set_custom_field_valueB

Set a value for a custom field on a task

clickup_set_custom_field_value_by_custom_idC

Set a value for a custom field on a task using the task's custom ID

get_list_assigneesC

Get all members (potential assignees) of a list

clickup_search_docsC

Search for docs in a specific parent

clickup_create_docC

Create a new doc in ClickUp

clickup_get_doc_pagesC

Get pages from a ClickUp doc

clickup_get_pageC

Get a page from a ClickUp doc

clickup_create_pageC

Create a new page in a ClickUp doc

clickup_edit_pageC

Edit a page in a ClickUp doc

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 19 tools

Disambiguation4/5

Most tools have distinct purposes targeting specific ClickUp resources (docs, tasks, lists, folders, spaces), but there is some overlap between task-related tools (e.g., clickup_update_task and clickup_update_task_by_custom_id) and custom field tools that could cause confusion if not carefully distinguished by ID type. The descriptions help clarify, but the duplication in functionality for tasks and custom fields creates minor ambiguity.

Naming Consistency3/5

The naming is mixed: most tools use a consistent 'clickup_verb_noun' pattern (e.g., clickup_create_task, clickup_get_doc_pages), but some tools deviate with a simpler 'verb_noun' format (e.g., create_list, get_folders) without the 'clickup_' prefix. This inconsistency breaks the pattern and makes the set less predictable, though the names remain readable and descriptive overall.

Tool Count4/5

With 19 tools, the count is on the higher side but reasonable for a comprehensive ClickUp integration covering docs, tasks, lists, folders, and spaces. It feels slightly heavy due to some redundancy (e.g., multiple task and custom field tools), but each tool serves a specific purpose, and the scope justifies the number to handle various operations in the domain.

Completeness4/5

The tool set provides good coverage for core ClickUp operations, including CRUD for docs, pages, tasks, lists, folders, and spaces, as well as custom field management and search. Minor gaps exist, such as no direct tools for deleting resources or managing comments/attachments, but agents can likely work around these with the available tools for basic workflows in the domain.

Maintenance

ActivityInactive
ResponsivenessNo issues