Back to Tools
Productivity & Docs OAuth
clickup logo

ClickUp MCP Tools for AI Agents

Let an agent find tasks, create and update work, assign teammates, and read or reply to task comments in ClickUp.

Available Tools

40 tools available in this integration

Clickup.CreateTask

Create a new task in a ClickUp list with optional planning metadata.

Clickup.CreateTaskComment

Create a new comment on a ClickUp task with optional assignment.

Clickup.CreateTaskCommentReply

Create a new threaded reply to an existing ClickUp comment.

Clickup.FuzzySearchFoldersByName

Search for folders using fuzzy matching on folder names.

Clickup.FuzzySearchListsByName

Search for lists using fuzzy matching on list names.

Clickup.FuzzySearchMembersByName

Search for workspace members using fuzzy matching on member names.

Clickup.FuzzySearchTasksByName

Search for tasks using fuzzy matching on task names.

Clickup.GetFoldersForSpace

Retrieve folders (also called directories, project categories, or project areas) from a

Clickup.GetListsForFolder

Retrieve task lists from a ClickUp folder (when users refer to a folder as a "directory",

Clickup.GetListsForSpace

Retrieve all task lists from a ClickUp space by collecting lists from all folders within the

Clickup.GetMembersForWorkspace

Retrieve all team members from a specific ClickUp workspace.

Clickup.GetSpaces

Retrieve spaces from a ClickUp workspace.

Clickup.GetStatusesForList

Retrieve the possible task statuses for a specific ClickUp list.

Clickup.GetSystemGuidance

Return static guidance intended solely to help agents make informed decisions.

Clickup.GetTask

Get detailed information about a specific task by its ID.

Clickup.GetTaskById

Get detailed information about a specific task by its ID.

Clickup.GetTaskCommentReplies

Get threaded replies for a specific ClickUp comment with pagination support.

Clickup.GetTaskComments

Get comments for a specific ClickUp task with pagination support.

Clickup.GetTasksByAssignees

Get filtered tasks assigned to specific team members with advanced filtering options.

Clickup.GetTasksByScope

Get filtered tasks from ClickUp with advanced filtering options.

Clickup.GetWorkspaceInsights

Return a brief overview for a workspace using the latest updated tasks to inform the user.

Clickup.GetWorkspaceOverview

Return a brief overview for a workspace using the latest updated tasks to inform the user.

Clickup.ListFolderLists

Retrieve task lists from a ClickUp folder (when users refer to a folder as a "directory",

Clickup.ListFolders

Retrieve folders (also called directories, project categories, or project areas) from a

Clickup.ListListStatuses

Retrieve the possible task statuses for a specific ClickUp list.

Clickup.ListReplies

Get threaded replies for a specific ClickUp comment with pagination support.

Clickup.ListSpaceLists

Retrieve all task lists from a ClickUp space by collecting lists from all folders within the

Clickup.ListSpaces

Retrieve spaces from a ClickUp workspace.

Clickup.ListTaskComments

Get comments for a specific ClickUp task with pagination support.

Clickup.ListTasks

List filtered tasks from a ClickUp workspace.

Clickup.ListWorkspaceMembers

Retrieve all team members from a specific ClickUp workspace.

Clickup.ReplyToComment

Create a new threaded reply to an existing ClickUp comment.

Clickup.SearchFolders

Search for folders using fuzzy matching on folder names.

Clickup.SearchLists

Search for lists using fuzzy matching on list names.

Clickup.SearchTasks

Search for tasks using fuzzy matching on task names.

Clickup.SearchWorkspaceMembers

Search for workspace members using fuzzy matching on member names.

Clickup.UpdateTask

Update one or more fields of an existing ClickUp task.

Clickup.UpdateTaskAssignees

Update task assignees by adding and/or removing specific users.

Clickup.UpdateTaskComment

Update an existing comment on a ClickUp task.

Clickup.WhoAmI

Return current user profile and accessible workspaces (teams).

Working directly against the raw API? 134 more tools in the ClickUp API server →

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "find the overdue tasks in the mobile app project and assign the unowned ones to me." Arcade picks the right ClickUp tools without guessing space, list, or task IDs first.

Up to 100x fewer tokens

ClickUp list and search results return lightweight task, list, folder, and member metadata by default, while detailed task fields and comments are fetched separately, so the agent need not load an entire workspace into context.

Complete the workflow end to end

Find the project list, inspect its tasks and comments, update statuses and assignees, add a comment, and create follow-up tasks through one toolkit designed around the complete project-management task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing ClickUp

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For ClickUp, you can implement some of these policies:

Access when tools are listed for a user
  • Hide Clickup.UpdateTaskAssignees from agents unless the roles your IDP marks as project owners are active, so an agent cannot add people to work without authorization.
  • Restrict Clickup.CreateTaskCommentReply to agents operating under your collaboration role, so unreviewed automation cannot continue a sensitive discussion on someone else's task.
  • Deny Clickup.UpdateTask to read-only agents, so they cannot change deadlines, priorities, statuses, or other task fields.
  • Hide Clickup.ReplyToComment from agents unless the roles your IDP marks as discussion owners are active, so an agent cannot continue a conversation on another person's task.
Pre-execution before each tool call
  • Require human approval before Clickup.CreateTask runs in lists used for customer commitments, so an agent cannot create externally binding work without review.
  • Block Clickup.CreateTaskComment when the comment contains credentials, access tokens, or customer data, so an agent cannot publish secrets in your workspace.
  • Require human approval before Clickup.UpdateTaskComment changes comments marked for legal or executive review, so an agent cannot alter an auditable discussion without sign-off.
  • Require human approval before Clickup.ReplyToComment posts a reply on tasks marked for executive, legal, or customer escalation, so an agent cannot add an unreviewed commitment to the thread.
Post-execution after the tool returns
  • Redact phone numbers, email addresses, credentials, and customer identifiers from Clickup.GetTaskComments results before they reach the model.
  • Strip message bodies from Clickup.GetTaskCommentReplies results when the parent comment is marked confidential, while retaining reply authors and timestamps for workflow context.
  • Redact private descriptions, attachments, and custom-field values from Clickup.GetTaskById results for tasks labeled confidential before the model sees them.
  • Redact task descriptions, custom-field values, and assignee details from Clickup.ListTasks results for tasks labeled confidential before they reach the model.
  • Strip personal email addresses, phone numbers, and profile URLs from Clickup.ListWorkspaceMembers results, so the model receives names and workspace roles without private contact details.
  • Deny the output of Clickup.GetWorkspaceOverview when its latest tasks include a legal-hold or executive-confidential label, so sensitive project summaries do not reach the model.

How to use ClickUp with your agent

Connect ClickUp to your MCP client and follow the setup from authorization through your first agent request. Each user authorizes their own ClickUp account.

Your questions, answered

A ClickUp MCP server exposes ClickUp workspace capabilities as structured tools that an AI agent can call through the Model Context Protocol. After a user authorizes their ClickUp account, the agent can search workspace structures, read tasks and comments, and create or update permitted work items.

ClickUp's own MCP server is a ClickUp-provided endpoint for accessing ClickUp capabilities. Arcade adds per-user OAuth, agent-optimized task and workspace actions, approval workflows, redaction, and scope controls, while giving agents one connection path from supported clients.

Arcade agents can browse spaces, folders, lists, statuses, members, and tasks; search for tasks and workspace members; read task details, comments, and replies; create and update tasks; change assignees; and create, update, or reply to task comments. They can also return workspace overviews and insights, but these actions do not include deleting tasks or other broader ClickUp administration.

Arcade uses per-user ClickUp OAuth, with access limited by the permissions and workspace access granted to that user. Read workflows need read access, while creating or changing tasks, assignees, or comments requires the corresponding ClickUp write permissions; grant only the access your workflow needs.

Yes. Each user authorizes their own ClickUp account through OAuth. Actions run under that user's authorization and can reach only the workspaces and resources that user is allowed to access.

Yes. Contextual Access policies can require human approval before consequential ClickUp actions, such as creating or updating tasks, changing assignees, or posting comments. The call proceeds only after the policy's conditions have been satisfied.

Arcade proxies ClickUp API calls and does not persist your ClickUp content as part of normal tool execution. ClickUp credentials are brokered and stored encrypted at rest, and the model never receives them.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works with Arcade ClickUp, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade refreshes ClickUp access while the user's authorization remains valid. If the authorization is revoked, rotated, or can no longer be refreshed, ClickUp actions stop until the user reconnects their account.

ClickUp's API rate limits and workspace-level access constraints still apply to actions performed through Arcade. Arcade does not remove those ClickUp limits, so high-volume workflows should pace requests and handle rate-limit responses.

Ready to actually ship your agent?

Connect your agent to ClickUp with managed OAuth, agent-optimized tools and approval controls for consequential actions.