hi

clickup_update_task silently drops the REST API's points field (Sprint Points). Updating "points" returns "At least one field to update must be provided". clickup_create_task has no points parameter, clickup_get_task returns no points field, and clickup_get_operators reports no enabled operators.

clickup_get_task omits synced-block content from markdown_description (text and images), with no way to resolve it

We just started using synced content (a great feature!), but the MCP server, and seemingly the REST API, can't read it.

Problem

When a task description contains a synced block, text_content returns only a [sync-block:<uuid>] marker, and markdown_description drops the block entirely, text and images included. This happens in the task that created the block and in every task that shows it. Nothing in the response gives the block's content or source, and no tool fetches a block by ID. Exports, reports and AI summaries built from MCP output are silently incomplete.

Steps to reproduce

Observed

Expected (any one would do)

Impact

The markdown has no gap marker, so consumers can't tell content is missing. The only way to notice is to cross-check text_content for [sync-block: markers against the UI.

Note

The response shape (markdown_description, text_content, epoch-ms dates, dropdown values as orderindex) looks like REST v2 GET /v2/task/{task_id}?include_markdown_description=true. The Get Task reference doesn't mention synced blocks, so the gap may be in the underlying API as well as the MCP server.

Having a few issues:

clickup_add_time_entry declares its tags parameter as:

"tags": { "type": "array", "items": { "type": "string" },

"description": "Array of tag names to assign to the time entry." }

So the tool ships tags: ["dev"].

The v2 endpoint behind it, POST /api/v2/team/{team_id}/time_entries, documents tags as an array of objects, and every tagged entry your own API returns carries the object form:

"tags": [ { "name": "dev", "tag_bg": null, "tag_fg": null, "creator": 30013528 } ]

ClickUp looks for a name key on each element, gets a bare string, and answers:

Failed to add time entry: Name value is required

Result: tags cannot be written through the MCP server at all. I tried a plain string array and an object-shaped string, and both fail the same way. The schema itself blocks passing a real object, so there's no client side workaround.

Fix: declare tags as an array of objects with a required name, or keep accepting strings and map each one to { "name": value } before calling the API.

Worse than the tag failure. When the tag step fails, the call returns an error, but the time entry is created anyway without its tag. An error that looks like nothing happened is an error people retry.

I retried, and ended up with three identical one hour entries on one task and two identical entries on another. And there is no delete_time_entry or update_time_entry tool exposed, so nothing can clean it up programmatically. It had to be fixed by hand in the UI.

Fix: apply the tags in the same transaction as the entry, or roll the entry back when tagging fails. Either way the response should tell the truth about whether the entry landed.

POST /api/v2/team/{team_id}/time_entries/tags tags existing entries. Nothing in the MCP server exposes it, so entries written untagged can never be fixed programmatically.

No delete or update for time entries, which is what turned defect 2 into manual cleanup.

Environment

Official ClickUp MCP server at mcp.clickup.com/mcp, public beta, reached through Anthropic's connector directory. Observed 2026-09-12.

I’m trying to connect the built-in ClickUp integration in ChatGPT, but the connection keeps failing.

When I click to connect ClickUp, the authorization window opens and immediately shows this error:

invalid_client - Invalid client_id

It happens before I get the chance to choose or authorize a ClickUp workspace.

I first thought it might be an issue with my ClickUp account, so I tested the ClickUp API separately using a custom GPT Action. That works fine — it can authenticate, see my workspace, and retrieve spaces. So my ClickUp account and API access seem to be working normally.

Because of that, it looks like the issue is specifically with the built-in ChatGPT/ClickUp connection and its OAuth setup.

I also tried reconnecting, but I keep getting the same Invalid client_id error.

Can you check whether the OAuth client ID being used for the ChatGPT integration is still valid or configured correctly?

We are experiencing the same issue with ChatGPT + ClickUp in a real production-planning workspace.

Our ClickUp tasks contain critical Custom Fields used for manufacturing planning — production CW, export CW, order/MTK identifiers, quantities and other structured production data.

ChatGPT can identify the task, Task ID, status and location in the workspace, and even reports the number of Custom Fields, but it cannot retrieve the actual Custom Field schema and values.

This prevents the AI from reliably analyzing production capacity and forces us to combine ClickUp task IDs with an external Master File as a workaround.

This is not a cosmetic limitation for us — the missing Custom Fields prevent a real manufacturing planning system from operating correctly through the ChatGPT connector.

Please expose the complete Custom Field schema and values to ChatGPT/Codex with parity across supported MCP clients.

An error appears to be a null-handling bug. The "Available workspaces:" list comes back empty, and the example prints undefined, suggesting the server fails to enumerate workspaces, gets an empty list, and misreports "none found" as "multiple found."

workspace_id is not exposed in the tool schemas, so even if I wanted to supply it, I can't. The parameter the error demands doesn't exist on clickup_get_workspace_hierarchy, clickup_create_task, etc

These artificial rate limits are the dumbest thing I've seen.

I am trying to connect Meta’s official Ads MCP server to ClickUp using this URL: https://mcp.facebook.com/ads

In ClickUp, I navigate to App Center → MCP Servers → Add Custom MCP Server, enter the Meta Ads MCP server URL, and attempt to authorise the connection. However, the connection fails and ClickUp displays an error, so the Meta Ads tools never become available in ClickUp Brain or Super Agents.

Meta has released this connector to provide authorised AI tools for Meta Ads reporting, campaign creation, ad set and ad editing, product catalogue management, and account diagnostics. ClickUp currently supports external MCP servers, but the Meta Ads server does not complete the connection or authorization process.

Expected result: ClickUp should open Meta’s authorisation flow, allow me to select and approve the relevant Meta Business and advertising accounts, then return to ClickUp with the Meta Ads tools connected.

Actual result: The connection fails with an error before setup can be completed. Retrying the connection produces the same result.

This issue prevents our marketing agency from connecting client Meta Ads accounts to ClickUp for campaign reporting, diagnostics, and approved advertising actions. Please investigate whether ClickUp’s MCP connection, OAuth callback, requested scopes, or compatibility with Meta’s MCP server requires an update.

Also connecting to Social Media Page results would be helpful as well - like how many new followers etc

We tag Docs in our workspace (e.g. "llm sync") and need to programmatically retrieve all Docs with a specific tag after a given date. The tags exist in the UI and can be applied to Docs, but the MCP has no way to query or filter Docs by tag or updated date.

Use case: We use Claude via MCP to sync meeting notes tagged "llm sync" into an external system. Right now there's no way to say "get me all docs tagged X updated after Y" without manually finding them in the UI.

Ideal solution: A search/filter tool in the MCP that supports Doc tags and date ranges, similar to how tasks can be queried by tag and due date today.