A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Clickup is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read teams, spaces, lists and tasks; create, update and comment on tasks and track time.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http usefulapi-clickup-mcp https://clickup.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# clickup_get_authorized_user, clickup_list_workspaces, clickup_list_spaces and 11 more
Clickup costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http usefulapi-clickup-mcp https://clickup.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get the user associated with the current ClickUp API token. ClickUp REST: GET /user.
No parameter schema on file.
List the workspaces (the ClickUp API calls these "teams") the token can access — their ids are the team_id used by other tools. ClickUp REST: GET /team.
No parameter schema on file.
List spaces in a workspace (team). ClickUp REST: GET /team/{team_id}/space.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_id | string | yes | The workspace (team) id. |
| archived | boolean | no | Include archived items — serialized as archived=true/false. Default false. |
List folders in a space. ClickUp REST: GET /space/{space_id}/folder.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| space_id | string | yes | The space id. |
| archived | boolean | no | Include archived items — serialized as archived=true/false. Default false. |
List the lists inside a folder. ClickUp REST: GET /folder/{folder_id}/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| folder_id | string | yes | The folder id. |
| archived | boolean | no | Include archived items — serialized as archived=true/false. Default false. |
List the lists that live directly in a space (not inside a folder). ClickUp REST: GET /space/{space_id}/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| space_id | string | yes | The space id. |
| archived | boolean | no | Include archived items — serialized as archived=true/false. Default false. |
Get the tasks in a list, with optional filters and pagination. ClickUp REST: GET /list/{list_id}/task.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list id. |
| archived | boolean | no | Include archived items — serialized as archived=true/false. Default false. |
| page | integer | no | 0-indexed page number for pagination. |
| order_by | string | no | Sort field, e.g. 'created', 'updated', 'due_date', 'id'. |
| reverse | boolean | no | Reverse the sort order (serialized true/false). |
| subtasks | boolean | no | Include subtasks (serialized true/false). |
| statuses | array | no | Filter by status names (repeated statuses[] params), e.g. ["open","in progress"]. |
| include_closed | boolean | no | Include closed tasks (serialized true/false). |
| assignees | array | no | Filter by assignee user ids (repeated assignees[] params). |
| due_date_gt | integer | no | Only tasks due after this Unix time in ms. |
| due_date_lt | integer | no | Only tasks due before this Unix time in ms. |
Get a single task by id. ClickUp REST: GET /task/{task_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | string | yes | The task id. |
| include_subtasks | boolean | no | Include the task's subtasks (serialized true/false). |
Get the comments on a task. ClickUp REST: GET /task/{task_id}/comment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | string | yes | The task id. |
Get the comments on a list. ClickUp REST: GET /list/{list_id}/comment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list id. |
Search/filter tasks across a whole workspace (team), optionally scoped to spaces/folders/lists. ClickUp's "Get Filtered Team Tasks". ClickUp REST: GET /team/{team_id}/task.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_id | string | yes | The workspace (team) id. |
| page | integer | no | 0-indexed page number for pagination. |
| order_by | string | no | Sort field, e.g. 'created', 'updated', 'due_date', 'id'. |
| reverse | boolean | no | Reverse the sort order (serialized true/false). |
| statuses | array | no | Filter by status names (repeated statuses[] params), e.g. ["open","in progress"]. |
| assignees | array | no | Filter by assignee user ids (repeated assignees[] params). |
| include_closed | boolean | no | Include closed tasks (serialized true/false). |
| space_ids | array | no | Restrict to these space ids (repeated space_ids[] params). |
| project_ids | array | no | Restrict to these folder/project ids (repeated project_ids[] params). |
| list_ids | array | no | Restrict to these list ids (repeated list_ids[] params). |
| due_date_gt | integer | no | Only tasks due after this Unix time in ms. |
| due_date_lt | integer | no | Only tasks due before this Unix time in ms. |
WRITE: create a new task in a list. name is required; the list is the {list_id} path param, not a body field. ClickUp REST: POST /list/{list_id}/task.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list id to create the task in (path param, not body). |
| name | string | yes | The task name (required). |
| description | string | no | The task description / body text. |
| assignees | array | no | User ids to assign the task to (numeric). |
| status | string | no | Status name (must be a valid status in the list). |
| priority | integer | no | Task priority: 1=Urgent, 2=High, 3=Normal, 4=Low. |
| due_date | integer | no | Due date as Unix time in ms. |
| due_date_time | boolean | no | Whether due_date carries a time component (else date-only). |
| start_date | integer | no | Start date as Unix time in ms. |
| tags | array | no | Tag names to attach. |
| parent | string | no | Parent task id — set to create this task as a subtask. |
WRITE: update fields on an existing task. Only the fields you pass are changed. ClickUp REST: PUT /task/{task_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | string | yes | The task id to update (path param, not body). |
| name | string | no | New task name. |
| description | string | no | New task description / body text. |
| status | string | no | New status name (must be valid for the list). |
| priority | integer | no | Task priority: 1=Urgent, 2=High, 3=Normal, 4=Low. |
| due_date | integer | no | Due date as Unix time in ms. |
| due_date_time | boolean | no | Whether due_date carries a time component (else date-only). |
| start_date | integer | no | Start date as Unix time in ms. |
| archived | boolean | no | Archive (true) or unarchive (false) the task. |
| parent | string | no | Parent task id (re-parent as a subtask). |
WRITE: add a comment to a task. comment_text is required; the task is the {task_id} path param. ClickUp REST: POST /task/{task_id}/comment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | string | yes | The task id to comment on (path param, not body). |
| comment_text | string | yes | The comment text (required). |
| assignee | integer | no | User id to assign the comment to (numeric). |
| notify_all | boolean | no | If true, notify everyone tagged/subscribed (else just the assignee). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Clickup or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| clickup_get_authorized_user | no tags | |
| clickup_list_workspaces | no tags | |
| clickup_list_spaces | no tags | |
| clickup_list_folders | no tags | |
| clickup_list_lists | no tags | |
| clickup_list_folderless_lists | no tags | |
| clickup_get_tasks | no tags | |
| clickup_get_task | no tags | |
| clickup_get_task_comments | no tags | |
| clickup_get_list_comments | no tags | |
| clickup_search_tasks | no tags | |
| clickup_create_task | state-write | state-write: declares destructiveHint: true |
| clickup_update_task | state-write | state-write: declares destructiveHint: true |
| clickup_create_task_comment | state-write | state-write: declares destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Clickup can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.