com.mcparmory/clickup
OCI · GHCR.IO/MCPARMORY/CLICKUP:1.0.4 · 2 COMPONENTS · SCANNED SEP 20
Manage tasks, lists, checklists, comments, and project workflows
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 25980 tokens (~193/item across 134 items; 134 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 26 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 134 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/clickup MCP server?
com.mcparmory/clickup runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/clickup:1.0.4. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/clickup:1.0.4
claude mcp add com-mcparmory-clickup -- docker run --rm -i ghcr.io/mcparmory/clickup:1.0.4
{
"mcpServers": {
"com-mcparmory-clickup": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/clickup:1.0.4"
]
}
}
} {
"servers": {
"com-mcparmory-clickup": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/clickup:1.0.4"
]
}
}
} codex mcp add com-mcparmory-clickup -- docker run --rm -i ghcr.io/mcparmory/clickup:1.0.4
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-clickup": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/clickup:1.0.4"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-clickup:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/clickup:1.0.4"] {
"McpServers": {
"com-mcparmory-clickup": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/clickup:1.0.4"
]
}
}
} {
"mcpServers": {
"com-mcparmory-clickup": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/clickup:1.0.4"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.77 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −2
- Stability: pass → 0.80 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/clickup:1.0.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_guest_to_folder Add Guest to Folder ~144
Share a folder with a guest user by granting them a specific permission level. This endpoint is only available on the Enterprise Plan.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | number | yes | The unique identifier of the folder to share with the guest. |
| guest_id | number | yes | The unique identifier of the guest user to whom folder access will be granted. |
| include_shared | boolean | – | Whether to include details of items already shared with the guest in the response. Set to false to exclude shared item details. |
| permission_level | string | yes | The access level granted to the guest for this folder. Accepted values are: read (view only), comment, edit, or create (full access). |
No output schema declared.
No examples provided.
add_guest_to_list Add Guest to List ~146
Share a List with a guest user by granting them a specific permission level. This endpoint is exclusively available to Workspaces on the Enterprise Plan.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_id | number | yes | The unique identifier of the guest user to add to the List. |
| include_shared | boolean | – | Whether to include details of items already shared with the guest. Set to false to exclude shared item details; defaults to true. |
| list_id | number | yes | The unique identifier of the List to share with the guest. |
| permission_level | string | yes | The access level granted to the guest on this List. Accepted values are: read (view only), comment, edit, or create (full access). |
No output schema declared.
No examples provided.
add_guest_to_task Add Guest to Task ~149
Share a task with a guest user by granting them a specific permission level. This endpoint is only available to Workspaces on the Enterprise Plan.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_id | number | yes | The unique numeric identifier of the guest user to add to the task. |
| include_shared | boolean | – | Whether to include details of items shared with the guest in the response. Set to false to exclude shared item details; defaults to true. |
| permission_level | string | yes | The access level granted to the guest on this task. Accepted values are: read (view only), comment, edit, or create (full access). |
| task_id | string | yes | The unique identifier of the task to share with the guest. |
No output schema declared.
No examples provided.
add_list_comment Add List Comment ~136
Adds a comment to a specified List, optionally notifying the comment creator in addition to the standard assignees and watchers who are always notified.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | integer | yes | The user ID of the individual to assign to this comment. |
| comment_text | string | yes | The text content of the comment to be posted on the List. |
| list_id | number | yes | The unique identifier of the List to which the comment will be added. |
| notify_all | boolean | yes | When set to true, the creator of the comment will also receive a notification. Assignees and watchers on the List are always notified regardless of this setting. |
No output schema declared.
No examples provided.
add_tag_to_task Add Tag to Task ~170
Adds an existing tag to a specified task, associating it for organization and filtering purposes. Supports referencing tasks by custom task ID when the appropriate parameters are provided.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request body, which must indicate JSON format. |
| custom_task_ids | boolean | – | Set to true to reference the task by its custom task ID instead of the default system-generated task ID. |
| tag_name | string | yes | The name of the tag to add to the task. Must match an existing tag name exactly. |
| task_id | string | yes | The unique identifier of the task to which the tag will be added. |
| team_id | number | – | The Workspace ID required when using custom task IDs. Must be provided alongside custom_task_ids=true to correctly resolve the task. |
No output schema declared.
No examples provided.
add_tags_to_time_entries Add Tags to Time Entries ~129
Add one or more tags to a set of time entries in a workspace. Useful for bulk-labeling time entries for categorization or reporting purposes.
| Name | Type | Req | Description |
|---|---|---|---|
| tags | array | yes | List of tag names to attach to the specified time entries. Order is not significant; each item should be a tag name string. |
| team_id | number | yes | The unique identifier of the workspace containing the time entries. |
| time_entry_ids | array | yes | List of time entry IDs to which the tags will be applied. Order is not significant; each ID should be a valid time entry identifier within the workspace. |
No output schema declared.
No examples provided.
add_task_comment Add Task Comment ~203
Add a new comment to a specified task, with options to assign the comment to a user or group and notify all relevant parties.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | integer | – | The user ID of the individual to assign to this comment. |
| comment_text | string | yes | The text content of the comment to be added to the task. |
| custom_task_ids | boolean | – | Set to true if referencing the task by its custom task ID instead of the default system-generated ID. |
| group_assignee | string | – | The ID of the group to assign to this comment. |
| notify_all | boolean | yes | When true, the comment creator is also notified in addition to task assignees and watchers, who are always notified regardless of this setting. |
| task_id | string | yes | The unique identifier of the task to which the comment will be added. |
| team_id | number | – | The Workspace ID required when using custom task IDs. Must be provided alongside custom_task_ids=true. |
No output schema declared.
No examples provided.
add_task_dependency Add Task Dependency ~244
Create a dependency relationship between two tasks, setting one task as waiting on or blocking another. Use `depends_on` to specify a task this task is waiting on, or `dependency_of` to specify a task this task is blocking.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_task_ids | boolean | – | Set to true to reference tasks by their custom task IDs instead of their default system-generated IDs. Requires `team_id` to also be provided. |
| dependency_of | string | – | The ID of the task that the specified task (`task_id`) is blocking — i.e., the task that cannot proceed until `task_id` is completed. |
| depends_on | string | – | The ID of the task that the specified task (`task_id`) is waiting on — i.e., the task that must be completed before `task_id` can proceed. |
| task_id | string | yes | The ID of the task for which the dependency relationship is being defined — either the task that is waiting on another task or the task that is blocking another task. |
| team_id | number | – | The Workspace ID required when `custom_task_ids` is true, used to resolve custom task IDs within the correct Workspace scope. |
No output schema declared.
No examples provided.
add_task_to_list Add Task to List ~87
Adds an existing task to an additional list, enabling the task to appear in multiple lists simultaneously. Requires the Tasks in Multiple Lists ClickApp to be enabled in the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | number | yes | The unique numeric identifier of the list to which the task will be added. |
| task_id | string | yes | The unique string identifier of the task to add to the specified list. |
No output schema declared.
No examples provided.
clear_task_custom_field_value Clear Task Custom Field Value ~138
Clears the stored value of a specific Custom Field on a task without deleting the Custom Field definition or its available options.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_task_ids | boolean | – | Set to true to reference the task by its custom task ID instead of the default ClickUp task ID. |
| field_id | string | yes | The UUID of the Custom Field whose value should be removed from the task. |
| task_id | string | yes | The unique identifier of the task from which the Custom Field value will be cleared. |
| team_id | number | – | The Workspace ID (team_id) required when using custom task IDs; must be paired with custom_task_ids=true. |
No output schema declared.
No examples provided.
create_chat_view_comment Create Chat View Comment ~122
Adds a new comment to a specified Chat view. Optionally notifies the comment creator in addition to the assignees and watchers who are always notified.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_text | string | yes | The text content of the comment to post on the Chat view. |
| notify_all | boolean | yes | When set to true, the creator of the comment is also notified upon posting. Assignees and watchers on the view are always notified regardless of this setting. |
| view_id | string | yes | The unique identifier of the Chat view to which the comment will be added. |
No output schema declared.
No examples provided.
create_checklist Create Checklist ~121
Add a new named checklist to a specified task, allowing you to track subtasks or steps within that task.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_task_ids | boolean | – | Set to true if referencing the task by its custom task ID instead of the default system-generated task ID. |
| name | string | yes | The display name for the new checklist. |
| task_id | string | yes | The unique identifier of the task to which the checklist will be added. |
| team_id | number | – | The Workspace ID required when using custom task IDs; must be provided alongside custom_task_ids=true. |
No output schema declared.
No examples provided.
create_checklist_item Create Checklist Item ~94
Adds a new line item to an existing task checklist. Optionally assign the item to a specific user by their ID.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | integer | – | The numeric user ID of the team member to assign this checklist item to. |
| checklist_id | string | yes | The unique identifier of the checklist to which the new item will be added. |
| name | string | – | The display name or label for the checklist item. |
No output schema declared.
No examples provided.
create_folder Create Folder ~77
Creates a new folder within a specified Space to organize lists and tasks. Folders help structure your workspace hierarchy beneath a Space.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The display name for the new folder, used to identify it within the Space. |
| space_id | number | yes | The unique identifier of the Space in which the new folder will be created. |
No output schema declared.
No examples provided.
create_folder_from_template Create Folder from Template ~823
Create a new Folder within a Space using a predefined Folder template, optionally importing nested assets such as lists, tasks, subtasks, custom fields, and more. Supports both synchronous and asynchronous creation via the `return_immediately` parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | integer | – | Controls whether archived tasks are included: 1 includes archived tasks, 2 includes only archived tasks, and null excludes archived tasks. |
| attachments | boolean | – | When true, imports file attachments from template tasks. |
| automation | boolean | – | When true, imports automation rules defined in the template. |
| comment | boolean | – | When true, imports comments from template tasks. |
| comment_attachments | boolean | – | When true, imports file attachments from task comments in the template. |
| content | string | – | Optional description text to apply to the new Folder. |
| custom_fields | boolean | – | When true, imports Custom Field definitions and values from template tasks. |
| custom_type | boolean | – | When true, imports custom task type definitions from the template. |
| due_date | string | – | The project due date used as the anchor point for remapping task dates from the template. Must be provided in ISO 8601 date-time format. |
| external_dependencies | boolean | – | When true, imports external task dependency relationships from the template. |
| include_views | boolean | – | When true, imports view configurations defined in the template. |
| internal_dependencies | boolean | – | When true, imports internal task dependency relationships from the template. |
| name | string | yes | The display name to assign to the newly created Folder. |
| old_assignees | boolean | – | When true, imports assignee assignments from template tasks. |
| old_checklists | boolean | – | When true, imports checklist items from template tasks. |
| old_due_date | boolean | – | When true, imports the original due dates from template tasks. |
| old_followers | boolean | – | When true, imports the watcher (follower) assignments from template tasks. |
| old_start_date | boolean | – | When true, imports the original start dates from template tasks. |
| old_status | boolean | – | When true, imports the current status values of tasks from the template. |
| old_statuses | boolean | – | When true, imports the status configuration (status types and workflow) from the template. |
| old_subtask_assignees | boolean | – | When true, imports both subtask structures and their assignee assignments together from the template. |
| old_tags | boolean | – | When true, imports tags assigned to tasks in the template. |
| priority | boolean | – | When true, imports priority levels assigned to tasks in the template. |
| recur_settings | boolean | – | When true, imports recurring task settings from the template. |
| relationships | boolean | – | When true, imports task relationship links (e.g., linked tasks) from the template. |
| remap_start_date | boolean | – | When true, recalculates and remaps task start dates relative to the provided project start or due date. |
| return_immediately | boolean | – | When true, returns the new Folder ID immediately after access checks without waiting for all nested assets to finish being created. When false, the request waits until the Folder and all its contents… |
| skip_weekends | boolean | – | When true, excludes Saturday and Sunday when calculating remapped task dates. |
| space_id | string | yes | The unique identifier of the Space where the new Folder will be created. |
| start_date | string | – | The project start date used as the anchor point for remapping task dates from the template. Must be provided in ISO 8601 date-time format. |
| subtasks | boolean | – | When true, imports subtask structures from the template tasks. |
| template_id | string | yes | The unique identifier of the Folder template to apply, always prefixed with `t-`. Retrieve available template IDs using the Get Folder Templates endpoint. |
| time_estimate | boolean | – | When true, imports time estimate data (hours, minutes, and seconds) from the template tasks. |
No output schema declared.
No examples provided.
create_folder_view Create Folder View ~928
Create a new view (List, Board, Calendar, Table, Timeline, Workload, Activity, Map, Chat, or Gantt) inside a specified Folder, with full control over grouping, sorting, filtering, and display settings.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_comments | boolean | yes | When true, the view displays tasks that have comments assigned to users. |
| assignees | array | yes | An array of assignee user IDs used to filter tasks shown in the view to only those assigned to the specified users. |
| collapse_empty_columns | string | – | Controls whether empty columns are collapsed in the view. Provide the desired collapse behavior as a string value. |
| columnsFields | array | yes | An array of column field objects controlling which columns are visible in the view. Custom Fields must use the cf_ prefix and be formatted as a JSON object with the Custom Field ID. |
| divideCollapsed | array | yes | An array of divide group identifiers that should appear collapsed by default. Order is not significant; each item represents a divide group to collapse. |
| divideDir | null | – | Sort direction for the divide field. Set to null to disable divide sorting. |
| divideField | null | – | The field used to divide tasks within the view. Set to null to disable division. |
| filtersFields | array | yes | An array of filter field objects that restrict which tasks appear in the view. Refer to the ClickUp filter-views documentation for the full list of supported field identifiers. |
| folder_id | number | yes | The unique numeric identifier of the folder where the new view will be created. |
| groupingCollapsed | array | yes | An array of group identifiers that should appear collapsed by default in the view. Order is not significant; each item represents a group to collapse. |
| groupingDir | integer | yes | Sort direction for the grouping field. Use 1 for ascending order (e.g., urgent priority at top) or -1 for descending order (e.g., no priority at top). |
| groupingField | string | yes | The field by which tasks in the view are grouped. Accepted values are none, status, priority, assignee, tag, or dueDate. |
| ignore | boolean | yes | When true, certain default behaviors or notifications for this view are ignored. Consult ClickUp documentation for the specific behavior this flag suppresses. |
| me_checklists | boolean | yes | When true, the view is filtered to show only tasks with checklists belonging to the currently authenticated user. |
| me_comments | boolean | yes | When true, the view is filtered to show only tasks that have comments from the currently authenticated user. |
| me_subtasks | boolean | yes | When true, the view is filtered to show only subtasks assigned to or created by the currently authenticated user. |
| name | string | yes | The display name for the new view. |
| op | string | yes | Logical operator applied to combine multiple filter conditions. Use AND to require all filters to match, or OR to require at least one filter to match. |
| search | string | yes | A search string used to filter tasks displayed in the view by matching against task names or content. |
| show_assignees | boolean | yes | When true, assignee avatars or names are shown on task cards within the view. |
| show_closed | boolean | yes | When true, closed tasks are included in the view alongside open tasks. |
| show_closed_subtasks | boolean | yes | When true, closed subtasks are included in the view. |
| show_images | boolean | yes | When true, image attachments are displayed inline on task cards within the view. |
| show_subtask_parent_names | boolean | yes | When true, the parent task name is displayed alongside each subtask in the view for additional context. |
| show_subtasks | integer | yes | Controls how subtasks are displayed. Use 1 to show subtasks separately, 2 to show them expanded inline, or 3 to show them collapsed inline. |
| show_task_locations | boolean | yes | When true, the location (Space, Folder, List) of each task is shown within the view. |
| sortingFields | array | yes | An ordered array of field objects defining the sort sequence applied to tasks in the view. Supports the same fields available when filtering a view; earlier entries in the array take sort precedence. |
| type | string | yes | The view type to create. Must be one of the supported layout types: list, board, calendar, table, timeline, workload, activity, map, conversation, or gantt. |
| unassigned_tasks | boolean | yes | When true, tasks with no assignee are included in the view. |
No output schema declared.
No examples provided.
create_folderless_list Create Folderless List ~259
Creates a new List directly within a Space, without placing it inside a Folder. Use this when you want a top-level List organization within the Space.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | integer | – | The user ID of the member to assign as the owner of this List. |
| due_date | integer | – | The due date for the List, expressed as a Unix timestamp in milliseconds. |
| due_date_time | boolean | – | When set to true, the due date includes a specific time component; when false, only the date is considered. |
| markdown_content | string | – | Description body for the List, formatted in Markdown. Use this field instead of `content` when rich text formatting is needed. |
| name | string | yes | The display name for the new List. |
| priority | integer | – | The priority level for the List, represented as an integer (e.g., 1 = Urgent, 2 = High, 3 = Normal, 4 = Low). |
| space_id | number | yes | The unique identifier of the Space in which the new List will be created. |
| status | string | – | Sets the color of the List, which is referred to as its status. This is distinct from the task-level statuses available within the List. |
No output schema declared.
No examples provided.
create_goal Create Goal ~191
Creates a new Goal within a specified Workspace, allowing you to define objectives with ownership, due dates, and visual categorization.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | yes | A color used to visually identify the Goal in the UI, specified as a hex color code. |
| description | string | yes | A detailed description providing context or additional information about the Goal. |
| due_date | integer | yes | The deadline for the Goal expressed as a Unix timestamp in milliseconds. |
| multiple_owners | boolean | yes | Set to true to allow multiple users to own this Goal simultaneously, or false to restrict to a single owner. |
| name | string | yes | The display name of the Goal. |
| owners | array | yes | List of user IDs assigned as owners of the Goal. Order is not significant; each item should be a valid integer user ID. |
| team_id | number | yes | The unique identifier of the Workspace where the Goal will be created. |
No output schema declared.
No examples provided.
create_key_result Create Key Result ~327
Create a new key result (target) within a specified goal to define measurable outcomes. Supports multiple target types including numeric, currency, boolean, percentage, and automatic tracking.
| Name | Type | Req | Description |
|---|---|---|---|
| goal_id | string | yes | The unique identifier of the goal to which this key result will be added. |
| list_ids | array | yes | An array of List IDs to link with this key result, allowing progress to be tracked automatically based on list task completion. Order is not significant. |
| name | string | yes | The display name of the key result that describes the measurable target. |
| owners | array | yes | An array of user IDs representing the owners responsible for this key result. Order is not significant. |
| steps_end | integer | yes | The ending value of the target range, representing the goal completion threshold. |
| steps_start | integer | yes | The starting value of the target range, representing the baseline or initial progress point. |
| task_ids | array | yes | An array of task IDs to link with this key result, allowing progress to be tracked automatically based on task completion. Order is not significant. |
| type | string | yes | The measurement type for this key result. Valid values are: `number` (numeric count), `currency` (monetary value), `boolean` (true/false completion), `percentage` (0–100 scale), or `automatic` (deriv… |
| unit | string | yes | The unit label associated with the key result value (e.g., a currency code or custom unit name), applicable when the type is `number` or `currency`. |
No output schema declared.
No examples provided.
create_list Create List ~252
Creates a new List inside a specified Folder, allowing you to organize tasks with optional metadata such as due dates, priority, assignee, and a color status.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | integer | – | The user ID of the member to assign as the owner of this List. |
| due_date | integer | – | The due date for the List, expressed as a Unix timestamp in milliseconds. |
| due_date_time | boolean | – | When set to true, the due date includes a specific time component; when false, only the date is considered. |
| folder_id | number | yes | The unique identifier of the Folder in which the new List will be created. |
| markdown_content | string | – | Optional description for the List, formatted using Markdown. Use this field instead of a plain-text content field to apply rich formatting. |
| name | string | yes | The display name for the new List. |
| priority | integer | – | The priority level for the List, represented as an integer (e.g., 1 = urgent, 2 = high, 3 = normal, 4 = low). |
| status | string | – | The color status of the List, which represents a visual label rather than task-level statuses defined within the List. |
No output schema declared.
No examples provided.
create_list_from_template Create List from Template ~785
Create a new List within a Space using an existing List template, importing selected task properties such as assignees, due dates, custom fields, and more. Supports both synchronous and asynchronous creation via the `return_immediately` parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | integer | – | Controls inclusion of archived tasks: use 1 to include archived tasks, 2 to include only archived tasks, or omit for no archived tasks. |
| attachments | boolean | – | Whether to import file attachments from the template's tasks. |
| automation | boolean | – | Whether to import automation rules defined in the template. |
| comment | boolean | – | Whether to import comments from the template's tasks. |
| comment_attachments | boolean | – | Whether to import comment attachments from the template's tasks. |
| content | string | – | Optional description or body text for the new List. |
| custom_fields | boolean | – | Whether to import Custom Field definitions and values from the template's tasks. |
| custom_type | boolean | – | Whether to import custom task type definitions from the template's tasks. |
| due_date | string | – | The project due date used as the anchor point when remapping task dates, provided in ISO 8601 date-time format. |
| external_dependencies | boolean | – | Whether to import external task dependencies from the template's tasks. |
| include_views | boolean | – | Whether to import views configured in the template. |
| internal_dependencies | boolean | – | Whether to import internal task dependencies from the template's tasks. |
| name | string | yes | The display name to assign to the newly created List. |
| old_assignees | boolean | – | Whether to import assignees from the template's tasks. |
| old_checklists | boolean | – | Whether to import checklists from the template's tasks. |
| old_due_date | boolean | – | Whether to import due dates from the template's tasks. |
| old_followers | boolean | – | Whether to import watchers (followers) from the template's tasks. |
| old_start_date | boolean | – | Whether to import start dates from the template's tasks. |
| old_status | boolean | – | Whether to import the current status values of the template's tasks. |
| old_statuses | boolean | – | Whether to import status configuration settings from the template's tasks. |
| old_subtask_assignees | boolean | – | Whether to import assignees on subtasks from the template's tasks. |
| old_tags | boolean | – | Whether to import tags from the template's tasks. |
| priority | boolean | – | Whether to import priority settings from the template's tasks. |
| recur_settings | boolean | – | Whether to import recurring task settings from the template's tasks. |
| relationships | boolean | – | Whether to import task relationship links from the template's tasks. |
| remap_start_date | boolean | – | Whether to remap task start dates relative to the new project start date. |
| return_immediately | boolean | – | When true, returns the new object ID immediately after access checks without waiting for all nested assets to finish being created. When false, the request waits until the List and all its contents a… |
| skip_weekends | boolean | – | Whether to skip weekend days when calculating remapped task dates. |
| space_id | string | yes | The unique identifier of the Space where the new List will be created. |
| start_date | string | – | The project start date used as the anchor point when remapping task dates, provided in ISO 8601 date-time format. |
| subtasks | boolean | – | Whether to import subtasks from the template's tasks. |
| template_id | string | yes | The unique identifier of the List template to apply, always prefixed with `t-`. Retrieve available template IDs using the Get List Templates endpoint. |
| time_estimate | number | – | Whether to import time estimate values (hours, minutes, and seconds) from the template's tasks. |
No output schema declared.
No examples provided.
create_list_from_template_in_folder Create List from Template in Folder ~852
Create a new List inside a specified Folder using an existing List template, optionally controlling which task properties (assignees, due dates, custom fields, etc.) are imported from the template. By default the request returns immediately with the future List ID, though the List and its nested objects may still be generating in the background.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | integer | – | Controls inclusion of archived tasks from the template: 1 includes archived tasks, 2 excludes them. Omit to use the default behavior. |
| attachments | boolean | – | Whether to import file attachments from the template's tasks. |
| automation | boolean | – | Whether to import automation rules defined in the template. |
| comment | boolean | – | Whether to import comments from the template's tasks. |
| comment_attachments | boolean | – | Whether to import file attachments that are embedded in task comments from the template. |
| content | string | – | Optional description or body text for the new List. |
| custom_fields | boolean | – | Whether to import Custom Field definitions and values from the template's tasks. |
| custom_type | boolean | – | Whether to import custom task type definitions from the template's tasks. |
| due_date | string | – | The project due date used as the anchor when remapping task dates from the template. Must be an ISO 8601 date-time string. |
| external_dependencies | boolean | – | Whether to import external dependency links from the template's tasks. |
| folder_id | string | yes | The ID of the Folder in which the new List will be created. |
| include_views | boolean | – | Whether to import view configurations (e.g., Board, Calendar) from the template. |
| internal_dependencies | boolean | – | Whether to import internal dependency links between tasks from the template. |
| name | string | yes | The display name to assign to the newly created List. |
| old_assignees | boolean | – | Whether to import assignee assignments from the template's tasks. |
| old_checklists | boolean | – | Whether to import checklist items from the template's tasks. |
| old_due_date | boolean | – | Whether to import the original due dates from the template's tasks. |
| old_followers | boolean | – | Whether to import the watcher (follower) assignments from the template's tasks. |
| old_start_date | boolean | – | Whether to import the original start dates from the template's tasks. |
| old_status | boolean | – | Whether to import the current status values set on the template's tasks. |
| old_statuses | boolean | – | Whether to import the status configuration (status columns/workflow) from the template. |
| old_subtask_assignees | boolean | – | Whether to import assignees on subtasks from the template's tasks. |
| old_tags | boolean | – | Whether to import tags from the template's tasks. |
| priority | boolean | – | Whether to import priority levels from the template's tasks. |
| recur_settings | boolean | – | Whether to import recurring task settings from the template's tasks. |
| relationships | boolean | – | Whether to import task relationship links (e.g., blocked by, related to) from the template. |
| remap_start_date | boolean | – | Whether to remap task start dates relative to the new project start date provided in 'start_date'. |
| return_immediately | boolean | – | When true (default), the new List's ID is returned immediately before all nested template objects are fully created. When false, the request waits until the List and all sub-objects are fully applied… |
| skip_weekends | boolean | – | Whether to skip weekend days (Saturday and Sunday) when calculating remapped task dates. |
| start_date | string | – | The project start date used as the anchor when remapping task dates from the template. Must be an ISO 8601 date-time string. |
| subtasks | boolean | – | Whether to import subtasks from the template's tasks. |
| template_id | string | yes | The ID of the List template to apply. Template IDs include a 't-' prefix. Retrieve available template IDs using the Get List Templates endpoint. |
| time_estimate | number | – | Whether to import time estimate values (hours, minutes, and seconds) from the template's tasks. |
No output schema declared.
No examples provided.
create_list_view Create List View ~837
Create a new view (List, Board, Calendar, Table, Timeline, Workload, Activity, Map, Chat, or Gantt) within a specified List, configuring grouping, sorting, filtering, and display options.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_comments | boolean | yes | When true, the view displays comments that have been assigned to users. |
| assignees | array | yes | An array of assignee identifiers used to filter the view to tasks assigned to specific users. |
| collapse_empty_columns | string | – | Controls whether empty columns are collapsed in the view, reducing visual clutter. |
| columnsFields | array | yes | An array of column field definitions to display in the view. Custom Fields must use the 'cf_' prefix and be formatted as a JSON object with the Custom Field ID. |
| divideCollapsed | array | yes | An array of divide-group identifiers that should be rendered in a collapsed state by default in the view. |
| divideDir | null | – | The sort direction for the divide field. Set to null to disable. |
| divideField | null | – | The field used to divide tasks within the view. Set to null to disable division. |
| filtersFields | array | yes | An array of filter field definitions to apply to the view, limiting which tasks are displayed. Refer to the filter-views documentation for available fields. |
| groupingCollapsed | array | yes | An array of group identifiers that should be rendered in a collapsed state by default in the view. |
| groupingDir | integer | yes | The sort direction for groups. Use 1 for ascending order (e.g., urgent priority at top) or -1 for descending order (e.g., no priority at top). |
| groupingField | string | yes | The field by which tasks in the view are grouped. Use 'none' to disable grouping. |
| ignore | boolean | yes | When true, certain default behaviors or inherited settings are ignored when creating the view. |
| list_id | number | yes | The unique identifier of the List in which to create the new view. |
| me_checklists | boolean | yes | When true, the view is filtered to show only tasks that have checklist items assigned to the current user. |
| me_comments | boolean | yes | When true, the view is filtered to show only tasks that have comments from the current user. |
| me_subtasks | boolean | yes | When true, the view is filtered to show only tasks that have subtasks assigned to or created by the current user. |
| name | string | yes | The display name for the new view. |
| op | string | yes | The logical operator used to combine multiple filter conditions. Use 'AND' to require all conditions, or 'OR' to require any condition. |
| search | string | yes | A search string used to filter tasks displayed in the view by matching text content. |
| show_assignees | boolean | yes | When true, assignee avatars or names are shown on task cards or rows within the view. |
| show_closed | boolean | yes | When true, closed tasks are included in the view alongside open tasks. |
| show_closed_subtasks | boolean | yes | When true, closed subtasks are included in the view. |
| show_images | boolean | yes | When true, image attachments are previewed directly on task cards or rows within the view. |
| show_subtask_parent_names | boolean | yes | When true, the parent task name is displayed alongside each subtask in the view. |
| show_subtasks | integer | yes | Controls how subtasks are displayed. Use 1 to show subtasks separately, 2 to show them expanded inline, or 3 to show them collapsed inline. |
| show_task_locations | boolean | yes | When true, the location (Space, Folder, List) of each task is shown within the view. |
| sortingFields | array | yes | An ordered array of field definitions specifying which fields to sort by and in what direction. Supports the same fields available when filtering a view. |
| type | string | yes | The view type to create. Determines the visual layout and available features for the view. |
| unassigned_tasks | boolean | yes | When true, tasks with no assignee are included in the view. |
No output schema declared.
No examples provided.
create_space Create Space ~364
Creates a new Space within a specified Workspace, allowing configuration of its name, assignee settings, and feature toggles such as due dates, time tracking, tags, and dependencies.
| Name | Type | Req | Description |
|---|---|---|---|
| checklistsEnabled | boolean | yes | Whether checklists are enabled for tasks in this Space. |
| custom_fieldsEnabled | boolean | yes | Whether custom fields are enabled for tasks in this Space. |
| dependency_warningEnabled | boolean | yes | Whether a warning is shown when a task has unresolved dependencies in this Space. |
| due_datesEnabled | boolean | yes | Whether the due dates feature is enabled for tasks in this Space. |
| multiple_assignees | boolean | yes | Whether tasks in this Space can be assigned to more than one user simultaneously. |
| name | string | yes | The display name for the new Space. |
| portfoliosEnabled | boolean | yes | Whether the Portfolios feature is enabled for this Space. |
| remap_closed_due_date | boolean | yes | Whether due dates on closed tasks are remapped when rescheduling dependent tasks in this Space. |
| remap_dependenciesEnabled | boolean | yes | Whether dependency dates are automatically remapped when a dependent task's date changes in this Space. |
| remap_due_dates | boolean | yes | Whether due dates are automatically remapped for dependent tasks when a parent task's due date changes. |
| start_date | boolean | yes | Whether start dates are enabled for tasks in this Space. |
| tagsEnabled | boolean | yes | Whether tags are enabled for tasks in this Space. |
| team_id | number | yes | The unique identifier of the Workspace (team) in which the new Space will be created. |
| time_estimatesEnabled | boolean | yes | Whether time estimates are enabled for tasks in this Space. |
| time_trackingEnabled | boolean | yes | Whether time tracking is enabled for tasks in this Space. |
No output schema declared.
No examples provided.
create_space_tag Create Space Tag ~118
Creates a new tag in the specified Space, allowing tasks within that Space to be categorized and labeled with custom colors.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The display name of the tag as it will appear throughout the Space. |
| space_id | number | yes | The unique identifier of the Space where the new tag will be created. |
| tag_bg | string | yes | The background color of the tag, specified as a hex color code. |
| tag_fg | string | yes | The foreground (text) color of the tag, specified as a hex color code. |
No output schema declared.
No examples provided.
create_space_view Create Space View ~843
Create a new view (List, Board, Calendar, Table, Timeline, Workload, Activity, Map, Chat, or Gantt) within a specified Space, with full control over grouping, sorting, filtering, and display settings.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_comments | boolean | yes | When true, the view displays tasks that have comments assigned to specific users. |
| assignees | array | yes | An array of assignee identifiers used to filter tasks shown in the view to only those assigned to the specified users. |
| collapse_empty_columns | string | – | Controls whether empty columns are collapsed in applicable view types such as Board. |
| columnsFields | array | yes | An array of column field objects controlling which columns are visible in the view. Custom Fields must use the 'cf_' prefix and be formatted as a JSON object with the Custom Field ID. |
| divideCollapsed | array | yes | An array of division identifiers that should be rendered in a collapsed state by default in this view. |
| divideDir | null | – | Sort direction for divided groups. Set to null to disable. |
| divideField | null | – | The field used to divide tasks within groups. Set to null to disable division. |
| filtersFields | array | yes | An array of filter field objects that restrict which tasks appear in the view. Refer to the filter-views documentation for the full list of supported fields. |
| groupingCollapsed | array | yes | An array of group identifiers that should be rendered in a collapsed state by default in this view. |
| groupingDir | integer | yes | Sort direction for groups. Use 1 for ascending order (e.g., urgent priority at top) or -1 for descending order (e.g., no priority at top). |
| groupingField | string | yes | The field by which tasks in the view are grouped. Use 'none' to disable grouping. |
| ignore | boolean | yes | When true, certain default behaviors or validations are bypassed during view creation. |
| me_checklists | boolean | yes | When true, the view is filtered to show only tasks that have checklist items assigned to the currently authenticated user. |
| me_comments | boolean | yes | When true, the view is filtered to show only tasks that have comments from the currently authenticated user. |
| me_subtasks | boolean | yes | When true, the view is filtered to show only tasks that have subtasks assigned to the currently authenticated user. |
| name | string | yes | The display name for the new view. |
| op | string | yes | Logical operator applied to combine multiple filter conditions. Use 'AND' to require all conditions, or 'OR' to require any one condition. |
| search | string | yes | A search string used to filter tasks displayed in the view by matching text content. |
| show_assignees | boolean | yes | When true, assignee avatars or names are displayed on task cards within the view. |
| show_closed | boolean | yes | When true, closed tasks are included in the view alongside open tasks. |
| show_closed_subtasks | boolean | yes | When true, closed subtasks are included in the view. |
| show_images | boolean | yes | When true, image attachments are previewed directly on task cards within the view. |
| show_subtask_parent_names | boolean | yes | When true, the parent task name is shown alongside each subtask in the view for additional context. |
| show_subtasks | integer | yes | Controls how subtasks are displayed. Use 1 to show subtasks separately, 2 to show them expanded inline, or 3 to show them collapsed inline. |
| show_task_locations | boolean | yes | When true, the location (List, Folder, Space) of each task is displayed within the view. |
| sortingFields | array | yes | An ordered array of field objects specifying the sort criteria for tasks in the view. Supports the same fields available when filtering a view. |
| space_id | number | yes | The unique identifier of the Space where the new view will be created. |
| type | string | yes | The view type to create. Determines the layout and interaction model for tasks in this view. |
| unassigned_tasks | boolean | yes | When true, tasks with no assignee are included in the view. |
No output schema declared.
No examples provided.
create_task Create Task ~613
Creates a new task in the specified list, supporting full configuration including assignees, scheduling, custom fields, subtask relationships, and sprint points.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | Whether the task should be created in an archived state. |
| assignees | array | – | List of user IDs to assign to the task. Order is not significant. |
| check_required_custom_fields | boolean | – | When true, enforces validation of any required Custom Fields on the task; by default required Custom Fields are ignored during API task creation. |
| custom_fields | array | – | List of Custom Field objects to populate on the new task, each specifying a field ID and its value. Object and array type fields can be cleared by passing a null value. |
| custom_item_id | number | – | The custom task type ID to apply to this task. Omit or pass null to create a standard task; retrieve available custom type IDs using the Get Custom Task Types endpoint. |
| due_date | integer | – | The due date for the task as a Unix timestamp in milliseconds. |
| due_date_time | boolean | – | Set to true to include a specific time component with the due date, or false to treat it as a date-only value. |
| group_assignees | array | – | List of user group IDs to assign to the task. Order is not significant. |
| links_to | string | – | The ID of an existing task to create a linked dependency relationship with the new task. |
| list_id | number | yes | The unique numeric ID of the list in which the task will be created. |
| markdown_content | string | – | Markdown-formatted description for the task. Takes precedence over the plain-text description field if both are provided. |
| name | string | yes | The display name of the task. |
| notify_all | boolean | – | When true, the task creator is also notified upon creation; all other assignees and watchers are always notified regardless of this setting. |
| parent | string | – | The ID of an existing task to nest this new task under as a subtask. The parent task must reside in the same list specified in the path and may itself be a subtask. |
| points | number | – | The number of sprint points to assign to the task. |
| priority | integer | – | The priority level for the task, where 1 is urgent, 2 is high, 3 is normal, and 4 is low. |
| start_date | integer | – | The start date for the task as a Unix timestamp in milliseconds. |
| start_date_time | boolean | – | Set to true to include a specific time component with the start date, or false to treat it as a date-only value. |
| status | string | – | The status to assign to the task. Must match an existing status name defined in the list. |
| tags | array | – | List of tag names to apply to the task. Order is not significant. |
| time_estimate | integer | – | The estimated time to complete the task, expressed in milliseconds. |
No output schema declared.
No examples provided.
create_task_from_template Create Task From Template ~109
Create a new task in a specified list using a pre-defined task template from your workspace. Publicly shared templates must be added to your workspace library before they can be used via the API.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | number | yes | The unique numeric identifier of the list where the new task will be created. |
| name | string | yes | The display name to assign to the newly created task. |
| template_id | string | yes | The unique string identifier of the task template to use when creating the task. |
No output schema declared.
No examples provided.
create_time_entry Create Time Entry ~370
Creates a time entry for a user in the specified workspace, supporting both completed entries (with start and stop/duration) and actively running timers. A negative duration indicates a timer is currently running for that user.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | integer | – | The user ID to assign the time entry to. Workspace owners and admins may specify any user ID; members may only specify their own user ID. |
| billable | boolean | – | Marks the time entry as billable when set to true. |
| custom_task_ids | boolean | – | Set to true to reference the associated task by its custom task ID instead of its standard ClickUp task ID. |
| description | string | – | An optional text description or note to associate with the time entry. |
| duration | integer | yes | The duration of the time entry in milliseconds. Used as an alternative to the stop parameter; ignored when both start and stop values are present. A negative value indicates a currently running timer. |
| start | integer | yes | The start time of the time entry as a Unix timestamp in milliseconds. |
| stop | integer | – | The end time of the time entry as a Unix timestamp in milliseconds. Can be used instead of the duration parameter; if both stop and start are provided, duration is ignored. |
| tags | array | – | A list of time tracking label objects to attach to the entry. Available to users on the Business Plan and above; each item should represent a valid time tracking tag. |
| team_Id | number | yes | The unique identifier of the workspace where the time entry will be created. |
| team_id | number | – | The workspace ID required when using custom task IDs. Must be provided alongside custom_task_ids=true to correctly resolve the custom task reference. |
| tid | string | – | The ID of the task to associate with this time entry. |
No output schema declared.
No examples provided.
create_user_group Create User Group ~170
Creates a User Group within a Workspace to organize and manage users collectively. Note that adding a guest with view-only permissions automatically converts them to a paid guest, which may incur prorated charges if additional seats are needed.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | – | An optional short identifier or alias for the User Group, typically used as a reference handle within the Workspace. |
| members | array | yes | A list of user objects to include as members of the new User Group; order is not significant and each item should represent a user to be added. |
| name | string | yes | The display name for the new User Group, used to identify it within the Workspace. |
| team_id | number | yes | The unique identifier of the Workspace (referred to as team_id in the API) where the User Group will be created. |
No output schema declared.
No examples provided.
create_workspace_view Create Workspace View ~877
Create a new view at the Everything (Workspace) level, supporting view types such as List, Board, Calendar, Table, Timeline, Workload, Activity, Map, Chat, or Gantt. Configure grouping, sorting, filtering, and display settings for the view.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_comments | boolean | yes | When true, the view displays comments that are assigned to users. |
| assignees | array | yes | An array of assignee identifiers used to filter tasks shown in the view to only those assigned to the specified users. |
| collapse_empty_columns | string | – | Controls whether empty columns are collapsed in the view. Applicable primarily to Board-type views. |
| columnsFields | array | yes | An array of column field objects controlling which columns are visible in the view. Custom Fields must use the 'cf_' prefix and be formatted as a JSON object with the Custom Field ID. |
| divideCollapsed | array | yes | An array of division identifiers that should be rendered in a collapsed state by default. Order is not significant; each item is a division identifier string. |
| divideDir | null | – | The sort direction for divided groups. Set to null to disable. |
| divideField | null | – | The field used to divide tasks within groups. Set to null to disable division. |
| filtersFields | array | yes | An array of filter field objects defining which fields and conditions are used to filter tasks displayed in the view. Refer to the filter-views documentation for available fields. |
| groupingCollapsed | array | yes | An array of group identifiers that should be rendered in a collapsed state by default. Order is not significant; each item is a group identifier string. |
| groupingDir | integer | yes | The sort direction for groups. Use 1 for ascending order (e.g., urgent priority at top) or -1 for descending order (e.g., no priority at top). |
| groupingField | string | yes | The field by which tasks in the view are grouped. Use 'none' to disable grouping. |
| ignore | boolean | yes | When true, certain default behaviors or validations are bypassed during view creation. |
| me_checklists | boolean | yes | When true, the view is filtered to show only checklists assigned to or created by the current user. |
| me_comments | boolean | yes | When true, the view is filtered to show only comments that mention or are assigned to the current user. |
| me_subtasks | boolean | yes | When true, the view is filtered to show only subtasks assigned to or created by the current user. |
| name | string | yes | The display name for the new view. |
| op | string | yes | The logical operator used to combine multiple filter conditions. Use 'AND' to require all conditions to match, or 'OR' to require any condition to match. |
| search | string | yes | A search string used to filter tasks displayed in the view by matching task names or content. |
| show_assignees | boolean | yes | When true, assignee avatars or names are displayed on task cards or rows within the view. |
| show_closed | boolean | yes | When true, closed tasks are included in the view alongside open tasks. |
| show_closed_subtasks | boolean | yes | When true, closed subtasks are included in the view. |
| show_images | boolean | yes | When true, image attachments are displayed as previews on task cards or rows within the view. |
| show_subtask_parent_names | boolean | yes | When true, the parent task name is shown alongside each subtask in the view. |
| show_subtasks | integer | yes | Controls how subtasks are displayed. Use 1 to show subtasks separately, 2 to show them expanded inline, or 3 to show them collapsed inline. |
| show_task_locations | boolean | yes | When true, the location (List, Folder, Space) of each task is displayed within the view. |
| sortingFields | array | yes | An ordered array of field objects specifying the sort fields and their directions. Supports the same fields available when filtering a view. |
| team_id | number | yes | The unique identifier of the Workspace in which to create the view. |
| type | string | yes | The view type to create. Determines the visual layout and available features for the view. |
| unassigned_tasks | boolean | yes | When true, tasks with no assignee are included in the view. |
No output schema declared.
No examples provided.
delete_checklist Delete Checklist ~51
Permanently deletes a checklist from a task. This action is irreversible and removes the checklist along with all its items.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist_id | string | yes | The unique identifier (UUID) of the checklist to delete. |
No output schema declared.
No examples provided.
delete_checklist_item Delete Checklist Item ~84
Permanently removes a specific line item from a task checklist. This action cannot be undone and will delete the item and its associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist_id | string | yes | The unique identifier (UUID) of the checklist from which the item will be deleted. |
| checklist_item_id | string | yes | The unique identifier (UUID) of the specific checklist item to be deleted. |
No output schema declared.
No examples provided.
delete_comment Delete Comment ~49
Permanently deletes a specific task comment by its unique identifier. This action is irreversible and removes the comment from the task.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | number | yes | The unique numeric identifier of the comment to delete. |
No output schema declared.
No examples provided.
delete_folder Delete Folder ~52
Permanently deletes a folder from your Workspace. This action cannot be undone, so ensure the correct folder ID is specified before proceeding.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | number | yes | The unique numeric identifier of the folder to be deleted. |
No output schema declared.
No examples provided.
delete_goal Delete Goal ~76
Permanently removes a specified Goal from your Workspace. This action is irreversible and will delete all associated goal data.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request body, used to indicate the format of the data being sent. |
| goal_id | string | yes | The unique identifier (UUID) of the Goal to be deleted. |
No output schema declared.
No examples provided.
delete_key_result Delete Key Result ~58
Permanently deletes a key result (target) from a Goal. This action is irreversible and removes the specified key result and its associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| key_result_id | string | yes | The unique identifier (UUID) of the key result to delete. |
No output schema declared.
No examples provided.
delete_list Delete List ~76
Permanently deletes a specified List from your Workspace. This action is irreversible and removes the List along with its associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request body, used to indicate the format of the data being sent. |
| list_id | number | yes | The unique numeric identifier of the List to be deleted. |
No output schema declared.
No examples provided.
delete_space Delete Space ~49
Permanently deletes a Space from your Workspace. This action is irreversible and removes the Space along with its associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| space_id | number | yes | The unique numeric identifier of the Space to be deleted. |
No output schema declared.
No examples provided.
delete_space_tag Delete Space Tag ~150
Permanently removes a task tag from a specified Space. The tag will no longer be available for tasks within that Space.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The display name of the tag being deleted, used to identify the tag in the request body. |
| space_id | number | yes | The unique numeric identifier of the Space from which the tag will be deleted. |
| tag_bg | string | yes | The background color of the tag, specified as a hex color code. |
| tag_fg | string | yes | The foreground (text) color of the tag, specified as a hex color code. |
| tag_name | string | yes | The URL path identifier of the tag to delete, typically matching the tag's display name. |
No output schema declared.
No examples provided.
What is the com.mcparmory/clickup MCP server?
com.mcparmory/clickup is an MCP server listed in the public MCP registry as com.mcparmory/clickup. Manage tasks, lists, checklists, comments, and project workflows. This page covers its container image (ghcr.io/mcparmory/clickup:1.0.4).
Is the com.mcparmory/clickup MCP server safe to use?
com.mcparmory/clickup scores 48 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/clickup MCP server expose?
com.mcparmory/clickup exposes 134 tools: upload_task_attachment, get_current_user, list_workspaces, create_checklist, update_checklist, and 129 more. Their descriptions and schemas cost roughly 25,980 tokens of context every time the server is loaded.
Is the com.mcparmory/clickup MCP server still maintained?
com.mcparmory/clickup is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.