pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for clickup

Pod holds 16 of 16 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to clickup.

Most discussed

[bug] list_documents and get_document return doc URLs with /v/d/ that 404 — should be /v/dc/

Type

  • Bug Report

Prerequisites

Environment Check:

  • Node.js version: v24.14.0
  • npm version: 11.9.0
  • Operating System: macOS 26.4
  • ClickUp API key configured
  • ClickUp Team ID configured
  • MCP License Key configured Quick Self-Check:
  • I've verified my Node.js version meets requirements
  • I've checked the configuration matches the README examples

Description

list_documents and get_document return document URLs with the path /v/d/ whic

Read the thread · 2026-03-29 · closed · external user · 2 comments

ClickUp MCP returns incorrect Document URLs

MCP Server: ClickUp MCP (Premium) Reported by: Luke Sellers (luke@salvatoauctions.com) Date: 2026-03-27

Summary

When creating a document via the ClickUp MCP server using create_document, the url field in the response contains an incorrectly formatted URL that results in a 404 page when visited.

Steps to Reproduce

  1. Create a document using create_document:
{
  "name": "Facebook Strategy — Summary for Review",
  "parentType": "workspace",
  "parentId": "9017934

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/19) · 2026-03-27 · closed · external user · 2 comments

### set_task_custom_field: "type": "any" in value parameter schema is invalid JSON Schema draft 2020-12

## Type
- [x] Bug Report
- [ ] Feature Request
- [ ] Question/Other

## Prerequisites (for Bug Reports)

**Environment Check:**
- [x] Node.js version: v22.22.0 (must be v18.0.0+)
- [ ] npm version: `npm --version`
- [x] Operating System: Ubuntu Linux (6.8.0)
- [x] MCP Host: Claude Code (CLI)
- [ ] ClickUp API key configured
- [ ] ClickUp Team ID available

**Quick Self-Check:**
- [x] I've verified my Node.js version meets requirements
- [x] I've tried clearing npm cache: `npm cache clean --force

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/16) · 2026-03-15 · closed · external user · 2 comments

### MCP Server does not provide list_attachment or get_attachment tool

## Type
- [x] Bug Report
- [ ] Feature Request
- [ ] Question/Other

## Prerequisites (for Bug Reports)
<!-- Skip this section for Feature Requests -->

**Environment Check:**
- [x] Node.js version: `node --version` (must be v18.0.0+)
- [x] npm version: `npm --version`
- [x] Operating System: (e.g., macOS 14, Windows 11, Ubuntu 22.04)
- [x] ClickUp API key configured
- [x] ClickUp Team ID configured
- [x] MCP License Key configured

**Quick Self-Check:**
- [x] I've verified my Node.js version me

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/15) · 2026-03-09 · closed · external user · 3 comments

### include_timl Parameter for get_workspace_tasks

Summary: Please add include_timl (Tasks In Multiple Lists) parameter support.

The Issue: When querying by list_id, only tasks where that list is the home list are returned. Tasks added to the list via ClickUp's "multiple lists" feature (common for Sprint planning) are excluded.

Use Case: We use Sprint lists that aggregate tasks from multiple project lists. A task lives in "list 1" but is also assigned to "list 12". When querying Sprint 12, we need ALL assigned tasks, not just home-list tasks.

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/9) · 2026-02-09 · closed · external user · 6 comments

### Make the X-Cliickup-Key dynamic, please

## Type
- [ ] Bug Report
- [X] Feature Request
- [ ] Question/Other

## Prerequisites (for Bug Reports)
<!-- Skip this section for Feature Requests -->

**Environment Check:**
- [X] Node.js version: `node --version` (must be v18.0.0+)
- [X] npm version: `npm --version`
- [X] Operating System: (e.g., macOS 14, Windows 11, Ubuntu 22.04)
- [X] ClickUp API key configured
- [X] ClickUp Team ID configured
- [?] MCP License Key configured

**Quick Self-Check:**
- [X] I've verified my Node.js version me

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/6) · 2026-02-05 · closed · external user · 6 comments

### API Error: Tool input_schema uses unsupported oneOf/allOf/anyOf at top level

## Description

When using the ClickUp MCP server (v0.12.8) with Claude Code, the Anthropic API rejects requests with the following error:

API Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"tools.35.custom.input_schema: input_schema does not support oneOf, allOf, or anyOf at the top level"},"request_id":"req_011CXoEXj5hg7u5CVHGpdcYi"}


## Root Cause

One or more tool definitions in the MCP server have JSON schemas that use `oneOf`, `allOf`, or `anyOf` at t

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/5) · 2026-02-04 · closed · external user · 3 comments

### Getting *A valid license key is required to use this tool.*

*A valid license key is required to use this tool.* event when I pass the key

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/4) · 2026-01-28 · closed · external user · 6 comments

## Most recent

### update_task silently drops dueDate: success:true echoes the new due_date but the API payload never includes it (v0.14.5)

## Summary

`update_task` with a `dueDate` parameter (millisecond timestamp) returns `success: true` and echoes the requested new `due_date` in its response — but the due date never changes in ClickUp. Re-reading the task (via `get_task` or the UI) shows the old value.

## Reproduction (v0.14.5)

1. Call `update_task` with `{"taskId": "<id>", "dueDate": "<epoch-ms>"}` (name/description updates in the same call apply fine).
2. Response: `success: true`, echoed task object shows the new `due_date`

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/60) · 2026-08-18 · open · external user · 0 comments

### reset license 403

## Type
- [ ] Bug Report
- [ ] Feature Request
- [x ] Question/Other

## Prerequisites (for Bug Reports)
<!-- Skip this section for Feature Requests -->

**Environment Check:**
- [ ] Node.js version: `node --version` (must be v18.0.0+)
- [ ] npm version: `npm --version`
- [ ] Operating System: (e.g., macOS 14, Windows 11, Ubuntu 22.04)
- [ ] ClickUp API key configured
- [ ] ClickUp Team ID configured
- [ x] MCP License Key configured

**Quick Self-Check:**
- [x ] I've verified my Node.js version

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/59) · 2026-08-17 · open · external user · 0 comments

### Hosted server injects an "AI Duty" workspace directive and a per-response "Premium Active" banner — should be README-documented config, not injected instructions

Hi — thanks for the server, it's been part of my daily ticket workflow for months and the tool coverage is great.

I'm filing this about two behaviors of the hosted server (`clickup-mcp.taazkareem.com`) that are injected into the model's context rather than configured by the user. Neither looks malicious — but both actively interfere with agentic use, and two of my agents independently tripped over them in a single evening.

**1. The MCP `instructions` block carries a mandatory "AI Duty" directi

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/57) · 2026-07-15 · closed · external user · 1 comment

### No privacy policy or terms of service given

## Type
- [ ] Bug Report
- [ X] Feature Request
- [ ] Question/Other

## Prerequisites (for Bug Reports)
<!-- Skip this section for Feature Requests -->

**Environment Check:**
- [ ] Node.js version: `node --version` (must be v18.0.0+)
- [ ] npm version: `npm --version`
- [ ] Operating System: (e.g., macOS 14, Windows 11, Ubuntu 22.04)
- [ ] ClickUp API key configured
- [ ] ClickUp Team ID configured
- [ ] MCP License Key configured

**Quick Self-Check:**
- [ ] I've verified my Node.js version m

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/55) · 2026-05-30 · closed · external user · 2 comments

### Local STDIO server leaks hundreds of orphaned npx/node processes under Claude Code

## Summary

Running the local STDIO configuration for `@taazkareem/clickup-mcp-server@0.14.3` under Claude Code on macOS appears to leak/spawn repeated `clickup-mcp-server` process pairs. Over time this created hundreds of orphaned processes, consumed several GB of resident memory, and forced macOS into heavy memory compression/swap.

This does not look malicious from local process inspection; it looks like a process lifecycle / host compatibility issue where local STDIO server instances are rep

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/21) · 2026-04-28 · closed · external user · 2 comments

### Bug Report: Newlines Double-Escaped in Task Descriptions

**MCP Server:** ClickUp MCP (Premium)
**Reported by:** Luke Sellers (luke@salvatoauctions.com)
**Date:** 2026-03-26

---

## Summary

When creating or updating tasks via the ClickUp MCP server, newline characters (`\n`) in the `description` and `markdown_description` fields are double-escaped before being sent to the ClickUp API. This results in literal `\n` text rendering in the task body instead of actual line breaks.

## Steps to Reproduce

1. Create a task using `create_task` with a multilin

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/18) · 2026-03-26 · closed · external user · 2 comments

### oneOf/anyOf in tool schemas breaks Anthropic API — 11 core tools affected (v0.12.8 & v0.12.9)

## Type
- [x] Bug Report
- [ ] Feature Request
- [ ] Question/Other

## Prerequisites (for Bug Reports)

**Environment Check:**
- [x] Node.js version: v23.11.0
- [x] npm version: 10.9.2
- [x] Operating System: macOS 26.1
- [x] ClickUp API key configured
- [x] ClickUp Team ID configured
- [x] MCP License Key configured

**Quick Self-Check:**
- [x] I've verified my Node.js version meets requirements
- [x] I've tried clearing npm cache: `npm cache clean --force`
- [x] I've checked the configuration

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/7) · 2026-02-06 · closed · external user · 1 comment

### [Feature Request] Add include_markdown_description parameter to clickup_get_task

## Problem

When using `clickup_get_task`, the `description` field only returns **plain text**, not including markdown formatting or inline image references.

This causes issues when trying to **append content to the end of description** while preserving existing images/attachments at their original positions.

**Current behavior:**
- `description` field returns plain text only
- Images embedded in description are lost when doing GET → modify → PUT

## Root Cause

ClickUp API supports `include_m

[Read the thread](https://github.com/taazkareem/clickup-mcp-server/issues/3) · 2026-01-16 · closed · external user · 1 comment

The remaining reports are on [the project's issue tracker](https://github.com/taazkareem/clickup-mcp-server/issues).