MCP server for the ClickUp public API (v2 + v3, stdio).
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"amazing-clickup-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ClickUp MCP Server (amazing-clickup-mcp) A comprehensive [Model Context Protocol](https://modelcontextprotocol.io) server for the [ClickUp public API](https://developer.clickup.com/reference) (v2 + v3), built on the official [MCP Python SDK](https://github.com/modelcontextprotocol/python-sdk) (FastMCP, stdio transport). It exposes **166 tools** covering nearly the entire ClickUp surface — Spaces, Folders, Lists, Views, Docs, Tasks, Comments, Checklists, Tags, Custom Fields, Time Tracking, Goals, Members, Guests, Webhooks, Chat, and more — so an LLM can read and drive a ClickUp Workspace on your behalf. > The PyPI distribution and console script are both **`amazing-clickup-mcp`** (the bare > `clickup-mcp` name is taken on PyPI by an unrelated package). Always run > `uvx amazing-clickup-mcp` — never `uvx clickup-mcp`. ## Features - **Full API coverage (166 tools).** v2 and v3 endpoints across 22 resource groups — Spaces, Folders, Lists, Views, Docs, Tasks, Comments, Checklists, Tags, Custom Fields, Time Tracking 2.0, Relationships, Attachments, Goals, Members & User Groups, Guests, Users, Webhooks, Workspace admin, Chat channels, Chat messages, and a health check. - **Statuses managed via payloads.** ClickUp has no dedicated statuses endpoint; create and update Space/Folder/List objects with `statuses`/`override_statuses` payloads. - **Docs created in-place (v3).** Create a Doc directly in its final Space/Folder/List/ Everything location — no drag-later. - **Dual-format responses.** Markdown for humans and LLMs (default) or JSON for programmatic use, selectable per call via `response_format`. - **Strict input validation.** One pydantic v2 model per tool (`extra="forbid"`, field-level constraints) so malformed calls fail fast with a clear message. - **Uniform error mapping.** 400/401/403/404/429, timeouts, and connection errors are normalized into readable strings that surface ClickUp `err`/`ECODE` details and rate-limit guidance. - **stdio-onl…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.