ClickUp

Name: ClickUp MCP Server
Availability: InStock
Author: ClickUp

HIPAA CompliantSOC2 ReadyISO 27001 Ready

Productivity35 tools

Run your ClickUp workspace from an AI assistant: create and update tasks, write Docs, post to Chat, and log time. Anthropic lists 35 tools — 8 create, 5 update, none that delete. Two bulk writers can rewrite many tasks in one call.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 19 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect ClickUp via MCP

https://mcp.clickup.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect ClickUp once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

ClickUp Tools & Capabilities (35)

clickup_search

clickup_get_workspace_hierarchy

clickup_create_task

clickup_get_task

clickup_update_task

clickup_get_task_comments

clickup_create_task_comment

clickup_attach_task_file

clickup_create_bulk_tasks

clickup_update_bulk_tasks

clickup_get_workspace_tasks

clickup_get_task_time_entries

clickup_start_time_tracking

clickup_stop_time_tracking

clickup_add_time_entry

clickup_get_current_time_entry

clickup_create_list

clickup_create_list_in_folder

clickup_get_list

clickup_update_list

clickup_create_folder

clickup_get_folder

clickup_update_folder

clickup_add_tag_to_task

clickup_remove_tag_from_task

clickup_get_workspace_members

clickup_find_member_by_name

clickup_resolve_assignees

clickup_get_chat_channels

clickup_send_chat_message

clickup_create_document

clickup_list_document_pages

clickup_get_document_pages

clickup_create_document_page

clickup_update_document_page

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

The directory lists 35 tools; ClickUp documents about 48. The thirteen-odd extras include the only destructive tool on the surface. Read ClickUp's Supported Tools page, not just the listing.
ClickUp's two MCP pages contradict each other on deletion. The developer overview says deletion tools were withheld as a safety measure; the Supported Tools page lists Delete task. Do not treat "no delete" as a guarantee.
Bulk writes have no documented ceiling. Neither the tool docs nor the API reference states a maximum tasks-per-call for the two bulk tools, nor whether a partial failure rolls back.
No dry run, no undo. Nothing documented previews a bulk change or reverses one.
The directory record has no permissions label. Not "read only", not "read and write" — absent, over a surface with twenty write tools.
We could not verify tool behaviour ourselves. The endpoint returns 401 to an anonymous handshake, so no safety annotations were readable. The verb census comes from names and ClickUp's descriptions.
Time-tracking writes reach financial records. Three tools start, stop and backdate time entries. ClickUp documents no approval step and no distinction between human and agent entries.
Permission scope is your account's scope. ClickUp states the assistant can only do what you can do, and documents no way to narrow a connection below that — to a single Space, for example.
Rate limits are per workspace, not per user, and ClickUp's two pages give different numbers. Without the Everything AI add-on, the help centre lists 100 / 300 / 1,000 / 2,500 / 5,000 calls per rolling 24 hours for Free / Unlimited / Business / Business Plus / Enterprise, while the developer overview lists 50 for Free and 300 for Unlimited and above. Both agree the limit is workspace-wide, that every connected client draws from the same pool, and that every request counts — including ordinary reads.
The 24-hour window is rolling and cannot be reset. It starts at your first request. Exceeded calls return a 429 rate-limit error until the window rolls.
With the Everything AI add-on the model changes entirely — limits become the public API's per-minute, per-token quotas: 100 for Free, Unlimited and Business, 1,000 for Business Plus, 10,000 for Enterprise. The daily cap no longer applies.
Connected Search is out of reach. ClickUp states MCP cannot search external apps connected to your workspace.
There is no usage meter. ClickUp states you cannot currently monitor how many MCP calls your workspace has used — so you find the daily cap by hitting it.
It is a public beta. ClickUp says future restrictions may apply and that limits may change.

Frequently asked questions

Not through the 35 tools Anthropic lists — none of them delete anything. ClickUp's developer overview states it has not added deletion tools as a safety measure. But ClickUp's own Supported Tools page, updated later, does list a Delete task tool. The two ClickUp pages disagree, so treat deletion as possible until ClickUp reconciles them.

Anthropic's directory snapshot lists 35. By verb that is 15 read tools, 8 create, 5 update, 3 time-tracking writes, and 4 others that attach files, tag, untag and post chat messages. ClickUp's own documentation describes roughly 48, so the directory listing covers about three-quarters of the documented surface.

ClickUp does not document a limit. Its Supported Tools page describes the tool as modifying multiple tasks simultaneously and gives moving a whole List's tasks between statuses as the example, but names no maximum, no batching rule and no transactional guarantee. Whether a partly failed bulk call rolls back or leaves half the tasks changed is unstated. Scope the target List before calling.

Yes. ClickUp states plainly that your AI assistant can only perform actions in ClickUp that you have permission to do. That makes the connecting user's role the real boundary, not the connector. An agent connected by a workspace owner reaches what an owner reaches, so connect with the narrowest account that can still do the job.

Yes. Three of the 35 tools write to time tracking: start a timer, stop it, and add a historical entry with a start and end time or a duration. ClickUp's example is logging two hours against a task for yesterday. In organisations where timesheets feed client billing or payroll, that is a financial record an agent can write.

All of them. ClickUp documents the MCP server as available on every plan, and states no admin action is needed inside ClickUp before connecting an external tool. What changes by plan is throughput. Without the Everything AI add-on, usage is capped per rolling 24 hours by plan tier; with it, limits match the public API's per-minute quotas.

Yes. ClickUp's protected-resource descriptor advertises exactly two scopes, read and write, verified live on 2026-08-19. That is a real split, and unusually clear for a 35-tool surface. What the descriptor does not reveal is whether a client can request read alone, or whether the consent screen grants both together. Check the screen before approving.

Sources

ClickUp help centre, "What is ClickUp MCP?" — https://help.clickup.com/hc/en-us/articles/33335772678423-What-is-ClickUp-MCP (fetched 2026-08-19 via the Zendesk Help Center article API at /api/v2/help_center/en-us/articles/33335772678423.json; article updated 2026-08-18. This is the URL Anthropic's directory publishes) · retrieved 2026-08-19
ClickUp developer docs, "ClickUp's MCP Server" — https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server (fetched 2026-08-19 as Markdown via the .md suffix, which the site itself advertises; page updated 2026-08-13. Source of the public-beta label, the all-plans statement and the deletion-as-safety-measure answer) · retrieved 2026-08-19
ClickUp developer docs, "Supported Tools" — https://developer.clickup.com/docs/mcp-tools (fetched 2026-08-19 as Markdown; page updated 2026-03-19. Source of the ~48 documented tools, the permission-inheritance statement and the Delete task entry) · retrieved 2026-08-19
ClickUp developer docs, "MCP Server Setup Instructions" — https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server-1 (fetched 2026-08-19; page updated 2026-08-14. Source of the connect command and the ChatGPT-side admin restriction) · retrieved 2026-08-19
ClickUp developer docs, "Rate limits" — https://developer.clickup.com/docs/rate-limits (fetched 2026-08-19; source of the per-minute public API quotas) · retrieved 2026-08-19
ClickUp developer docs machine index — https://developer.clickup.com/llms.txt (fetched 2026-08-19; used to enumerate MCP pages rather than guess sub-URLs). help.clickup.com/llms.txt returns 404; clickup.com/llms.txt returns 200 but is marketing copy with no MCP detail · retrieved 2026-08-19
help.clickup.com/robots.txt is a stock Zendesk file allowing /hc/ article paths, and clickup.com/robots.txt opens with User-agent: * / Allow: /. Neither carries a Content-Signal header or directive (both fetched 2026-08-19) · retrieved 2026-08-19
Live RFC 9728 protected-resource descriptors — https://mcp.clickup.com/.well-known/oauth-protected-resource (200, 471 bytes) and https://mcp.clickup.com/.well-known/oauth-protected-resource/mcp (200, 475 bytes; differ only in the resource value). The path-insert form https://mcp.clickup.com/mcp/.well-known/oauth-protected-resource returns 404 (all fetched 2026-08-19) · retrieved 2026-08-19
Live RFC 8414 authorization-server metadata — https://mcp.clickup.com/.well-known/oauth-authorization-server (fetched 2026-08-19; the path-append form returns 404) · retrieved 2026-08-19
Live anonymous probe — 2026-08-19: an unauthenticated initialize POST to the endpoint returns HTTP 401 with www-authenticate: Bearer realm="MCP Server", error="invalid_token", resource_metadata="https://mcp.clickup.com/.well-known/oauth-protected-resource/mcp". We did not authenticate and called no tools · retrieved 2026-08-19
Community ClickUp MCP servers, named only to distinguish them from the official hosted one — https://github.com/taazkareem/clickup-mcp-server (fetched 2026-08-19) · retrieved 2026-08-19
Anthropic connector directory — https://claude.ai/directory/aa5a2bca-4004-49ea-bc2b-978162587a3a (snapshot 2026-08-16; source of the 35 tool names, the partner tier, and the absent permissions field) · retrieved 2026-08-16