Available

ClickUp MCP server

Find a List and maintain its tasks with Arc0’s ClickUp tools. Updates cover selected task fields, while comments remain visible collaboration rather than private notes. Connect through Arc0 to use the actions your identity is allowed to call.

ProductivityAPI key · OAuthMCP + RESTclickup.com
AUDIT LOG · CLICKUPPOLICY: acme-support
09:41:07 · claude · u_8f2read
clickup.list_lists
List lists✓ allowed · 212ms
09:41:08 · claude · u_8f2read
clickup.get_task
Get task✓ allowed · 164ms
09:41:09 · claude · u_8f2write
clickup.create_task
Create task✓ approved · approved by user
ILLUSTRATIVE POLICY TRACE · NOT A LIVE RECEIPT

Working with ClickUp

When a task needs a destination, use clickup.list_workspaces, clickup.list_spaces, and clickup.list_folders to navigate to the relevant container. clickup.list_lists lists the Lists in a known Folder; it does not discover folderless Lists. Retain the native List and task IDs rather than substituting human-facing custom task identifiers.

clickup.get_tasks reads a filtered List page, while clickup.get_task retrieves the current content and status of a known task. clickup.create_task records new work in that List. clickup.update_task can change supported content, status, priority, due date, or archive state; it does not reassign an existing task or clear its priority or due date.

Use clickup.add_comment for a visible progress note. Assignees or watchers may receive notifications even when broad notification is disabled. clickup.list_members returns explicit List member IDs, excluding inherited access, so an empty result does not mean nobody can see the List. After an uncertain creation, inspect recent tasks with a creation-time filter and include closed tasks before considering another attempt.

Official MCP reference: ClickUp documentation.

01 · USE CASES

Agent workflows for ClickUp.

01

Locate the destination List

Use clickup.list_workspaces, clickup.list_spaces, clickup.list_folders and clickup.list_lists to navigate the supported hierarchy.

02

Review List tasks

Use clickup.get_tasks for a filtered page and clickup.get_task for a known native task ID.

03

Create a follow-up

Use clickup.create_task with the chosen List and reviewed task details.

04

Record task progress

Use clickup.update_task for supported status or content changes and clickup.add_comment for a collaborator-visible update.

02 · ACTIONS

10 ClickUp actions, graded by risk.

These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.

read

7

Look things up, subject to your permissions.

  • clickup.list_workspaces
    List workspaces

    Use when you need accessible Workspace IDs. Do not use for member discovery; this action omits members.

  • clickup.list_spaces
    List spaces

    Use when you need Space IDs in a Workspace. Do not use for member discovery; this action omits members.

  • clickup.list_folders
    List folders

    Use when you need Folder IDs in a Space, including its flat list of subfolders. Do not use to list tasks or folderless Lists.

  • clickup.list_lists
    List lists

    Use when you need List IDs in a known Folder. Do not use for folderless Lists; they are not included.

  • clickup.get_task
    Get task

    Use when you need current content and status for a native ClickUp task ID. Do not use custom task IDs or search text; use get_tasks to browse a List.

  • clickup.get_tasks
    Get tasks

    Use when you need a filtered List page or recent creates via date_created_gt (Unix ms). Pages start at zero, up to 100 tasks; follow next_page until null. Do not use for Workspace-wide search.

  • clickup.list_members
    List members

    Use when you need explicit List member IDs only. Do not use to infer all access: Team, Folder and Space inheritance is excluded; empty does not mean nobody has access. Workspace/Space member reads are not exposed by this connector.

write

3

Create and change things. Allow, or ask the user first.

  • clickup.create_task
    Create task

    Use when you need a new task in a known List. Do not use to update a task or retry an ambiguous write. After timeout, use get_tasks with date_created_gt just before the attempt and include_closed true, then compare candidate content before deciding.

  • clickup.update_task
    Update task

    Use when you need to change task content, status, priority, due date or archive state using a native ID. Supply a change. Do not use for reassignment, custom IDs or clearing priority/due date; those operations are not exposed.

  • clickup.add_comment
    Add comment

    Use when you need a task comment. Do not use for silent notes: assignees/watchers may be notified even with notify_all false. Do not retry an ambiguous outcome.

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · POLICIES AND AUDIT

Control access to ClickUp.

Connect the intended ClickUp account, authorize your AI client and set policies for its tools.

Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.

Configure policies and approvals

Example policy choices

  • Read actions: allow where authorized
  • clickup.create_task: require approval

Arc0 MCP endpoint: https://api.arc0.ai/mcp

04 · AUTH AND DATA

How ClickUp connects.

Connect ClickUp using API key or OAuth. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →

AUTH
API key · OAuth
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · AI CLIENTS

Use ClickUp with your AI client.

Sign in to Arc0 and connect ClickUp in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.

ClickUp with Claude

Claude Desktop + Claude Code

  1. In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
  2. For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
  3. Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Claude
ClickUp with ChatGPT

ChatGPT on the web

  1. Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
  2. Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
  3. Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for ChatGPT
ClickUp with OpenAI Codex

Codex app + CLI

  1. Run the registration command below. The app and CLI share ~/.codex/config.toml.
  2. Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
  3. Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for OpenAI Codex
ClickUp with Cursor

Remote MCP setup

  1. Add Arc0 in your client’s remote MCP settings using the server URL below.
  2. Choose OAuth, sign in to Arc0, select the intended workspace and review access.
  3. Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Cursor
ClickUp with VS Code

Remote MCP setup

  1. Add a remote HTTP MCP server named Arc0 using the URL below.
  2. Use OAuth and finish Arc0 sign-in, workspace selection and consent.
  3. Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
ClickUp with Any MCP client

Streamable HTTP

  1. Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
  2. For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
  3. Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting

After setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.

07 · FAQ

ClickUp and Arc0, answered.

Q01

Is there an official ClickUp MCP server, and how does Arc0 differ?

Yes. ClickUp provides an official OAuth-based MCP server. Arc0’s current ClickUp tools use a personal token and a bounded REST action set rather than the full vendor MCP tool list.

Q02

Which permissions does Arc0 need for ClickUp?

Use a personal API token; this version requests no OAuth scopes. The token’s user and Workspace permissions govern access. Member reads return IDs only and do not enumerate all inherited access.

Q03

Does this work with Claude, ChatGPT, Codex and Cursor?

Yes, through Arc0 MCP when your Claude, ChatGPT, Codex, or Cursor client supports remote MCP and your account permits it. Connect the app in Arc0 and configure your client using the Arc0 setup guide. App permissions still apply.

Q04

How are credentials stored, refreshed and revoked?

Arc0 stores the token encrypted with no refresh flow. Disconnect removes local access. Regenerate or revoke the token in ClickUp to invalidate it outside Arc0.

Q05

What happens with rate limits or errors?

ClickUp rate limits depend on the Workspace plan and token. Arc0 reports rate-limit and permission failures. Unknown task or comment writes are not safe to repeat automatically; inspect the task or recent List activity first.

Q06

What is the availability of these ClickUp tools?

These tools are available. Connect the app in Arc0 and authorize your AI client. The action list describes the current implementation.

Get started

Plug ClickUp into your agent.

ClickUp MCP server: 10 actions including list workspaces, list spaces, list folders. Connect through Arc0.

Free to build · MCP + REST · Audit log on every plan

ClickUp and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by ClickUp.