clickup

# ClickUp Use this skill when working with ClickUp — fetching tasks, creating/updating issues, managing lists, or configuring the ClickUp MCP server. ## Three Ways to Interact with ClickUp ### 1. Official ClickUp MCP Server (OAuth only — limited Hermes support) The official ClickUp MCP server is at `https://mcp.clickup.com/mcp` but uses **OAuth** (browser-based authorization), **not** personal API tokens. This means: - ❌ **Personal API tokens (`pk_...`) are rejected** — server returns `"Failed to decode JWE header"` - ❌ **Bearer tokens from OAuth app** — also rejected unless you've gone through the full OAuth device-code flow - ✅ **Works in Claude Desktop, Cursor, VS Code** — these clients support the interactive OAuth redirect flow - ⚠️ **Does NOT work with Hermes HTTP MCP transport** — Hermes supports only static headers, not OAuth authorization flows For environments that support OAuth MCP (like Claude Desktop), add as: ```yaml mcp_servers: clickup: url: "https://mcp.clickup.com/mcp" timeout: 120 # No headers needed — OAuth is handled by the client at connection time ``` ### 2. REST API (recommended for Hermes) Use the ClickUp REST API directly via `curl` or Python `urllib` — no MCP server needed: ```bash # Personal API token in Authorization header curl -s "https://api.clickup.com/api/v2/task/GYMED-425?custom_task_ids=true&team_id=$CLICKUP_TEAM_ID" \ -H "Authorization: $CLICKUP_API_TOKEN" | python3 -m json.tool ``` Set env vars: ``` CLICKUP_API_T...