Skip to main content
Glama

ClickUp MCP Server

A Model Context Protocol server for ClickUp, built around two ideas:

Everything takes human names. find(scope: "Cavalry/Findings", assignee: "me", due: "overdue") — no IDs, no walking the tree to discover them. Names that don't resolve raise an error listing the valid options, because a confidently empty result is worse than a failure.

You choose what it can do. Four capability profiles, enforced on every outgoing request. Hand an unattended agent the agent profile and it can create tasks and comments but cannot alter or delete anything that already exists.

18 tools, 354 tests. Version 4.3.0 — see CHANGELOG.md. A heavily renovated fork of nsxdavid/clickup-mcp-server.

Status: 4.x is new. It has been through five adversarial red-team rounds but has not yet run in production. The previous 3.x line is still shipped in this repo and still what the reference deployment runs — see Running 3.x.

Quick start

Get a token from ClickUp → Settings → Apps → API Token (it starts with pk_). The workspace is discovered automatically — there is nothing else to configure.

No install:

{
  "mcpServers": {
    "clickup": {
      "command": "npx",
      "args": ["-y", "github:benthesoundguy/clickup-mcp-server"],
      "env": { "CLICKUP_API_TOKEN": "pk_your_token_here" }
    }
  }
}

Or from a clone, which is what you want if you plan to change anything:

git clone https://github.com/benthesoundguy/clickup-mcp-server
cd clickup-mcp-server
npm install          # builds automatically
npm run check        # verifies the token and connects — do this before wiring up a client
{
  "mcpServers": {
    "clickup": {
      "command": "node",
      "args": ["/absolute/path/to/clickup-mcp-server/build/v4/index.js"],
      "env": { "CLICKUP_API_TOKEN": "pk_your_token_here" }
    }
  }
}

Where that block goes

The shape above works as-is in Claude Desktop, Claude Code, Cursor, Cline, and Windsurf — they all use the mcpServers key. Two clients differ:

  • VS Code (.vscode/mcp.json) uses servers instead of mcpServers. Same inner shape. Copying a Cursor config unchanged is the most common setup mistake.

  • Zed (settings.json) uses context_servers, and nests the command:

    { "context_servers": { "clickup": { "command": { "path": "node", "args": ["/path/to/build/v4/index.js"] } } } }

Claude Code can skip the file entirely:

claude mcp add clickup --env CLICKUP_API_TOKEN=pk_... -- npx -y github:benthesoundguy/clickup-mcp-server

Putting the token in a file instead

If you would rather not paste a token into a client config — desktop apps rewrite those files and can persist a stale copy — put it in a .env next to the install and omit the env block entirely:

echo 'CLICKUP_API_TOKEN=pk_your_token_here' > .env

The server looks in <cwd>/.env, <install>/.env, and <install>/../.env, in that order, and says which one it used at startup. The token from the file outranks the environment, so rotating it in one place actually takes effect. Every other setting works the other way round — an explicit value in your client config always wins, so a stray .env can never widen MCP_PROFILE. Set MCP_STRICT_ENV=1 on a server to switch the whole lookup off.

When it doesn't work

npm run check          # from a clone
node build/v4/index.js --check

This prints every input the server resolved — which .env it found and what it applied, whether the token is present and the right shape, the active profile and tool count, the Node version and build stamp — and then actually connects to ClickUp and reports who you are and your rate budget. It never prints the token, so the output is safe to paste into an issue.

If the token is missing, the server does not die silently in stdio mode. It starts, registers its tools, and every call answers with what's wrong and how to fix it, so the problem shows up in your conversation rather than in a log file you have to go find. (In HTTP mode it still exits 1 — an unattended deployment should fail loudly.)

Related MCP server: ClickUp MCP Server

Capability profiles

One binary, four profiles, selected with MCP_PROFILE. Install once and add a client entry per profile, enabling whichever a given agent should have.

MCP_PROFILE

tools

schema cost

What it can do

read

11

2,236 tok

Observe only. No write of any kind can leave the process.

agent

12

2,635 tok

Read, plus append: create tasks, comments, chat messages, checklist items, time logs. Cannot alter or delete anything existing.

core (default)

16

4,129 tok

Everything a normal user does. No membership, guest, or webhook administration.

full

18

4,748 tok

Unrestricted, including membership and webhooks.

Schema cost is what the tool definitions consume in the model's context on every request, before any work happens. For comparison, 3.x costs ~18,600 tokens for 88 tools.

agent is the interesting one. It can add but never alter or destroy, so the worst an unattended agent can do is create clutter you can delete. That guarantee is enforced in three layers, and only the third is a security boundary:

  1. Tool filtering — which tools appear at all (context cost + tool selection)

  2. Action filtering — which actions a tool advertises (context cost + honesty)

  3. Write policy — an allowlist checked on every outgoing request, including uploads ← the guarantee

Layers 1 and 2 depend on every tool being tagged correctly by every future contributor. Layer 3 does not: it inspects the actual request on its way out, so a mistagged tool, a refactor, or an endpoint added next year cannot widen a profile. The test suite proves this by calling core-only handlers directly with an agent context — bypassing layers 1 and 2 entirely — and asserting nothing reaches the wire.

Things that look additive but are excluded from agent on purpose: attaching a tag, setting a custom field, and adding a dependency all mutate an existing task; creating a webhook starts streaming your data to an external endpoint. Append-only and safe are not the same property.

Why the default is core and not full

full grants membership administration — inviting a user consumes a billable seat, removing one changes a real person's access — plus webhooks, which send workspace data off-site. None of that is what a first connection is for, and a default nobody changes has to be the safe one. Ask for administration by name when you want it; until you do, the refusal tells you exactly how.

Attachments and the filesystem

attach reads a file from the machine the server runs on. That is a resource the write policy cannot see — it inspects URLs, and a file read has no URL — so it is governed separately by CLICKUP_ATTACH_ROOT:

  • Set → reads are confined to that directory. Containment is checked against the file's real path, after resolving .. and every symlink.

  • Unset → core and full may read any file the process can. Under agent, attach is not offered at all (12 tools instead of 13), because there is no safe default root: the working directory is usually the project directory, which is where .env lives.

A misconfigured root is fatal at startup rather than ignored — a boundary that silently isn't there is worse than none.

Tools

Tool

Min profile

Job

find

read

Query tasks anywhere. Scope, status, assignee, tags, due date — all by name.

task

read

One task in full, optionally with comments and subtasks.

tree

read

Workspace structure, printing the exact paths other tools accept.

meta

read

What values are legal here — statuses a list accepts, tags in a space, assignable people.

whoami

read

Identity, workspace, rate-limit budget, server health.

docs

read

Search ClickUp Docs, or read one.

comment

read

Read a task's comment thread, or post to it.

time

read

start · stop · current · log · report

fields

read

Inspect a list's custom fields, or set one by name.

chat

read

channels · read · post · members

checklist

read

list · add · add_item · rename · remove · check · uncheck

create

agent

Create one or more tasks — pass an array for bulk.

attach

agent

Upload a local file to a task (max 25MB). See above.

update

core

Update, move, assign, close, or delete — pass several IDs for bulk.

lists

core

create · rename · delete for lists and folders. Deletes need confirm: true.

goals

core

list · get · create · update · delete, including key results.

people

full

Members, guests, seats, groups, invitations, admin rights.

webhooks

full

list · create · delete

Tools narrow rather than vanish where it makes sense: under read, comment shows only its reading arguments and checklist advertises only list, so the schema tells the truth about what this connection can do instead of advertising actions that would be refused.

The rule everything follows

Never return a confident wrong answer. ClickUp makes this easy to get wrong, because it answers bad input with cheerful nonsense:

Request

ClickUp says

Which reads as

?assignees[]=99999999

200 {"tasks":[]}

"Sam has no work" — there is no Sam

?query=anything

200 + unfiltered results

a filtered search that wasn't

POST /list/{dest}/task/{id}

200 {}

"moved" — it didn't move

PUT /task/{id} with list_id

200

"moved" — silently ignored

GET /task/{bad-id}

401 Team not authorized

a permissions problem — it's a typo

?order_by=bogus

500

an outage — it's a bad enum

So this server resolves names and raises on ambiguity ("Findings" matching four lists is an error naming all four, never a coin flip); raises rather than returning empty when a filter value doesn't resolve; validates enums client-side against what the list actually accepts; verifies writes it cannot trust by reading the object back; and never overstates a count — a query that stopped paging reports 100+ matches, and any client-side filter reports how much it actually scanned.

Errors say what failed, why, and what to do next, with the valid options listed.

Environment variables

Variable

Default

Notes

CLICKUP_API_TOKEN

—

Required. ClickUp personal API token.

MCP_PROFILE

core

read · agent · core · full. Invalid values are fatal, never silently downgraded.

CLICKUP_ATTACH_ROOT

unset

Absolute directory that attach may read from. Required for attach under agent.

CLICKUP_WORKSPACE_ID

discovered

Only needed if the token can see several workspaces and you want a specific one.

MCP_TRANSPORT

stdio

Set to http for streamable HTTP.

MCP_HTTP_HOST

127.0.0.1

Bind address. Loopback by default — put a proxy or tunnel in front rather than binding 0.0.0.0.

MCP_HTTP_PORT

8000

Also selects HTTP mode if set.

MCP_AUTH_TOKEN

generated

Static bearer token, min 16 chars. Optional once MCP_OAUTH_ISSUER is set.

MCP_OAUTH_ISSUER

—

Authorization server issuer URL. Setting it makes this an OAuth resource server.

MCP_PUBLIC_URL

—

Required with OAuth. This server's canonical URI — the audience inbound tokens must name. Never inferred from the request.

MCP_OAUTH_AUDIENCE

MCP_PUBLIC_URL

Override, if your issuer mints a different audience value.

MCP_OAUTH_JWKS_URL

discovered

Signing keys, if the issuer publishes no discovery document.

MCP_OAUTH_SCOPES

—

Advertised in the metadata document. Informational.

MCP_STRICT_ENV

off

Set to 1 for servers — see below.

MCP_ALLOW_TOKEN_IN_PATH

off in strict

Re-enables the /mcp/<token> URL form under strict mode.

MCP_NO_ENV_FILE

off

Disables the .env file lookup (implied by strict mode).

CF_ACCESS_TEAM_DOMAIN

—

Cloudflare Access team. Enables Access JWT validation.

CF_ACCESS_AUD

—

Access application AUD tag. Required alongside the team domain — neither alone enables anything.

Remote mode (Claude web + mobile, and any HTTP client)

The server speaks streamable HTTP, and accepts three independent credentials. Any one of them authenticates a request; they are meant to coexist, because different clients can present different things.

Credential

For

Set with

OAuth 2.1 access token

Hosted clients — claude.ai connectors, ChatGPT connectors, anything spec-compliant

MCP_OAUTH_ISSUER + MCP_PUBLIC_URL

Cloudflare Access JWT

An origin behind a CF Tunnel

CF_ACCESS_TEAM_DOMAIN + CF_ACCESS_AUD

Static bearer token

Scripts, n8n, curl, CI

MCP_AUTH_TOKEN

MCP_TRANSPORT=http MCP_AUTH_TOKEN=$(openssl rand -hex 24) \
MCP_PROFILE=core CLICKUP_API_TOKEN=... node build/v4/index.js

GET /health is an unauthenticated probe reporting version, active profile, tool count and attachment root.

OAuth (what hosted clients want)

This server does not need to be an OAuth provider, and isn't one. Since the 2025-06-18 MCP spec, an MCP server is a resource server: it names the authorization server it trusts and validates the tokens that server issues. Login, consent and token issuance belong to your IdP — Cloudflare Access, WorkOS, Auth0, Descope, Stytch, Keycloak, anything with OIDC discovery.

MCP_TRANSPORT=http \
MCP_PUBLIC_URL=https://mcp.example.com \
MCP_OAUTH_ISSUER=https://your-idp.example.com \
CLICKUP_API_TOKEN=pk_... node build/v4/index.js

That is the whole configuration. The server then:

  • serves RFC 9728 Protected Resource Metadata at /.well-known/oauth-protected-resource, naming your issuer, unauthenticated;

  • answers an unauthenticated request with 401 and a WWW-Authenticate header pointing at that document, which is how a client discovers where to log in;

  • discovers your issuer's signing keys via /.well-known/openid-configuration (or RFC 8414), or uses MCP_OAUTH_JWKS_URL if you set it;

  • validates every token: RS256 pinned, signature against the issuer's JWKS, exp, nbf, iss, and aud — the token must name this server.

That last check is the one that matters. Without it, a token your IdP minted for some other service could be replayed here. It's why MCP_PUBLIC_URL is required rather than inferred: the expected audience must never come from the request, because the Host header is set by the caller.

MCP_AUTH_TOKEN becomes optional once an issuer is configured — an OAuth-only deployment doesn't need a shared password it never uses.

Note on Dynamic Client Registration. The 2026-07-28 spec deprecated DCR in favour of Client ID Metadata Documents. That change lands on authorization servers and clients; a resource server is unaffected either way, which is a good reason to delegate rather than roll your own AS.

The claude.ai connector caveat

Claude's custom connector UI accepts OAuth fields only — Authorization URL, Token URL, Client ID, Client Secret. There is no field for a static bearer token or a custom header (#112, #411). So:

  • With OAuth configured, connect it as a normal custom connector. This is the intended path.

  • Without OAuth, the only way in is the token-in-URL form, /mcp/<token>, enabled with MCP_ALLOW_TOKEN_IN_PATH=1. It works, but it puts a credential in a URL where proxies log it, which is why strict mode refuses it. Treat it as a workaround, not a deployment.

Cloudflare Access (optional third auth mode)

Set CF_ACCESS_TEAM_DOMAIN and CF_ACCESS_AUD and the server validates the Cf-Access-Jwt-Assertion header Access puts on every request it forwards: RS256 against the team JWKS, plus exp, iss, and aud. Both Access flows validate through one path — a browser login carries email, a service token carries common_name.

This is defence in depth. A request reaching the origin without passing through Access — a tunnel misconfiguration, a second ingress, something on the host's network — cannot impersonate an Access-authenticated caller. It fails closed: alg is pinned to RS256 (so alg: none and HS256 confusion are rejected), an unreachable JWKS denies rather than bypasses, and the JWKS URL comes from configuration, never from the token.

Bearer auth keeps working. A request is authorized by a valid Access JWT or a valid bearer token, so header-capable agents need no changes.

The origin does not serve /.well-known/oauth-* — with Managed OAuth enabled, Access is the authorization server and serves discovery at the edge.

Strict mode (MCP_STRICT_ENV=1)

The posture for an unattended deployment. Secrets must come from the environment, the server never invents or persists a credential, and it exits 1 with an actionable message rather than starting misconfigured. It also refuses the URL-path token form, which lands the credential in proxy access logs.

This matters because the .env-file lookup deliberately outranks process.env — a desktop host rewrites its own config file from memory on quit, so the file has to win there. On a server that precedence is backwards: a stray .env in the working directory would silently outrank the systemd unit. Strict mode turns the lookup off.

See deploy/DEPLOY.md for the full recipe: VPS setup script, hardened systemd unit, Cloudflare Tunnel, and connecting it to Claude.

Upgrading from 3.x

The tool names are entirely different — 4.x is a rewrite, not a rename. Anything holding hard-coded 3.x tool names (saved prompts, agent instructions, scripts) needs updating.

The mapping is mostly many-to-one:

3.x

4.x

workspaces_list, spaces, lists_search, lists_list_in_space

tree

tasks_list

find

tasks_get

task

tasks_create, tasks_create_bulk

create

tasks_update, tasks_delete, tasks_move, tasks_link, tags_assign, dependencies

update

lists_create, lists_update, lists_delete, folders_*

lists

statuses list, tags list, custom_fields list

meta

users_*, guests_*, groups, workspaces_seats_get

people

time_*

time

*_comments_*, comments_*

comment

checklists_*

checklist

channels*

chat

Not carried over: project_intelligence (the eight local analysis reports) and reminders_create. Status management — creating, renaming, reordering statuses — is also absent; meta reads statuses but does not change them. If you need any of these, run 3.x.

Running 3.x

3.x is still built and shipped from this repo:

npm run start:v3       # via the package script
node build/index.js    # the 3.x entry point directly

Point an MCP client at build/index.js instead of build/v4/index.js to keep using it.

The reference systemd unit in deploy/ is deliberately still pinned to 3.x, because a running service should not change major version because a package default moved underneath it. Migrate it by pointing ExecStart at build/v4/index.js and setting MCP_PROFILE explicitly.

Known ClickUp API limitations

Not bugs here — the API genuinely lacks these, and this server reports the limit rather than faking around it.

  • Tasks cannot be moved between lists. POST /list/{dest}/task/{id} returns 200 {} and does nothing without the "Tasks in Multiple Lists" ClickApp; PUT with list_id is silently ignored; /move 404s. update's move path reads the task back and fails loudly rather than reporting a move that didn't happen.

  • Attachments have no list endpoint — task reads them off the task object. Uploads are multipart-only, capped at 25MB.

  • Docs cannot be renamed or deleted, and pages cannot be deleted.

  • Custom field definitions can be listed and created, not edited or deleted.

  • Date custom fields require Unix milliseconds; YYYY-MM-DD is rejected by ClickUp for those. Task due_date/start_date accept both and are converted here.

  • Status and tag names are stored lower-cased; matching here is case-insensitive throughout.

  • Lists override their space's statuses constantly, so "what statuses are valid" is a per-list question. meta answers it per list.

  • ClickUp answers an invalid enum with HTTP 500, so enums are validated client-side before sending.

  • The rate limit is roughly 100 requests/minute per token, shared across everything using it. whoami reports the live budget; the server paces itself against the x-ratelimit-* headers.

Webhook receiver (optional)

Process ClickUp webhook events without external infrastructure:

WEBHOOK_PORT=3001 WEBHOOK_SECRET=your_secret node build/webhook-receiver/index.js
  • HMAC-SHA256 validation over the raw request body; when a secret is configured, unsigned requests are rejected

  • Structured event parsing — type, object, operation, changes, user, timestamp

  • Optional forwarding to a callback URL (WEBHOOK_FORWARD_URL)

  • Pure Node.js http, zero extra dependencies

Development

npm install
npm run build
npm test          # 354 tests, mocked HTTP — no token needed
npm run smoke     # live CRUD walk (needs CLICKUP_API_TOKEN; creates and
                  # deletes its own sandbox in your workspace)

Architecture notes for 4.x live in src/v4/README.md; the design rationale and measurements are in V4-PLAN.md.

Debugging a fix that "didn't work"

Call whoami. It reports the running build's version and stamp. MCP hosts spawn their own server process at session start and hold it, so a rebuild does not reach an already-running session — if the stamp predates your change, restart the host app. This accounted for several phantom bug reports before the tool existed.

License

MIT — see LICENSE. Fork of nsxdavid/clickup-mcp-server by David Whatley.

Available Tools

87 tools
attachmentsA

Manage attachments on ClickUp tasks. Use "list" to see existing attachments, "create" to attach by URL, or "upload" to upload a file (base64-encoded).

Inputs: action (required), task_id (required), url, file_data, +1 more.

channelsB

Manage ClickUp chat channels. Use action to list, get, create, update, delete, create DM, search, view stats, or mark as read.

Inputs: action (required), name, type, user_ids, +4 more.

channels_membersB

Manage members of a ClickUp chat channel. Use action to list members, list followers, add, or remove.

Inputs: action (required), channel_id (required), user_id.

channels_messagesB

Manage messages in a ClickUp chat channel. Use action to list, send, update, delete, manage replies, reactions, tagged users, unread count, or search messages.

Inputs: action (required), limit, query, cursor, +7 more.

checklists_createA

Create a new checklist in a ClickUp task. Returns the created checklist details.

Inputs: name (required), task_id (required).

checklists_deleteA

Delete a checklist from a ClickUp task. Removes the checklist and all its items.

Inputs: checklist_id (required).

checklists_items_createA

Create a new item in a ClickUp checklist. Supports optional assignee and resolved status.

Inputs: name (required), checklist_id (required), assignee, resolved.

checklists_items_deleteA

Delete an item from a ClickUp checklist.

Inputs: checklist_id (required), checklist_item_id (required).

checklists_items_updateA

Update an existing ClickUp checklist item's properties including name, assignee, and resolved status.

Inputs: checklist_id (required), checklist_item_id (required), name, assignee, +1 more.

checklists_updateA

Update an existing ClickUp checklist's name.

Inputs: name (required), checklist_id (required).

comments_deleteB

Delete a comment from ClickUp.

Inputs: comment_id (required).

comments_replies_createA

Create a new threaded comment (reply) to a parent comment. Supports notification settings.

Inputs: comment_id (required), comment_text (required), notify_all.

comments_replies_listA

Get threaded comments (replies) for a parent comment. Returns comment details with pagination support.

Inputs: comment_id (required), start, start_id.

comments_updateA

Update an existing ClickUp comment's properties including text, assignee, and resolved status.

Inputs: comment_id (required), comment_text (required), assignee, resolved.

custom_fieldsA

List, create, update, or delete custom field definitions. Use "list" to get field schemas, "create" to add a field, "update" to modify it, or "delete" to remove it.

Inputs: action (required), name, type, options, +4 more.

custom_fields_valuesA

Get, set, remove, or bulk-set custom field values on ClickUp tasks. Use "get" to read all field values on a task, "set" to write a value, "remove" to clear it, or "bulk_set" to set values across multiple tasks in one operation. For dropdown/labels fields, pass the option UUID (get UUIDs from custom_fields tool with action="list"). For date fields, pass a Unix timestamp in milliseconds. For people fields, pass {add:[user_ids], rem:[user_ids]}. For location fields, pass {lat:number, lng:number, formatted_address?:string}.

Inputs: action (required), updates (required), value, task_id, +2 more.

dependenciesB

Manage task dependencies. Use action to create, get, update, delete, view dependency graph, check/resolve conflicts, view timeline impact, or bulk create.

Inputs: action (required), task_id, depends_on, dependencies, +3 more.

dependencies_workspaceB

Manage dependencies at the workspace level. Use action to list all dependencies, view stats, or export/import the dependency graph.

Inputs: action (required), workspace_id (required), data, page.

docsB

Manage ClickUp docs and pages. Use action to get, list, create, update docs, or list, create, update, delete pages, or search docs.

Inputs: action (required), name, limit, query, +13 more.

folders_createA

Create a new folder in a ClickUp space with the specified name.

Inputs: name (required), space_id (required).

folders_deleteA

Delete a folder from ClickUp. Removes the folder and its contents.

Inputs: folder_id (required).

folders_updateA

Update an existing ClickUp folder's name.

Inputs: name (required), folder_id (required).

goals_createA

Create a new goal in a ClickUp workspace.

Inputs: name (required), workspace_id (required), due_date.

goals_deleteA

Delete a ClickUp goal by ID.

Inputs: goal_id (required).

goals_getA

Get details of a specific ClickUp goal by ID.

Inputs: goal_id (required).

goals_key_results_createB

Create a key result under a ClickUp goal.

Inputs: name (required), type (required), goal_id (required), unit, +1 more.

goals_key_results_deleteB

Delete a key result from a ClickUp goal.

Inputs: goal_id (required), key_result_id (required).

goals_key_results_updateA

Update a key result under a ClickUp goal.

Inputs: goal_id (required), key_result_id (required), name.

goals_listA

Get all goals in a ClickUp workspace.

Inputs: workspace_id (required).

goals_updateA

Update a ClickUp goal name and/or due date.

Inputs: goal_id (required), name, due_date.

groupsA

Manage user groups in a ClickUp workspace. Use action to list, create, update, or delete groups.

Inputs: action (required), workspace_id (required), name, group_id.

guests_attachB

Grant a guest access to a specific location (task, list, or folder).

Inputs: guest_id (required), location_id (required), location_type (required), permission_level.

guests_detachA

Remove a guest's access from a task, list, or folder.

Inputs: guest_id (required), location_id (required), location_type (required).

guests_getB

Get details about a specific guest in the workspace.

Inputs: guest_id (required), workspace_id (required).

guests_inviteB

Invite a guest to a ClickUp workspace.

Inputs: email (required), workspace_id (required), can_edit_tags.

guests_removeB

Remove a guest from the workspace entirely.

Inputs: guest_id (required), workspace_id (required).

guests_updateB

Update a guest's permissions or details in the workspace.

Inputs: guest_id (required), workspace_id (required), can_edit_tags.

lists_comments_createA

Create a new comment on a ClickUp list. Supports optional assignee and notification settings.

Inputs: list_id (required), comment_text (required), assignee, notify_all.

lists_comments_listA

Get comments for a ClickUp list. Returns comment details with pagination support.

Inputs: list_id (required), start, start_id.

lists_createC

Create a new list in a ClickUp folder or space with the specified name.

Inputs: name (required), container_id (required), container_type (required).

lists_create_from_template_in_folderA

Create a new list in a ClickUp folder using an existing template.

Inputs: name (required), folder_id (required), template_id (required).

lists_create_from_template_in_spaceA

Create a new list in a ClickUp space using an existing template.

Inputs: name (required), space_id (required), template_id (required).

lists_create_in_spaceA

Create a new list directly in a ClickUp space without placing it in a folder.

Inputs: name (required), space_id (required).

lists_deleteA

Delete a list from ClickUp. Removes the list and its tasks.

Inputs: list_id (required).

lists_getA

Get details about a specific ClickUp list including its name and content.

Inputs: list_id (required).

lists_list_in_spaceA

Get lists that are not in any folder within a ClickUp space.

Inputs: space_id (required).

lists_members_listA

Get members assigned to a ClickUp list. Returns user IDs, usernames, and emails.

Inputs: list_id (required).

lists_updateB

Update an existing ClickUp list's name.

Inputs: name (required), list_id (required).

project_intelligenceA

Analyze ClickUp project data and return actionable insights. Use "health" for a status overview, "bottlenecks" to find stuck workflows, "velocity" to measure completion rate, "dependencies" to trace dependency chains, "sprint" to check sprint readiness, "workload" to view team distribution, "risk" to surface tasks needing attention, or "time_report" for time tracking summaries. Every action handles edge cases.

Inputs: action (required), list_id (required), end_date, start_date.

remindersB

Manage personal reminders in ClickUp. Use action "list" to search/filter, "create" to add, or "update" to modify or complete.

Inputs: action (required), limit, title, cursor, +7 more.

spacesA

Get spaces from a workspace, or details of a specific space. Omitting space_id lists all spaces in the workspace.

Inputs: workspace_id (required), space_id.

statusesA

Manage custom statuses on ClickUp lists. Use action to list current statuses, create, update, delete, or reorder them.

Inputs: action (required), list_id (required), status_name, all_statuses, +2 more.

tagsB

Manage space tags. Use action to list, create, update, or delete tags in a space.

Inputs: action (required), space_id (required), name, tag_bg, +2 more.

tags_assignA

Add a tag to a ClickUp task. The tag must already exist in the space.

Inputs: task_id (required), tag_name (required).

tags_unassignB

Remove a tag from a ClickUp task.

Inputs: task_id (required), tag_name (required).

tasks_comments_createA

Create a new comment on a ClickUp task. Supports optional assignee and notification settings.

Inputs: task_id (required), comment_text (required), assignee, notify_all.

tasks_comments_listA

Get comments for a ClickUp task. Returns comment details including text, author, and timestamps.

Inputs: task_id (required), start, start_id.

tasks_createB

Create a new task in a ClickUp list with specified properties like name, description, assignees, status, and dates.

Inputs: name (required), list_id (required), tags, parent, +11 more.

tasks_create_bulkA

Create multiple tasks in a ClickUp list in a single operation. More efficient than creating tasks individually. Supports up to 50 tasks per call.

Inputs: tasks (required), list_id (required), continue_on_error.

tasks_deleteA

Delete a ClickUp task permanently.

Inputs: task_id (required).

tasks_getA

Get detailed information about a specific ClickUp task. Returns comprehensive task data including description, assignees, status, and dates.

Inputs: task_id (required), include_subtasks.

tasks_listB

Get tasks from a ClickUp list. Returns task details including name, description, assignees, and status.

Inputs: list_id (required), page, reverse, order_by, +2 more.

tasks_members_listB

Get members assigned to a ClickUp task. Returns user IDs, usernames, and emails.

Inputs: task_id (required).

tasks_updateC

Update an existing ClickUp task's properties including name, description, assignees, status, and dates.

Inputs: task_id (required), name, status, due_date, +9 more.

tasks_update_bulkA

Update multiple existing ClickUp tasks in a single operation. Each entry must include a task_id and the fields to update. Can batch-change status across tasks (set status per task), batch-reassign (set assignees array per task), or batch-add tags (set tags array per task). Supports up to 50 tasks per call.

Inputs: updates (required), continue_on_error.

templatesA

Get available templates in a ClickUp workspace. Scope type determines which templates are returned (task, list, or folder templates).

Inputs: scope_type (required), workspace_id (required), scope_id.

time_entries_listA

Get time entries for a ClickUp team/workspace. Supports filtering by task, date range, and assignees.

Inputs: team_id (required), task_id, assignee, end_date, +2 more.

time_entry_createA

Create a new manual time entry for a task. Requires team_id, task_id, and start time. Optional duration or end_time.

Inputs: start (required), task_id (required), team_id (required), tags, +4 more.

time_entry_deleteB

Delete a time entry by ID.

Inputs: team_id (required), entry_id (required).

time_entry_updateB

Update an existing time entry. Supports changing start, duration, end time, description, and billable status.

Inputs: team_id (required), entry_id (required), tags, start, +4 more.

time_tracking_currentA

Get the currently running time entry, if any. Returns the active time entry details or an empty response.

Inputs: team_id (required).

time_tracking_startA

Start the timer on a ClickUp task. Only one timer can run at a time. Supports optional description and billable status.

Inputs: team_id (required), tags, task_id, billable, +1 more.

time_tracking_stopA

Stop the currently running timer. Returns the completed time entry details.

Inputs: team_id (required), tags, description.

users_inviteA

Invite a user to a ClickUp workspace by email.

Inputs: email (required), workspace_id (required), admin.

users_listA

List all users in a ClickUp workspace.

Inputs: workspace_id (required).

users_removeB

Remove a user from a ClickUp workspace.

Inputs: user_id (required), workspace_id (required).

users_updateC

Update a user's details in the workspace.

Inputs: data (required), user_id (required), workspace_id (required).

viewsB

Manage ClickUp views and view configurations. Use action to list, create, get, update, delete views, set filters/grouping/sorting/settings, duplicate, manage sharing, or get tasks in a view.

Inputs: action (required), name, page, type, +14 more.

views_comments_createB

Create a new comment in a ClickUp chat view. Supports notification settings.

Inputs: view_id (required), comment_text (required), notify_all.

views_comments_listA

Get comments for a ClickUp chat view. Returns comment details with pagination support.

Inputs: view_id (required), start, start_id.

webhooksA

Manage ClickUp webhooks and parse incoming webhook events. Use action to list, create, update, delete webhooks, or process an incoming payload with optional HMAC validation.

Inputs: action (required), events, secret, status, +6 more.

workspaces_listA

Get a list of all ClickUp workspaces accessible to the authenticated user. Returns workspace IDs, names, and metadata.

Inputs: no named parameters.

workspaces_seats_getA

Get information about seats (user licenses) in a ClickUp workspace. Returns details about seat allocation and availability.

Inputs: workspace_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 87 tools

    Disambiguation3/5

    Many tools are entity-specific (tasks_, lists_, comments_) which helps, but there are overlapping creation tools like lists_create and lists_create_in_space, and multiple comment tools (tasks_comments_create vs comments_replies_create) that could confuse an agent. The generic noun tools (docs, spaces, views) also require reading descriptions to determine actions.

    Naming Consistency4/5

    Most tools follow a noun_verb pattern (tasks_create, lists_update, users_invite), but there are inconsistencies: time_tracking_current, lists_search, and single-word manager tools (docs, views, tags) that use an action parameter instead of a verb in the name.

    Tool Count2/5

    87 tools is far beyond the typical well-scoped range. While ClickUp is a broad platform, the sheer number requires significant navigation and increases the chance of selecting the wrong tool. Some consolidation via action parameters exists, but the count is still excessive.

    Completeness4/5

    The tool surface covers CRUD for tasks, lists, folders, comments, checklists, goals, time entries, users, guests, channels, and more, along with bulk operations and cross-cutting features like custom fields and dependencies. Minor gaps exist (no folder get/list, no space deletion) but overall coverage is thorough.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      An enhanced Model Context Protocol server that enables AI assistants to interact with ClickUp workspaces, supporting task relationships, comments, checklists, and workspace management through natural language.
      0
      2
      -
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to interact with ClickUp workspaces, allowing task creation, management, and workspace organization through natural language commands.
      21
      1,086 npm
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A comprehensive MCP server for the ClickUp API exposing 166 tools to manage Spaces, Folders, Lists, Tasks, Docs, and more, enabling LLMs to read and drive a ClickUp Workspace.
      100
      46 PyPI
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Complete Model Context Protocol server for ClickUp, enabling interaction with tasks, spaces, lists, docs, goals, time tracking, and more through 93 tools and 18 React MCP apps.
      MIT