ToolsMCP
ClickUp Serviteur MCP
Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- cryogenized-spec (GitHub)
- Prerequisites
- An MCP client that supports streamable-http. No credential header is declared in the registry record.
- Current version
- 0.3.0-beta.1 · updated
- Official links
Publisher’s description
Self-hosted OAuth-protected ClickUp MCP server for tasks, comments, Docs and workspace operations.
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.3.0-beta.1, registry status active. 1 remote endpoint (streamable-http)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- cryogenized-spec (GitHub)
- Version observed
- 0.3.0-beta.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.cryogenized-spec%2Fclickup-serviteur-mcp/versions/0.3.0-beta.1
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
- Remote endpoints
https://{worker_hostname}/mcp(streamable-http)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.cryogenized-spec/clickup-serviteur-mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.