ClickUp MCP integration for AI agents.
Connect AI agents to ClickUp through 68 structured actions, including add task to list, add dependency, and delete checklist. Review authentication, inputs…
- ACTION CONTRACTS
- 68
- AUTHENTICATION
- OAuth 2.0 + API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the ClickUp integration exposes
The ClickUp Agent App exposes 68 provider-backed actions for productivity work. Its current contract lets an authorized agent add a clickup task to an additional list, add a clickup dependency relationship to a task, and delete a clickup checklist by checklist id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0 and API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected ClickUp account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ClickUp capabilities.
Showing 12 of 68 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
add_task_to_listREADAdd a ClickUp task to an additional list.
INPUTS: listId / taskId
add_dependencyWRITEAdd a ClickUp dependency relationship to a task.
INPUTS: taskId / dependsOnTaskId / dependencyOfTaskId
delete_checklistHIGH IMPACTDelete a ClickUp checklist by checklist ID.
INPUTS: checklistId
add_tag_to_taskWRITEAdd a ClickUp tag to a task.
INPUTS: taskId / tagName
add_task_linkWRITEAdd a ClickUp task link to a task.
INPUTS: taskId / linksToTaskId
create_checklistWRITECreate a checklist on a ClickUp task.
INPUTS: taskId / name
create_checklist_itemWRITECreate a checklist item on a ClickUp checklist.
INPUTS: checklistId / name / assignee
create_folderWRITECreate a ClickUp folder in a space.
INPUTS: spaceId / name
create_folderless_listREADCreate a ClickUp folderless list in a space.
INPUTS: spaceId / name / content / markdownContent / dueDate
create_listREADCreate a ClickUp list in a folder.
INPUTS: folderId / name / content / markdownContent / dueDate
create_list_from_templateREADCreate a ClickUp list from a folder list template.
INPUTS: folderId / templateId / name / options
create_spaceWRITECreate a ClickUp space in a workspace.
INPUTS: workspaceId / name / multipleAssignees / features
INPUT CONTRACTS
Know what the action needs before it runs.
add_task_to_list
listIdREQUIRED- The ClickUp list ID.
taskIdREQUIRED- The ClickUp task ID.
add_dependency
taskIdREQUIRED- The ClickUp task ID.
dependsOnTaskIdOPTIONAL- The ClickUp task ID that the task depends on.
dependencyOfTaskIdOPTIONAL- The ClickUp task ID that depends on the task.
delete_checklist
checklistIdREQUIRED- The ClickUp checklist ID.
add_tag_to_task
taskIdREQUIRED- The ClickUp task ID.
tagNameREQUIRED- The ClickUp tag name.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Add Task To List
Add a ClickUp task to an additional list. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
add_task_to_listControl Add Dependency
Add a ClickUp dependency relationship to a task. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_dependencyVerify with Add Dependency
Add a ClickUp dependency relationship to a task. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
add_dependencySAFETY BOUNDARY
Operate ClickUp with explicit limits
- Authorize ClickUp with OAuth 2.0 and API key and grant only the provider access required by the selected actions.
- 31 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_checklist`, `delete_checklist_item`, and `delete_comment` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `clickup.write` and `clickup.read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the ClickUp task completed successfully.
CONNECTION MODEL
OAuth 2.0 + API key
ClickUp personal API token sent with the Authorization header. Generate it from Settings > Apps, or see https://developer.clickup.com/docs.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 37
- WRITE SIGNALS
- 19
- HIGH IMPACT
- 12
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by ClickUp.