ClickUp
The ClickUp connector lets AI agents browse the workspace hierarchy, manage tasks, add comments, change statuses, and assign work — all through the ClickUp REST API using OAuth 2.0. Your credentials are stored encrypted in MCPGate's vault and are never exposed to the AI client.
Required scopes#
MCPGate requests the following OAuth scopes when you connect a ClickUp account. All scopes are requested up front so you don't need to re-authorise when enabling additional tools.
| Scope | Purpose |
|---|---|
| read:task | Read tasks, comments, and workspace structure |
| write:task | Create, update, assign, and delete tasks |
| read:team | Read workspace and space metadata |
| read:user | Read user IDs for task assignment |
Tool reference#
The ClickUp connector exposes 12 tools: 6 read, 5 write, and 1 delete. Use the MCP Apps page to enable or disable individual tools per app, and the Guardrails page to add fine-grained rules on top.
| Tool | Category | Description |
|---|---|---|
| clickup_list_spaces | read | List all spaces in a ClickUp workspace |
| clickup_list_folders | read | List all folders in a ClickUp space |
| clickup_list_lists | read | List all lists in a ClickUp folder or space |
| clickup_list_tasks | read | List tasks in a ClickUp list |
| clickup_get_task | read | Get a specific ClickUp task by ID |
| clickup_list_comments | read | List comments on a ClickUp task |
| clickup_create_task | write | Create a new task in a ClickUp list |
| clickup_update_task | write | Update an existing ClickUp task |
| clickup_create_comment | write | Add a comment to a ClickUp task |
| clickup_set_status | write | Change the status of a ClickUp task |
| clickup_assign_task | write | Assign a ClickUp task to a user |
| clickup_delete_task | delete | Delete a ClickUp task permanently |
Delete is permanent
clickup_delete_taskpermanently deletes the task and all its comments and subtasks. ClickUp does not have a trash bin for deleted tasks. Always deny this tool in apps that don't explicitly need it.Common guardrail recipes#
Read-only access#
Enable only the six read tools and deny all write and delete tools. This is the safest configuration for agents that monitor project status, generate reports, or feed ClickUp data into other workflows.
Contribute preset#
Enable read tools plus clickup_create_task, clickup_update_task, clickup_create_comment, clickup_set_status, and clickup_assign_task. Deny clickup_delete_task. This is the recommended configuration for project management agents that need to actively work tasks without the risk of permanently destroying them.
Restrict to a specific list#
Apply the allow_values template to clickup_create_task and other write tools, targeting the list_id field. Provide the IDs of the list(s) the agent is permitted to write to, keeping it isolated from other lists in the workspace.
Troubleshooting#
- Invalid status error — Statuses in ClickUp are per-list and customisable. The value passed to
clickup_set_statusmust exactly match one of the statuses configured for that list. Read the list details or ask the user for valid status names. - Assignee not found —
clickup_assign_taskrequires a numeric ClickUp user ID, not a display name or email. Use the workspace member list to look up user IDs before assigning. - Rate limit exceeded— ClickUp's API enforces rate limits per token. Apply the
rate_limitguardrail template to high-volume tools likeclickup_list_tasksto prevent the agent from exhausting the limit.