com.mcparmory/clickup
PYPI · MCPARMORY-CLICKUP · 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 Security37
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
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: the license (MIT License) isn't a recognized OSI-approved license. 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 Management87
- Stability observed for 26 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 current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/clickup MCP server?
com.mcparmory/clickup runs locally as a PyPI package, launched with uvx mcparmory-clickup. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-clickup
claude mcp add com-mcparmory-clickup -- uvx mcparmory-clickup
{
"mcpServers": {
"com-mcparmory-clickup": {
"command": "uvx",
"args": [
"mcparmory-clickup"
]
}
}
} {
"servers": {
"com-mcparmory-clickup": {
"command": "uvx",
"args": [
"mcparmory-clickup"
]
}
}
} codex mcp add com-mcparmory-clickup -- uvx mcparmory-clickup
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-clickup": {
"type": "local",
"command": [
"uvx",
"mcparmory-clickup"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-clickup --command uvx --arg mcparmory-clickup
mcp_servers:
com-mcparmory-clickup:
command: "uvx"
args: ["mcparmory-clickup"] {
"McpServers": {
"com-mcparmory-clickup": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-clickup"
]
}
}
} assistant mcp add com-mcparmory-clickup -t stdio -c uvx -a mcparmory-clickup
{
"mcpServers": {
"com-mcparmory-clickup": {
"command": "uvx",
"args": [
"mcparmory-clickup"
]
}
}
} 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.
- 20 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.
- 19 Sept 26 −3
- Stability: pass → 0.83 functional
- 18 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 17 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 −14
- Malware scan: pass → unverified ▼ security
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 pypi/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 | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 46 packages
| Packages resolved | 46 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
list_tasks List Tasks ~765
Retrieve up to 100 tasks per page from a specified List, returning only tasks whose home List matches the given list_id by default. Use filtering, sorting, and pagination parameters to narrow results by status, assignee, tags, dates, custom fields, and more.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | When true, includes archived tasks in the response. Archived tasks are excluded by default. |
| assignees | array | – | Array of assignee user IDs to filter tasks by. Only tasks assigned to at least one of the specified users are returned. |
| custom_field | array | – | Array representing a single Custom Field filter, used when filtering tasks by exactly one Custom Field or Custom Relationship. Use custom_fields when filtering across multiple Custom Fields at once. |
| custom_fields | array | – | Array of Custom Field filter objects for filtering tasks across multiple Custom Fields simultaneously. Each object must specify a field_id, an operator, and a value. Use custom_field instead when fil… |
| custom_items | array | – | Array of custom task type identifiers to filter by. Use 0 for standard tasks, 1 for Milestones, or any other workspace-defined custom task type ID. |
| date_created_gt | integer | – | Returns only tasks created strictly after this Unix timestamp in milliseconds. |
| date_created_lt | integer | – | Returns only tasks created strictly before this Unix timestamp in milliseconds. |
| date_done_gt | integer | – | Returns only tasks marked done strictly after this Unix timestamp in milliseconds. |
| date_done_lt | integer | – | Returns only tasks marked done strictly before this Unix timestamp in milliseconds. |
| date_updated_gt | integer | – | Returns only tasks last updated strictly after this Unix timestamp in milliseconds. |
| date_updated_lt | integer | – | Returns only tasks last updated strictly before this Unix timestamp in milliseconds. |
| due_date_gt | integer | – | Returns only tasks with a due date strictly after this Unix timestamp in milliseconds. |
| due_date_lt | integer | – | Returns only tasks with a due date strictly before this Unix timestamp in milliseconds. |
| include_closed | boolean | – | When true, closed tasks are included in the response. Closed tasks are excluded by default. |
| include_markdown_description | boolean | – | When true, task descriptions are returned in Markdown format instead of plain text. |
| include_timl | boolean | – | When true, tasks that belong to multiple Lists (Tasks in Multiple Lists) are included in the response, even if their home List differs from the specified list_id. Excluded by default. |
| list_id | number | yes | The unique numeric ID of the List whose tasks you want to retrieve. To find it, hover over the List in the Sidebar, click the ellipsis menu, select Copy link, and extract the number following '/li' i… |
| order_by | string | – | Field by which to sort the returned tasks. Defaults to 'created' if not specified. |
| page | integer | – | Zero-based page number for paginated results. Increment to retrieve subsequent pages of up to 100 tasks each. |
| reverse | boolean | – | When true, reverses the sort order of the returned tasks. |
| statuses | array | – | Array of status names to filter tasks by. Only tasks matching one of the provided statuses are returned. To include closed tasks, also set include_closed to true. |
| subtasks | boolean | – | When true, subtasks are included in the response alongside top-level tasks. Subtasks are excluded by default. |
| tags | array | – | Array of tag names to filter tasks by. Only tasks that have at least one of the specified tags are returned. |
| watchers | array | – | Array of watcher user IDs to filter tasks by. Only tasks watched by at least one of the specified users are returned. |
No output schema declared.
No examples provided.
list_tasks_by_team List Tasks by Team ~879
Retrieve tasks from a Workspace that match specified filter criteria such as status, assignee, due date, tags, and location (Space, Folder, or List). Results are paginated at 100 tasks per page and limited to tasks the authenticated user can access.
| Name | Type | Req | Description |
|---|---|---|---|
| assignees | array | – | Array of ClickUp user IDs used to filter tasks by assignee. Multiple assignee IDs can be provided to match tasks assigned to any of the specified users. |
| custom_fields_field_ids | array | – | List of Custom Field IDs to filter by (one per filter entry). |
| custom_fields_operators | array | – | List of operators for each Custom Field filter (e.g. '=', '<', '>', '!='). Must match length of custom_fields_field_ids. |
| custom_fields_values | array | – | List of values for each Custom Field filter. Must match length of custom_fields_field_ids. |
| custom_items | array | – | Array of custom task type identifiers used to filter results. Use `0` for standard tasks, `1` for Milestones, or any other numeric ID corresponding to a custom task type defined in the Workspace. |
| date_created_gt | integer | – | Returns only tasks created strictly after this value, expressed as a Unix timestamp in milliseconds. |
| date_created_lt | integer | – | Returns only tasks created strictly before this value, expressed as a Unix timestamp in milliseconds. |
| date_done_gt | integer | – | Returns only tasks marked as done strictly after this value, expressed as a Unix timestamp in milliseconds. |
| date_done_lt | integer | – | Returns only tasks marked as done strictly before this value, expressed as a Unix timestamp in milliseconds. |
| date_updated_gt | integer | – | Returns only tasks last updated strictly after this value, expressed as a Unix timestamp in milliseconds. |
| date_updated_lt | integer | – | Returns only tasks last updated strictly before this value, expressed as a Unix timestamp in milliseconds. |
| due_date_gt | integer | – | Returns only tasks with a due date strictly after this value, expressed as a Unix timestamp in milliseconds. |
| due_date_lt | integer | – | Returns only tasks with a due date strictly before this value, expressed as a Unix timestamp in milliseconds. |
| include_closed | boolean | – | When set to true, includes closed tasks in the response alongside open tasks. Closed tasks are excluded by default. |
| include_markdown_description | boolean | – | When set to true, task description fields in the response are returned in Markdown format instead of plain text. |
| list_ids | array | – | Array of List IDs used to filter tasks to only those belonging to the specified Lists. Multiple values are supported. |
| order_by | string | – | Field by which to sort the returned tasks. Defaults to `created` if not specified. Accepted values are `id`, `created`, `updated`, and `due_date`. |
| page | integer | – | Zero-based page number for paginated results; begin with 0 for the first page and increment to retrieve subsequent pages. |
| parent | string | – | The ID of a parent task; when provided, the response returns the subtasks belonging to that parent task rather than top-level tasks. |
| project_ids | array | – | Array of Folder IDs (referred to as `project_ids` in the API) used to filter tasks to only those within the specified Folders. Multiple values are supported. |
| reverse | boolean | – | When set to true, reverses the sort order of the results so that the most recent or highest-value items appear first. |
| space_ids | array | – | Array of Space IDs used to filter tasks to only those belonging to the specified Spaces. Multiple values are supported. |
| statuses | array | – | Array of status names used to filter tasks by their current status. Use URL encoding for status names that contain spaces (e.g., a space character is represented as `%20`). |
| subtasks | boolean | – | When set to true, includes subtasks in the response. Subtasks are excluded by default. |
| tags | array | – | Array of tag names used to filter tasks that have all specified tags applied. Use URL encoding for tag names containing spaces (e.g., a space character is represented as `%20`). |
| team_Id | number | yes | The unique numeric ID of the Workspace (team) from which to retrieve tasks. |
No output schema declared.
No examples provided.
list_templates List Templates ~118
Retrieves all List templates available in a Workspace, returning their IDs and metadata. Use the returned template IDs (prefixed with `t-`) to create Lists from templates in a Folder or Space.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | MIME type for the request body, indicating the format of the data being sent. |
| page | integer | yes | Zero-indexed page number for paginating through template results; start at 0 for the first page. |
| team_id | number | yes | The unique identifier of the Workspace whose List templates you want to retrieve. |
No output schema declared.
No examples provided.
list_time_entries List Time Entries Within Date Range ~619
Retrieve time entries for a workspace filtered by a date range, location, assignee, and billing status. Defaults to the last 30 days for the authenticated user; only one location filter (space, folder, list, or task) may be applied at a time.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request payload, which must be set to indicate JSON content. |
| assignee | number | – | Filter results to one or more specific users by their user IDs, supplied as a comma-separated list. Only Workspace Owners and Admins may retrieve entries for users other than themselves. |
| custom_task_ids | boolean | – | Set to true to reference the target task using its custom task ID instead of its standard ClickUp task ID. Must be used together with the team_id parameter. |
| end_date | number | – | The end of the date range filter expressed as a Unix timestamp in milliseconds. Defaults to the current time if omitted. |
| folder_id | number | – | Restricts results to time entries linked to tasks within the specified Folder. Cannot be combined with space_id, list_id, or task_id. |
| include_approval_details | boolean | – | When set to true, includes current approval details for each time entry such as the approver ID, approval timestamp, list of approvers, and current approval status. |
| include_approval_history | boolean | – | When set to true, includes the full approval history for each time entry, including status changes, reviewer notes, and approver details. |
| include_location_names | boolean | – | When set to true, enriches each time entry with the human-readable names of its associated List, Folder, and Space alongside their respective IDs. |
| include_task_tags | boolean | – | When set to true, includes any tags associated with the task linked to each time entry in the response. |
| is_billable | boolean | – | Filters results by billing status: set to true to return only billable time entries, or false to return only non-billable time entries. Omit to return all entries regardless of billing status. |
| list_id | number | – | Restricts results to time entries linked to tasks within the specified List. Cannot be combined with space_id, folder_id, or task_id. |
| space_id | number | – | Restricts results to time entries linked to tasks within the specified Space. Cannot be combined with folder_id, list_id, or task_id. |
| start_date | number | – | The beginning of the date range filter expressed as a Unix timestamp in milliseconds. Defaults to 30 days before the current time if omitted. |
| task_id | string | – | Restricts results to time entries linked to a single specific task. Cannot be combined with space_id, folder_id, or list_id. |
| team_Id | number | yes | The unique identifier of the workspace from which to retrieve time entries. |
| team_id | number | – | The workspace ID required when custom_task_ids is set to true, used to resolve the custom task ID to the correct task within the workspace. |
No output schema declared.
No examples provided.
list_time_entry_tags List Time Entry Tags ~91
Retrieves all labels (tags) that have been applied to time entries within a specified Workspace. Useful for auditing or filtering time entry categorization across a team.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request payload, indicating the format in which data is being sent to the server. |
| team_id | number | yes | The unique identifier of the Workspace whose time entry tags you want to retrieve. |
No output schema declared.
No examples provided.
list_user_groups List User Groups ~121
Retrieves User Groups within a specified Workspace, optionally filtered to one or more specific groups. Note: in the API, 'team_id' refers to the Workspace ID and 'group_id' refers to a User Group ID.
| Name | Type | Req | Description |
|---|---|---|---|
| group_ids | array | – | An optional list of User Group IDs to filter results to specific groups; omit to return all User Groups in the Workspace. Each item should be a valid User Group ID string. Order is not significant. |
| team_id | number | yes | The unique ID of the Workspace whose User Groups you want to retrieve. |
No output schema declared.
No examples provided.
list_view_tasks List View Tasks ~72
Retrieve all visible tasks within a specific ClickUp view, returned in paginated results.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | yes | The zero-based page number to retrieve for paginated results, where 0 returns the first page. |
| view_id | string | yes | The unique identifier of the view whose tasks you want to retrieve. |
No output schema declared.
No examples provided.
list_views List Views ~51
Retrieves all task and page views available for a specified List. Returns standard views and required views as separate response groups.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | number | yes | The unique identifier of the List whose views you want to retrieve. |
No output schema declared.
No examples provided.
list_webhooks List Webhooks ~54
Retrieves all webhooks created via the API for a specified Workspace. Only webhooks created by the authenticated user are returned.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | number | yes | The unique identifier of the Workspace whose webhooks you want to retrieve. |
No output schema declared.
No examples provided.
list_workspace_custom_fields List Workspace Custom Fields ~95
Retrieves all Custom Fields created at the Workspace level for a specific Workspace. Note that Custom Fields created at the Space, Folder, or List level are not included in the results.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request payload, indicating the format of the request body sent to the API. |
| team_id | number | yes | The unique identifier of the Workspace whose Workspace-level Custom Fields you want to retrieve. |
No output schema declared.
No examples provided.
list_workspace_views List Workspace Views ~59
Retrieves all task and page views available at the Everything level of a Workspace, providing a top-level overview of all views across the entire Workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | number | yes | The unique identifier of the Workspace whose Everything-level views you want to retrieve. |
No output schema declared.
No examples provided.
list_workspaces List Workspaces ~33
Retrieves all workspaces accessible to the currently authenticated user. Use this to discover available workspaces before performing workspace-specific operations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
merge_tasks Merge Tasks ~125
Merges one or more source tasks into a specified target task, consolidating their content and history. Source tasks are provided in the request body, and Custom Task IDs are not supported.
| Name | Type | Req | Description |
|---|---|---|---|
| source_task_ids | array | yes | An array of IDs representing the source tasks to merge into the target task. Order is not significant; all listed tasks will be merged. Custom Task IDs are not supported. |
| task_id | string | yes | The unique ID of the target task that all source tasks will be merged into. Must be a valid internal task ID; Custom Task IDs are not supported. |
No output schema declared.
No examples provided.
remove_folder_guest Remove Folder Guest ~120
Revoke a guest's access to a specific Folder, removing their ability to view or interact with its contents. This endpoint is only available on the Enterprise Plan.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | number | yes | The unique numeric identifier of the Folder from which the guest's access will be revoked. |
| guest_id | number | yes | The unique numeric identifier of the guest whose access to the Folder will be removed. |
| include_shared | boolean | – | When set to false, the response excludes details of items shared with the guest; defaults to true to include shared item details. |
No output schema declared.
No examples provided.
remove_list_guest Remove List Guest ~121
Revokes a guest's access to a specific List, removing their ability to view or interact with it. 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 whose access to the List will be removed. |
| include_shared | boolean | – | Controls whether the response includes details of items 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 from which the guest's access will be revoked. |
No output schema declared.
No examples provided.
remove_tags_from_time_entries Remove Tags from Time Entries ~123
Remove one or more tags from specified time entries in a workspace. This disassociates the labels from the time entries without deleting the tags from the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| tags | array | yes | List of tag objects to remove from the specified time entries. Order is not significant; each item should represent a valid tag associated with the workspace. |
| team_id | number | yes | The unique identifier of the workspace containing the time entries. |
| time_entry_ids | array | yes | List of time entry IDs from which the specified tags will be removed. Order is not significant. |
No output schema declared.
No examples provided.
remove_task_from_list Remove Task from List ~102
Removes a task from an additional (non-home) List it has been added to. Requires the Tasks in Multiple Lists ClickApp to be enabled; a task cannot be removed from its original home List.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | number | yes | The unique numeric identifier of the List from which the task should be removed. Must not be the task's home List. |
| task_id | string | yes | The unique string identifier of the task to remove from the specified List. |
No output schema declared.
No examples provided.
remove_task_guest Remove Task Guest ~180
Revoke a guest's access to a specific task, removing their ability to view or interact with it. This endpoint is only available on the Enterprise Plan.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_task_ids | boolean | – | Set to true to reference the task by its custom task ID instead of the standard ClickUp task ID. |
| guest_id | number | yes | The numeric identifier of the guest user whose access to the task will be removed. |
| include_shared | boolean | – | Controls whether the response includes details of other items shared with the guest. Set to false to exclude shared item details; defaults to true. |
| task_id | string | yes | The unique identifier of the task from which the guest's access will be revoked. |
| 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.
remove_task_tag Remove Task Tag ~189
Removes a specific tag from a task without deleting the tag from the Space. The tag remains available for use on other tasks within the Space.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request body, indicating the format of the payload being sent. |
| custom_task_ids | boolean | – | Set to true if referencing the task by its custom task ID instead of the default ClickUp task ID. Must be used in conjunction with the team_id parameter. |
| tag_name | string | yes | The name of the tag to remove from the task. Must match the tag name exactly as it exists in the Space. |
| task_id | string | yes | The unique identifier of the task from which the tag will be removed. |
| team_id | number | – | The Workspace ID (team) required when custom_task_ids is set to true. Used to resolve the correct task when referencing by custom task ID. |
No output schema declared.
No examples provided.
remove_workspace_guest Remove Workspace Guest ~76
Revokes a guest's access to the specified Workspace, removing all associated permissions. This endpoint is only available on the Enterprise Plan.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_id | number | yes | The unique identifier of the guest whose Workspace access will be revoked. |
| team_id | number | yes | The unique identifier of the Workspace from which the guest will be removed. |
No output schema declared.
No examples provided.
remove_workspace_user Remove Workspace User ~86
Deactivates and removes a user from the specified Workspace, revoking their access. This endpoint is exclusively available to Workspaces on the Enterprise Plan.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | number | yes | The unique identifier of the Workspace (team) from which the user will be removed. |
| user_id | number | yes | The unique identifier of the user to be deactivated and removed from the Workspace. |
No output schema declared.
No examples provided.
rename_folder Rename Folder ~60
Renames an existing folder by updating its display name. The folder's contents and structure remain unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | number | yes | The unique numeric identifier of the folder to rename. |
| name | string | yes | The new name to assign to the folder. |
No output schema declared.
No examples provided.
rename_time_entry_tag Rename Time Entry Tag ~150
Rename an existing time entry tag within a workspace, updating its display name and color styling. All time entries using the old tag name will reflect the updated tag.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The current name of the tag to be renamed. |
| new_name | string | yes | The new name to assign to the tag, replacing the current name across all associated time entries. |
| tag_bg | string | yes | The background color for the tag, specified as a hex color code. |
| tag_fg | string | yes | The foreground (text) color for the tag, specified as a hex color code. |
| team_id | number | yes | The unique identifier of the workspace containing the time entry tags to update. |
No output schema declared.
No examples provided.
reply_to_comment Reply to Comment ~142
Create a threaded reply to an existing comment on a task. Supports assigning the reply to a user or group and controlling notification behavior.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | integer | – | The user ID of the individual to assign this comment to. |
| comment_id | number | yes | The unique identifier of the parent comment to reply to. |
| comment_text | string | yes | The text content of the threaded reply comment. |
| group_assignee | string | – | The identifier of the group to assign this comment to. |
| notify_all | boolean | yes | When true, the original comment creator is also notified of this reply. Assignees and task watchers are always notified regardless of this setting. |
No output schema declared.
No examples provided.
set_task_custom_field_value Set Task Custom Field Value ~232
Set or update the value of a specific Custom Field on a task. Requires the task ID and the UUID of the Custom Field to update.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | The request body containing the value to set for the Custom Field. The shape of the value varies by field type — supported types include URLs, UUIDs, email addresses, phone numbers, dates (millisecon… |
| custom_task_ids | boolean | – | Set to true if you are referencing the task by its Custom Task ID instead of the standard task ID. |
| field_id | string | yes | The universally unique identifier (UUID) of the Custom Field you want to set. Retrieve this from the Get Accessible Custom Fields or Get Task endpoints. |
| task_id | string | yes | The unique identifier of the task you want to update with a Custom Field value. |
| team_id | number | – | The Workspace ID required when referencing a task by its Custom Task ID. Must be provided alongside custom_task_ids=true. |
No output schema declared.
No examples provided.
start_time_entry Start Time Entry ~178
Starts a running timer for the authenticated user within the specified workspace. Optionally associates the entry with a task, tags, and billable status.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | Indicates whether the time being tracked should be marked as billable. |
| custom_task_ids | boolean | – | Set to true if the task is being referenced by its custom task ID rather than its default system-generated ID. |
| description | string | – | A brief label or note describing what the time entry is tracking. |
| tags | array | – | A list of time tracking label objects to associate with this entry; available to Business Plan users and above. Order is not significant. |
| team_Id | number | yes | The unique identifier of the workspace in which to start the time entry. |
| tid | string | – | The ID of the task to associate with this time entry. |
No output schema declared.
No examples provided.
stop_time_entry Stop Time Entry ~88
Stops the currently running timer for the authenticated user in the specified workspace. Only one active timer can be running at a time, and this operation halts it immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request body, which must be set to indicate JSON formatting. |
| team_id | number | yes | The unique identifier of the workspace in which to stop the active time entry. |
No output schema declared.
No examples provided.
track_task_time Track Task Time ~176
Records a time entry against a specific task using the legacy time tracking endpoint. For new integrations, the dedicated Time Tracking API endpoints are recommended instead.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_task_ids | boolean | – | Set to true if referencing the task by its custom task ID rather than the default system-generated ID. |
| end | integer | yes | The end time of the tracked time entry as a Unix timestamp in milliseconds. Must be greater than the start value. |
| start | integer | yes | The start time of the tracked time entry as a Unix timestamp in milliseconds. |
| task_id | string | yes | The unique identifier of the task to log time against. |
| team_id | number | – | The Workspace ID required when using custom task IDs. Must be provided alongside custom_task_ids=true. |
| time | integer | yes | The total duration of the time entry in milliseconds. |
No output schema declared.
No examples provided.
update_checklist Update Checklist ~102
Rename a checklist or change its display order relative to other checklists on a task. Provide a new name, a new position, or both.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist_id | string | yes | The unique identifier (UUID) of the checklist to update. |
| name | string | – | The new display name for the checklist. |
| position | integer | – | The zero-based display order of the checklist among all checklists on the task, where 0 places it at the top. |
No output schema declared.
No examples provided.
update_checklist_item Update Checklist Item ~179
Update an individual item within a task checklist, allowing you to rename it, reassign it, mark it as resolved or unresolved, or nest it under another checklist item as a child.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | The user ID of the team member to assign to this checklist item. |
| checklist_id | string | yes | The unique identifier of the checklist that contains the item to be updated. |
| checklist_item_id | string | yes | The unique identifier of the specific checklist item to update. |
| name | string | – | The updated display name or label for the checklist item. |
| parent | string | – | The checklist item ID of the parent item under which this item should be nested, enabling hierarchical checklist structures. |
| resolved | boolean | – | Whether the checklist item is marked as completed; set to true to resolve it or false to reopen it. |
No output schema declared.
No examples provided.
update_comment Update Comment ~149
Update an existing task comment by modifying its text, assigning it to a user or group, or marking it as resolved. All core fields must be provided in the request.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | integer | yes | The user ID of the individual to assign the comment to. |
| comment_id | number | yes | The unique identifier of the comment to update. |
| comment_text | string | yes | The updated text content to replace the existing comment body. |
| group_assignee | integer | – | The group ID to assign the comment to, used when assigning to a team or group rather than an individual. |
| resolved | boolean | yes | Set to true to mark the comment as resolved, or false to mark it as unresolved. |
No output schema declared.
No examples provided.
update_goal Update Goal ~228
Update an existing Goal's properties, including its name, due date, description, color, and ownership. Use this to rename a Goal, adjust its deadline, modify its description, or add and remove assigned owners.
| Name | Type | Req | Description |
|---|---|---|---|
| add_owners | array | yes | List of user IDs to add as owners of the Goal. Order is not significant; each item should be a valid user ID integer. |
| color | string | yes | The color to assign to the Goal, used for visual categorization in the UI. Provide a valid hex color code. |
| description | string | yes | The full replacement description for the Goal. This overwrites the existing description entirely. |
| due_date | integer | yes | The due date for the Goal, represented as a Unix timestamp in milliseconds. |
| goal_id | string | yes | The unique identifier (UUID) of the Goal to update. |
| name | string | yes | The new display name for the Goal. |
| rem_owners | array | yes | List of user IDs to remove as owners of the Goal. Order is not significant; each item should be a valid user ID integer. |
No output schema declared.
No examples provided.
update_key_result Update Key Result ~106
Update the progress and notes for an existing key result. Use this to record current step completion and add contextual notes to track advancement toward a goal.
| Name | Type | Req | Description |
|---|---|---|---|
| key_result_id | string | yes | The unique identifier of the key result to update. |
| note | string | yes | A note or comment describing the current status, blockers, or context for this progress update. |
| steps_current | integer | yes | The current number of steps completed toward the key result target. Should reflect the latest progress value. |
No output schema declared.
No examples provided.
update_list Update List ~297
Update a List's properties including its name, description, priority, assignee, due date, and color. Use this to rename a List or modify any of its metadata fields.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | The user ID of the member to assign as the List's default assignee. |
| due | string | – | Due date in ISO 8601 format. Include time (e.g. '2024-06-15T14:30:00') to set due_date_time=true, or date only (e.g. '2024-06-15') for due_date_time=false. |
| list_id | string | yes | The unique identifier of the List to update. |
| markdown_content | string | – | The List's description body formatted in Markdown. Use this field instead of `content` to apply rich text formatting. |
| name | string | yes | The new display name for the 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 applied to the List, referred to as its status. This controls the List's color indicator, not the task statuses within the List. |
| unset_status | boolean | – | When set to true, removes the currently applied color from the List. Defaults to false, which preserves the existing color. |
No output schema declared.
No examples provided.
update_space Update Space ~498
Update a Space's settings including its name, color, privacy, and enabled ClickApps such as due dates, time tracking, tags, and custom fields.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_can_manage | boolean | yes | Whether workspace admins are permitted to manage this private Space. Enabling or restricting this setting is an Enterprise Plan feature. |
| checklistsEnabled | boolean | yes | Whether the Checklists ClickApp is enabled for this Space, allowing checklist items to be added to tasks. |
| color | string | yes | The color associated with the Space, used for visual identification in the UI. |
| custom_fieldsEnabled | boolean | yes | Whether the Custom Fields ClickApp is enabled for this Space, allowing custom data fields to be defined on tasks. |
| dependency_warningEnabled | boolean | yes | Whether a warning is shown when a task with unresolved dependencies is marked complete. |
| due_datesEnabled | boolean | yes | Whether the Due Dates ClickApp is enabled for this Space, allowing tasks to have due date fields. |
| multiple_assignees | boolean | yes | Whether tasks in this Space can be assigned to multiple members simultaneously. |
| name | string | yes | The new display name for the Space. |
| portfoliosEnabled | boolean | yes | Whether the Portfolios ClickApp is enabled for this Space, allowing tasks and lists to be tracked in portfolio views. |
| private | boolean | yes | Whether the Space is private; private Spaces are only visible to invited members. |
| remap_closed_due_date | boolean | yes | Whether due dates on closed dependent tasks are also remapped when a predecessor task's due date changes. |
| remap_dependenciesEnabled | boolean | yes | Whether dependency remapping is enabled, automatically adjusting dependent task dates when a predecessor's dates change. |
| remap_due_dates | boolean | yes | Whether due dates on dependent tasks are automatically remapped when a predecessor task's due date changes. |
| space_id | number | yes | The unique identifier of the Space to update. |
| start_date | boolean | yes | Whether tasks in this Space support a start date field in addition to a due date. |
| tagsEnabled | boolean | yes | Whether the Tags ClickApp is enabled for this Space, allowing tasks to be labeled with tags. |
| time_estimatesEnabled | boolean | yes | Whether the Time Estimates ClickApp is enabled for this Space, allowing estimated time to be set on tasks. |
| time_trackingEnabled | boolean | yes | Whether the Time Tracking ClickApp is enabled for this Space, allowing members to log time on tasks. |
No output schema declared.
No examples provided.
update_space_tag Update Space Tag ~149
Updates the name and color properties of an existing tag within a specified space. Use this to rename a tag or change its foreground and background display colors.
| Name | Type | Req | Description |
|---|---|---|---|
| bg_color | string | yes | The background color for the tag, typically provided as a hex color code. |
| fg_color | string | yes | The foreground (text) color for the tag, typically provided as a hex color code. |
| name | string | yes | The new display name to assign to the tag. |
| space_id | number | yes | The unique identifier of the space that contains the tag to be updated. |
| tag_name | string | yes | The current name of the tag to be edited, used to identify the tag within the space. |
No output schema declared.
No examples provided.
update_task Update Task ~566
Update one or more fields on an existing task by its task ID. Supports updating metadata, assignments, dates, status, priority, and more.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | Set to true to archive the task, or false to unarchive it. |
| assigneesAdd | array | yes | List of user IDs to add as assignees to the task. Order is not significant. |
| assigneesRem | array | yes | List of user IDs to remove from the task's assignees. Order is not significant. |
| custom_item_id | number | – | The custom task type ID to assign to this task. Set to null to use the default 'Task' type. Retrieve available custom task 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 if the due date includes a specific time component, or false if it is a date-only value. |
| group_assigneesAdd | array | – | List of group (team) IDs to add as group assignees to the task. Order is not significant. |
| group_assigneesRem | array | – | List of group (team) IDs to remove from the task's group assignees. Order is not significant. |
| markdown_content | string | – | Markdown-formatted description for the task. Takes precedence over the plain-text description field if both are provided. |
| name | string | – | The display name of the task. |
| parent | string | – | The task ID of the parent task to move this subtask under. Cannot be used to convert a subtask back into a top-level task by passing null. |
| points | number | – | The number of Sprint Points to assign to this task. |
| priority | integer | – | The priority level of 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 if the start date includes a specific time component, or false if it is a date-only value. |
| status | string | – | The status of the task. Must match a valid status name defined in the task's list. |
| task_id | string | yes | The unique identifier of the task to update. |
| time_estimate | integer | – | The estimated time to complete the task, in milliseconds. |
| watchersAdd | array | yes | List of user IDs to add as watchers on the task. Order is not significant. |
| watchersRem | array | yes | List of user IDs to remove from the task's watchers. Order is not significant. |
No output schema declared.
No examples provided.
update_time_entry Update Time Entry ~319
Update the details of an existing time entry in a workspace, including its description, tags, start/end times, duration, and billable status.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | Indicates whether the time entry should be marked as billable. |
| custom_task_ids | boolean | – | Set to true to reference the associated task by its custom task ID instead of its default ClickUp task ID. |
| description | string | – | A text description or note to associate with the time entry. |
| duration | integer | – | The duration of the time entry in milliseconds. Use this to set a fixed duration rather than deriving it from start and end times. |
| end | integer | – | The end time of the time entry as a Unix timestamp in milliseconds. Must be provided together with the start parameter. |
| start | integer | – | The start time of the time entry as a Unix timestamp in milliseconds. Must be provided together with the end parameter. |
| tag_action | string | – | Specifies how the provided tags should be applied — for example, whether to replace existing tags or add to them. |
| tags | array | yes | A list of time tracking label objects to apply to the time entry. Available on Business Plan and above. Order is not significant; each item should be a valid tag object. |
| team_id | number | yes | The unique identifier of the workspace containing the time entry. |
| tid | string | yes | The unique identifier of the task to associate with this time entry. |
| timer_id | number | yes | The unique identifier of the time entry to update. |
No output schema declared.
No examples provided.
update_time_entry_legacy Update Time Entry ~207
Updates an existing tracked time interval on a task by modifying its start time, end time, or duration. Note: This is a legacy endpoint; the Time Tracking API is recommended for managing time entries.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_task_ids | boolean | – | Set to true to reference the task by its custom task ID instead of its default system ID. |
| end | integer | yes | The end time of the tracked interval as a Unix timestamp in milliseconds. Must be greater than the start value. |
| interval_id | string | yes | The unique identifier of the specific time interval to edit. |
| start | integer | yes | The start time of the tracked interval as a Unix timestamp in milliseconds. |
| task_id | string | yes | The unique identifier of the task containing the time interval to update. |
| team_id | number | – | The Workspace ID required when using custom task IDs. Must be provided alongside custom_task_ids=true. |
| time | integer | yes | The total duration of the tracked time interval in milliseconds. |
No output schema declared.
No examples provided.
update_user_group Update User Group ~155
Updates a User Group's name, handle, or membership within a Workspace. Note that adding a guest with view-only permissions automatically converts them to a paid guest, which may incur prorated billing charges.
| Name | Type | Req | Description |
|---|---|---|---|
| add | array | yes | List of user IDs to add to the User Group. Each item should be a valid user ID string. |
| group_id | string | yes | The unique identifier of the User Group to update. |
| handle | string | – | The new handle (short identifier or alias) for the User Group. |
| name | string | – | The new display name for the User Group. |
| rem | array | yes | List of user IDs to remove from the User Group. Each item should be a valid user ID string. |
No output schema declared.
No examples provided.
update_view Update View ~912
Update an existing view by renaming it or modifying its grouping, sorting, filters, columns, and display settings. Supports all view types within a Workspace, Space, Folder, or List.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_comments | boolean | yes | When true, the view displays only tasks that have comments assigned to a user. |
| 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. Applicable primarily to Board views. |
| columnsFields | array | yes | An array of column field objects defining which columns are visible in the view. Custom Fields must use the cf_ prefix and be formatted as a JSON object with the field's UUID. |
| divideCollapsed | array | yes | An array of divide group identifiers that should be rendered in a collapsed state within 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 objects applied to the view to restrict which tasks are displayed. 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 within the view. |
| groupingDir | integer | yes | The sort direction for grouping. 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. |
| id | string | yes | The unique identifier of the Workspace, Space, Folder, or List that contains this view. |
| ignore | boolean | yes | When true, ignores the default view settings and applies only the explicitly provided configuration. |
| me_checklists | boolean | yes | When true, the view filters to show only tasks that have checklist items assigned to the currently authenticated user. |
| me_comments | boolean | yes | When true, the view filters to show only tasks that have comments from the currently authenticated user. |
| me_subtasks | boolean | yes | When true, the view filters to show only tasks that have subtasks assigned to the currently authenticated user. |
| name | string | yes | The new display name for the 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 at least one condition to match. |
| parentType | integer | yes | The hierarchy level of the parent location where the view resides. Use 7 for Workspace, 4 for Space, 5 for Folder, or 6 for List. |
| search | string | yes | A text search string used to filter tasks displayed in the view by keyword. |
| 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. |
| 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 displayed within the view. |
| sortingFields | array | yes | An ordered array of field objects defining the sort criteria for the view. Each item specifies a field and sort direction; refer to the filter-views documentation for supported field names. |
| type | string | yes | The type of view being updated (e.g., list, board, calendar). |
| unassigned_tasks | boolean | yes | When true, tasks with no assignee are included in the view. |
| view_id | string | yes | The unique identifier of the view to update. |
No output schema declared.
No examples provided.
update_workspace_guest Update Workspace Guest ~214
Update permission settings and role assignment for a guest on a Workspace. This endpoint is only available on the Enterprise Plan.
| Name | Type | Req | Description |
|---|---|---|---|
| can_create_views | boolean | – | Whether the guest is allowed to create new views within the Workspace. |
| can_edit_tags | boolean | – | Whether the guest is allowed to create, edit, and delete tags. |
| can_see_points_estimated | boolean | – | Whether the guest is allowed to view point estimations on tasks. |
| can_see_time_estimated | boolean | – | Whether the guest is allowed to view time estimations on tasks. |
| can_see_time_spent | boolean | – | Whether the guest is allowed to view time tracked (spent) on tasks. |
| custom_role_id | integer | – | The ID of a custom role to assign to the guest, controlling their permission level within the Workspace. |
| guest_id | number | yes | The unique identifier of the guest whose settings are being updated. |
| team_id | number | yes | The unique identifier of the Workspace where the guest resides. |
No output schema declared.
No examples provided.
update_workspace_user Update Workspace User ~163
Update a workspace user's display name, admin status, and custom role assignment. This endpoint is exclusively available to Workspaces on the Enterprise Plan.
| Name | Type | Req | Description |
|---|---|---|---|
| admin | boolean | yes | Whether the user should be granted admin-level privileges in the Workspace. Set to true to grant admin access, false to revoke it. |
| custom_role_id | integer | yes | The identifier of the custom role to assign to the user, as defined in the Workspace's Enterprise role configuration. |
| team_id | number | yes | The unique identifier of the Workspace (team) in which the user will be updated. |
| user_id | number | yes | The unique identifier of the user to be updated within the specified Workspace. |
| username | string | yes | The new display name to assign to the user within the Workspace. |
No output schema declared.
No examples provided.
upload_task_attachment Upload Task Attachment ~164
Upload a local file to a task as an attachment using multipart/form-data. Note that cloud-hosted files are not supported; only locally accessible files can be attached.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment | array | – | Base64-encoded file content for upload. The file content to upload as a multipart/form-data attachment. Each item represents a part of the multipart payload for the file being attached. |
| custom_task_ids | boolean | – | Set to true to reference the task by its custom task ID instead of the default system-generated task ID. |
| task_id | string | yes | The unique identifier of the task to which the file will be attached. |
| team_id | number | – | The Workspace ID required when referencing a task by its custom task ID. Must be provided alongside custom_task_ids=true. |
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 PyPI package (mcparmory-clickup).
Is the com.mcparmory/clickup MCP server safe to use?
com.mcparmory/clickup scores 60 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.