ClickUp MCP for AI AssistantsSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Model Context Protocol (MCP) server enabling AI assistants to interact with ClickUp workspaces. Get complete task context with comments and images, search across projects, create and update tasks, collaborate through comments, and track time - all through natural language.
This MCP vs Official ClickUp MCP
See also: Official ClickUp MCP Documentation
e80a6e65d407OBSERVED · 2026-10-12Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add clickup-mcp --env CLICKUP_API_KEY=${CLICKUP_API_KEY} -- npx -y @hauptsache.net/[email protected]{
"mcpServers": {
"clickup-mcp": {
"command": "npx",
"args": [
"-y",
"@hauptsache.net/[email protected]"
],
"env": {
"CLICKUP_API_KEY": "${CLICKUP_API_KEY}"
}
}
}
}Exposed tools (14)
14 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
addComment | read | |
createDocumentOrPage | read | |
createTask | read | |
createTimeEntry | read | |
editComment | read | |
getListInfo | read | |
getTaskById | read | |
getTimeEntries | read | Gets time entries for a specific task or all user |
readDocument | read | |
searchSpaces | read | |
searchTasks | read | |
updateDocumentPage | read | |
updateListInfo | read | |
updateTask | read |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (5 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (3)
.mcpbignore
fuse.js, remark-gfm, remark-parse, unified, zod, @anthropic-ai/mcpb, @types/mdast, @types/node
This MCP server can be configured using environment variables. In the desktop extension (`.mcpb`) installer, the API key, team ID, primary language, upload size limit and comment edit window are offer
Gates applied: no_behavioural_pass.
e80a6e65d407full audit observations/trust-audit/mcp-server/hauptsachenet__clickup-mcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | e80a6e65d407 | SAFE | B | 89 | first audit |
Questions
What tools does @hauptsache.net/clickup-mcp expose?
14 in total: 14 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is @hauptsache.net/clickup-mcp safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does @hauptsache.net/clickup-mcp need?
It reads CLICKUP_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does @hauptsache.net/clickup-mcp run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @hauptsache.net/clickup-mcp at 1.9.0.
How current is this page?
The grade is for one exact copy of the source (e80a6e65d407), read on 2026-10-12. The repository is watched and re-audited when it changes.