ToolsMCP
clickup
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- taazkareem (GitHub)
- Prerequisites
- Install @taazkareem/clickup-mcp-server from npm (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.12.12 · updated
- Official links
Publisher’s description
Premium AI integration. Tasks, lists, docs, folders, time. 50+ tools. Instant setup.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.12.12, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- taazkareem (GitHub)
- Version observed
- 0.12.12
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.taazkareem%2Fclickup/versions/0.12.12
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Track tasks and tickets | Publisher description mentions “clickup”, “tasks”. | No connection check or task run. Capability is as described by the publisher. | Rule project-tracking matched: “clickup”, “tasks”. Rule project-tracking. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@taazkareem/clickup-mcp-server(npm, stdio, 2 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.taazkareem/clickup
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.