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 →
delete_task Delete Task ~158
Permanently deletes a task from your Workspace by its task ID. This action is irreversible and removes the task and its associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request body, which must be set to indicate JSON-formatted content. |
| custom_task_ids | boolean | – | Set to true to reference the task using its custom task ID rather than the default system-generated task ID. |
| task_id | string | yes | The unique identifier of the task to delete. Use the task's custom ID instead if the custom_task_ids parameter is set to true. |
| team_id | number | – | The Workspace ID (team 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.
delete_task_dependency Delete Task Dependency ~197
Remove a dependency relationship between two tasks, unlinking them so that one no longer depends on the other. Both the target task and the related dependent or prerequisite task must be specified.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_task_ids | boolean | – | Set to true to reference tasks by their custom task IDs instead of their system-generated IDs. Requires the team_id parameter to also be provided. |
| dependency_of | string | yes | The ID of the task that depends on the primary task — i.e., the downstream task to be unlinked. |
| depends_on | string | yes | The ID of the task that the primary task depends on — i.e., the prerequisite task to be unlinked. |
| task_id | string | yes | The unique identifier of the primary task whose dependency relationship is being removed. |
| team_id | number | – | The Workspace ID (team) required when using custom task IDs. Must be provided alongside custom_task_ids=true to correctly resolve custom task references. |
No output schema declared.
No examples provided.
delete_task_link Delete Task Link ~149
Removes the dependency or relationship link between two tasks. Both task IDs must be provided to identify the specific link to delete.
| 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 the team_id parameter to also be provided. |
| links_to | string | yes | The unique identifier of the target task that is currently linked to the source task. |
| task_id | string | yes | The unique identifier of the source task from which the link will be removed. |
| team_id | number | – | The Workspace ID required when using custom task IDs. Must be provided alongside custom_task_ids=true to correctly resolve tasks within the specified Workspace. |
No output schema declared.
No examples provided.
delete_time_entry Delete Time Entry ~123
Permanently deletes one or more time entries from a specified Workspace. Multiple time entries can be removed in a single request by providing a comma-separated list of timer IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request body, indicating the format in which the data is being sent. |
| team_id | number | yes | The unique identifier of the Workspace from which the time entries will be deleted. |
| timer_id | number | yes | The unique identifier of the time entry to delete. To delete multiple entries at once, provide a comma-separated list of timer IDs. |
No output schema declared.
No examples provided.
delete_tracked_time_interval Delete Tracked Time Interval ~168
Deletes a specific tracked time interval from a task using its interval ID. Note: This is a legacy endpoint; the Time Tracking API is recommended for managing time entries.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The MIME type of the request body, indicating the format of the data being sent. |
| custom_task_ids | boolean | – | Set to true to reference the task by its custom task ID instead of the default ClickUp task ID. |
| interval_id | string | yes | The unique identifier of the tracked time interval to delete. |
| task_id | string | yes | The unique identifier of the task from which the tracked time interval will be deleted. |
| 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.
delete_user_group Delete User Group ~65
Permanently removes a user group from the Workspace. Note that in the API, 'group_id' refers to a user group, while 'team_id' refers to the Workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | The unique identifier of the user group to delete from the Workspace. |
No output schema declared.
No examples provided.
delete_view Delete View ~51
Permanently deletes a specified view by its unique identifier. This action is irreversible and removes the view and its configuration from the system.
| Name | Type | Req | Description |
|---|---|---|---|
| view_id | string | yes | The unique identifier of the view to be deleted. |
No output schema declared.
No examples provided.
delete_webhook Delete Webhook ~51
Permanently deletes a webhook, stopping all event monitoring and location tracking associated with it. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | The unique identifier (UUID) of the webhook to delete. |
No output schema declared.
No examples provided.
get_bulk_tasks_time_in_status Get Bulk Tasks Time in Status ~148
Retrieves how long two or more tasks have spent in each status. Requires the Total Time in Status ClickApp to be enabled by a Workspace owner or admin.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request payload sent to the API. |
| custom_task_ids | boolean | – | Set to true if referencing tasks by their custom task IDs instead of default system IDs. |
| task_ids | string | yes | One or more task IDs to query; include this parameter once per task ID, with a maximum of 100 task IDs per request. |
| team_id | number | – | The Workspace ID required when custom_task_ids is set to true; must be provided alongside that parameter. |
No output schema declared.
No examples provided.
get_current_user Get Current User ~38
Retrieves the profile and account details of the currently authenticated ClickUp user. Useful for confirming identity, retrieving user ID, and accessing account-level information.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_folder Get Folder ~48
Retrieves a folder and the Lists contained within it. Use this to inspect the structure and contents of a specific folder.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | number | yes | The unique numeric identifier of the folder to retrieve. |
No output schema declared.
No examples provided.
get_goal Get Goal ~57
Retrieves the full details of a specific goal, including its associated targets and current progress. Use this to inspect a goal's configuration and status by its unique identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| goal_id | string | yes | The unique UUID identifier of the goal to retrieve. |
No output schema declared.
No examples provided.
get_guest Get Guest ~64
Retrieves detailed information about a specific guest user within a Workspace. Available exclusively on the Enterprise Plan.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_id | number | yes | The unique identifier of the guest user to retrieve. |
| team_id | number | yes | The unique identifier of the Workspace (team) containing the guest. |
No output schema declared.
No examples provided.
get_list Get List ~84
Retrieves detailed information about a specific List, including its settings, members, and configuration. Use this to inspect or reference a List's properties by its unique ID.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | number | yes | The unique numeric identifier of the List to retrieve. To locate this ID, right-click the List in your Sidebar, select Copy link, and extract the last segment of the pasted URL. |
No output schema declared.
No examples provided.
get_running_time_entry Get Running Time Entry ~125
Retrieves the currently active (running) time entry for the authenticated user in the specified workspace. A time entry with a negative duration indicates the timer is actively tracking time.
| 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 API. |
| assignee | number | – | The user ID of a specific team member whose running time entry should be retrieved; defaults to the authenticated user if omitted. |
| team_id | number | yes | The unique identifier of the workspace in which to look up the running time entry. |
No output schema declared.
No examples provided.
get_space Get Space ~41
Retrieves details for a specific Space within a Workspace, including its settings and configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| space_id | number | yes | The unique numeric identifier of the Space to retrieve. |
No output schema declared.
No examples provided.
get_task Get Task ~238
Retrieve detailed information about a specific task, including its fields, assignees, status, and attachments. Docs attached to the task are not returned.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_fields | array | – | Filter or include tasks matching specific Custom Field values using a JSON array of field conditions. Each condition specifies a field_id, a comparison operator, and a value. Supports Custom Relation… |
| custom_task_ids | boolean | – | Set to true to reference the task by its custom task ID instead of the default ClickUp task ID. Must be used together with the team_id parameter. |
| include_markdown_description | boolean | – | Set to true to return the task description formatted in Markdown instead of plain text. |
| include_subtasks | boolean | – | Set to true to include all subtasks nested under the task in the response. Defaults to false. |
| task_id | string | yes | The unique identifier of the task to retrieve. When using custom task IDs, set custom_task_ids to true and provide the team_id. |
| team_id | number | – | The Workspace ID required when custom_task_ids is set to true. Identifies which Workspace the custom task ID belongs to. |
No output schema declared.
No examples provided.
get_task_time_in_status Get Task Time in Status ~159
Retrieves how long a task has spent in each status, providing a breakdown of time per status stage. Requires the Total Time in Status ClickApp to be enabled by a Workspace owner or admin.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request payload, used to indicate the format of the request body sent to the API. |
| custom_task_ids | boolean | – | Set to true to reference the task by its custom task ID instead of the default ClickUp task ID. |
| task_id | string | yes | The unique identifier of the task for which to retrieve time-in-status data. |
| team_id | number | – | The Workspace ID (team_id) required when using custom task IDs. Must be provided alongside custom_task_ids=true. |
No output schema declared.
No examples provided.
get_task_tracked_time Get Task Tracked Time ~142
Retrieves all tracked time entries associated with a specific task. Note: This is a legacy endpoint; the Time Tracking API is recommended for managing time entries.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request payload, indicating the format of the data 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. |
| task_id | string | yes | The unique identifier of the task whose tracked time entries you want to retrieve. |
| 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.
get_time_entry Get Time Entry ~229
Retrieves a single time entry by its ID within a workspace. Note that a time entry with a negative duration indicates the timer is currently running for that user.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request body, indicating the format of the payload being sent. |
| include_approval_details | boolean | – | When true, includes detailed information about the current approval state and approver for the time entry. |
| include_approval_history | boolean | – | When true, includes the full approval history for the time entry, showing past approval state changes. |
| include_location_names | boolean | – | When true, includes the human-readable names of the List, Folder, and Space alongside their respective IDs in the response. |
| include_task_tags | boolean | – | When true, includes any task tags associated with the time entry in the response. |
| team_id | number | yes | The unique numeric ID of the workspace containing the time entry. |
| timer_id | string | yes | The unique ID of the time entry to retrieve. Time entry IDs can be obtained from the Get Time Entries Within a Date Range endpoint. |
No output schema declared.
No examples provided.
get_time_entry_history Get Time Entry History ~108
Retrieves the change history for a specific time entry, showing a chronological list of modifications made to it.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request body, indicating the format of the data being sent. |
| team_id | number | yes | The unique numeric ID of the workspace containing the time entry. |
| timer_id | string | yes | The unique ID of the time entry whose history you want to retrieve. Can be obtained from the Get Time Entries Within a Date Range endpoint. |
No output schema declared.
No examples provided.
get_view Get View ~64
Retrieves metadata and configuration details for a specific task or page view by its unique identifier. The fields returned vary depending on the view type.
| Name | Type | Req | Description |
|---|---|---|---|
| view_id | string | yes | The unique identifier of the view to retrieve. Corresponds to a specific task or page view within the workspace. |
No output schema declared.
No examples provided.
get_workspace_plan Get Workspace Plan ~48
Retrieves the current subscription plan details for the specified Workspace, including plan tier and associated features.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | string | yes | The unique identifier of the Workspace whose plan information you want to retrieve. |
No output schema declared.
No examples provided.
get_workspace_seats Get Workspace Seats ~56
Retrieves seat usage information for a Workspace, including the number of used, total, and available seats for both members and guests.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | string | yes | The unique identifier of the Workspace whose seat information you want to retrieve. |
No output schema declared.
No examples provided.
get_workspace_user Get Workspace User ~111
Retrieves detailed profile and role information for a specific user within a Workspace. Available exclusively on the Enterprise Plan.
| Name | Type | Req | Description |
|---|---|---|---|
| include_shared | boolean | – | When set to false, excludes details of items shared with the user as a guest; defaults to true to include all shared item details. |
| team_id | number | yes | The unique numeric ID of the Workspace (also referred to as a team) containing the user. |
| user_id | number | yes | The unique numeric ID of the user to retrieve within the specified Workspace. |
No output schema declared.
No examples provided.
invite_workspace_guest Invite Workspace Guest ~210
Invites a guest user to a Workspace by email on an Enterprise Plan. After inviting, grant the guest access to specific Folders, Lists, or Tasks using the corresponding add-guest endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| can_create_views | boolean | – | Whether the guest is allowed to create new views. |
| can_edit_tags | boolean | – | Whether the guest is permitted to edit tags within the Workspace. |
| can_see_points_estimated | boolean | – | Whether the guest can view point estimates on tasks. |
| can_see_time_estimated | boolean | – | Whether the guest can view time estimates on tasks. |
| can_see_time_spent | boolean | – | Whether the guest can view time spent on tasks. |
| custom_role_id | integer | – | The ID of a custom role to assign to the guest upon invitation. |
| string | yes | The email address of the guest to invite to the Workspace. | |
| team_id | number | yes | The unique identifier of the Workspace to which the guest will be invited. |
No output schema declared.
No examples provided.
invite_workspace_member Invite Workspace Member ~153
Invites a user to join a Workspace as a full member via email. This endpoint is exclusive to Enterprise Plan Workspaces; use the Invite Guest endpoint to add guest-level users instead.
| Name | Type | Req | Description |
|---|---|---|---|
| admin | boolean | yes | Set to true to grant the invited user admin-level permissions in the Workspace, or false for standard member permissions. |
| custom_role_id | integer | – | The ID of a custom role to assign to the invited user upon joining, if your Workspace has custom roles configured. Omit to use the default member role. |
| string | yes | The email address of the person to invite to the Workspace. | |
| team_id | number | yes | The unique identifier of the Workspace to which the user will be invited. |
No output schema declared.
No examples provided.
link_task Link Task ~158
Creates a directional link between two tasks, equivalent to using the Task Links feature in the task's right-hand sidebar. Only task-to-task links are supported; general or cross-object links are not.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_task_ids | boolean | – | Set to true to reference tasks by their custom task IDs instead of their default system IDs. Requires team_id to also be provided when enabled. |
| links_to | string | yes | The ID of the task to link to (the target task). |
| task_id | string | yes | The ID of the task initiating the link (the source task). |
| team_id | number | – | The Workspace ID (team) required when custom_task_ids is set to true, used to resolve custom task IDs within the correct workspace scope. |
No output schema declared.
No examples provided.
list_chat_view_comments List Chat View Comments ~158
Retrieve comments from a Chat view, returning the most recent 25 comments by default. Use the date and ID of the oldest comment from a previous response to paginate and retrieve the next 25 comments.
| Name | Type | Req | Description |
|---|---|---|---|
| start | integer | – | The timestamp of a Chat view comment to paginate from, expressed as Unix time in milliseconds. Use the date of the oldest comment from the previous response to retrieve the next page of comments. |
| start_id | string | – | The unique identifier of a Chat view comment to paginate from. Use the ID of the oldest comment from the previous response alongside the `start` parameter to retrieve the next page of comments. |
| view_id | string | yes | The unique identifier of the Chat view whose comments you want to retrieve. |
No output schema declared.
No examples provided.
list_comment_replies List Comment Replies ~54
Retrieves all threaded reply comments nested under a specified parent comment. The parent comment itself is excluded from the returned results.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | number | yes | The unique identifier of the parent comment whose threaded replies should be retrieved. |
No output schema declared.
No examples provided.
list_comments List Comments ~139
Retrieve comments added to a specific List, returning the most recent 25 by default. Use the oldest comment's date and ID as pagination cursors to fetch earlier comments in batches of 25.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | number | yes | The unique identifier of the List whose comments you want to retrieve. |
| start | integer | – | The timestamp of the oldest comment from the previous page, used to paginate to the next set of 25 comments. Provide as Unix time in milliseconds. |
| start_id | string | – | The unique comment ID of the oldest comment from the previous page, used alongside the start timestamp to paginate to the next set of 25 comments. |
No output schema declared.
No examples provided.
list_custom_fields List Custom Fields ~84
Retrieves all Custom Fields accessible to the authenticated user within a specific List. Use this to discover available field definitions before reading or writing custom field data.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type format for the request, indicating the content format expected by the API. |
| list_id | number | yes | The unique numeric identifier of the List whose Custom Fields you want to retrieve. |
No output schema declared.
No examples provided.
list_custom_roles List Custom Roles ~79
Retrieves all Custom Roles available in the specified Workspace, allowing you to review role definitions and optionally include their member assignments.
| Name | Type | Req | Description |
|---|---|---|---|
| include_members | boolean | – | When set to true, the response will include the list of members assigned to each Custom Role. |
| team_id | number | yes | The unique identifier of the Workspace whose Custom Roles you want to retrieve. |
No output schema declared.
No examples provided.
list_custom_task_types List Custom Task Types ~57
Retrieves all custom task types defined in a Workspace, allowing you to see available task type options for organizing and categorizing work.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | number | yes | The unique identifier of the Workspace whose custom task types you want to retrieve. |
No output schema declared.
No examples provided.
list_folder_custom_fields List Folder Custom Fields ~94
Retrieves all Custom Fields created at the Folder level for the specified folder. Note that Custom Fields created at the List level within the folder are not included in the results.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request payload, used to indicate the format of the data being sent to the server. |
| folder_id | number | yes | The unique numeric identifier of the folder whose custom fields you want to retrieve. |
No output schema declared.
No examples provided.
list_folder_lists List Folder Lists ~77
Retrieve all Lists contained within a specified Folder. Optionally include archived Lists in the results.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | When set to true, includes archived Lists in the response alongside active ones. Defaults to false, returning only active Lists. |
| folder_id | number | yes | The unique identifier of the Folder whose Lists you want to retrieve. |
No output schema declared.
No examples provided.
list_folder_templates List Folder Templates ~117
Retrieves all Folder templates available in a Workspace, including their template IDs. Use the returned template IDs (prefixed with `t-`) with the Create Folder From Template endpoint to instantiate new Folders.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type of the request body sent to the API. |
| page | integer | yes | Zero-indexed page number for paginating through Folder template results; start at 0 for the first page. |
| team_id | number | yes | The unique identifier of the Workspace whose Folder templates you want to retrieve. |
No output schema declared.
No examples provided.
list_folder_views List Folder Views ~55
Retrieves all task and page views available within a specific Folder. Use this to discover the views configured for organizing and displaying folder content.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | number | yes | The unique identifier of the Folder whose views you want to retrieve. |
No output schema declared.
No examples provided.
list_folderless_lists List Folderless Lists ~76
Retrieves all Lists within a Space that are not organized inside a Folder. Optionally includes archived Lists in the results.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | When set to true, includes archived Lists in the response alongside active ones. |
| space_id | number | yes | The unique identifier of the Space whose folderless Lists you want to retrieve. |
No output schema declared.
No examples provided.
list_folders List Folders ~77
Retrieve all Folders within a specified Space. Optionally include archived Folders in the results.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | When set to true, returns only archived Folders; when false or omitted, returns only active Folders. |
| space_id | number | yes | The unique identifier of the Space whose Folders you want to retrieve. |
No output schema declared.
No examples provided.
list_goals List Goals ~86
Retrieves all Goals available in a specified Workspace, with an option to include completed Goals in the results.
| Name | Type | Req | Description |
|---|---|---|---|
| include_completed | boolean | – | When set to true, completed Goals are included in the response alongside active ones; omitting this parameter or setting it to false returns only active Goals. |
| team_id | number | yes | The unique identifier of the Workspace whose Goals you want to retrieve. |
No output schema declared.
No examples provided.
list_list_members List List Members ~64
Retrieves Workspace members who have been explicitly granted access to a specific List. Note: this does not include members with inherited access via a Team, Folder, or Space.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | number | yes | The unique numeric identifier of the List whose explicit members you want to retrieve. |
No output schema declared.
No examples provided.
list_shared_hierarchy List Shared Hierarchy ~64
Retrieves all tasks, Lists, and Folders that have been shared with the authenticated user within a specified workspace. Useful for discovering shared content accessible to the current user.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | number | yes | The unique identifier of the workspace whose shared content you want to retrieve. |
No output schema declared.
No examples provided.
list_space_custom_fields List Space Custom Fields ~89
Retrieves all Custom Fields created at the Space level for a specific Space. Note that Custom Fields created at the 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, used to indicate the format of the data being sent. |
| space_id | number | yes | The unique identifier of the Space whose Custom Fields you want to retrieve. |
No output schema declared.
No examples provided.
list_space_tags List Space Tags ~78
Retrieve all task tags available in a specified Space. Use this to discover tags that can be applied to tasks within the Space.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type format for the request, indicating the content should be sent as JSON. |
| space_id | number | yes | The unique identifier of the Space whose tags you want to retrieve. |
No output schema declared.
No examples provided.
list_space_views List Space Views ~54
Retrieve all task and page views available within a specific Space. Useful for discovering how work is organized and displayed within a Space.
| Name | Type | Req | Description |
|---|---|---|---|
| space_id | number | yes | The unique identifier of the Space whose views you want to retrieve. |
No output schema declared.
No examples provided.
list_spaces List Spaces ~77
Retrieves all Spaces available within a specified Workspace. Member details are only accessible for private Spaces the authenticated user belongs to.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | When set to true, returns only archived Spaces; when false or omitted, returns only active Spaces. |
| team_id | number | yes | The unique identifier of the Workspace whose Spaces you want to retrieve. |
No output schema declared.
No examples provided.
list_task_comments List Task Comments ~149
Retrieve comments for a specific task, returned in reverse chronological order (newest to oldest). By default returns the 25 most recent comments; use the `start` and `start_id` parameters together with the last comment of the current response to paginate through older comments.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_task_ids | boolean | – | Set to `true` if referencing the task by its custom task ID instead of the default ClickUp task ID. |
| task_id | string | yes | The unique identifier of the task whose comments you want to retrieve. |
| team_id | number | – | The Workspace ID (team ID) required when `custom_task_ids` is set to `true` to correctly resolve the custom task ID. |
No output schema declared.
No examples provided.
list_task_members List Task Members ~65
Retrieves Workspace members who have been explicitly granted direct access to a specific task. Note: this does not include members with access via a Team, List, Folder, or Space.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The unique identifier of the task whose explicit members you want to retrieve. |
No output schema declared.
No examples provided.
list_task_templates List Task Templates ~108
Retrieves a paginated list of task templates available in the specified Workspace, which can be used to standardize task creation across teams.
| Name | Type | Req | Description |
|---|---|---|---|
| Content-Type | string | yes | The media type format for the request body, which must be set to indicate JSON content. |
| page | integer | yes | The zero-based page number for paginating through task template results, where 0 returns the first page. |
| team_id | number | yes | The unique identifier of the Workspace whose task templates you want to retrieve. |
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.