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.

Additional MCP asks: (1) ability to filter by custom fields and (2) ability to use Views to determine task pulls.

is the 300/24h limit for all workspace members, or is it per user authenticated to the server?

If the 300/24h limit applies to all workspace members, then our team still cannot use MCP.

I've been using the MCP server since it's initial rollout, and I am happy with all of the various features and how it has progressed.

The one issue, and it is a major one, is the rate limiting. 300 calls in 24 hours is not nearly sufficient- specifically when using it as a project management tool and managing a very large project.

I'd encourage you to raise the rate limits to something more reasonable, otherwise you risk AI-savvy customers creating their own tooling that uses the MUCH more reasonable API limits (1,000 requests PER MINUTE).

We'd want full CRUD access to the task URL links through the MCP. We have additional context from other apps here, which the agent can't see now. And I'd like for the agent to attach its GitHub PR to the task when it's done. Currently this can only be done through polluting the task description with the URL, whereas a human can cleanly add a URL link to the task via the task view sidebar.

Hello,

I believe there's a very high impact BUG on ChatGPT's MCP client.

While Claude works fine with the MCP as far as we use it, ChatGPT/Codex can't seem to work with custom fields. It can't read them, can't set values on them.

It seems that ChatGPT's MCP client doesn't have a way to get the custom fields schema when getting a task. Claude uses: include: ["custom_fields"] and gets the related schema, when I specifically instructed ChatGPT to use that it returned an error so this must be an MCP client bug.

It keeps compalining that all it can read is "custom_fields": 1 without any schema whatever it tried.

A silly workaround I figured out so far is that if I manually (or with Claude) find the custom field's UUID and instruct ChatGPT to update this custom field (it's a relationship field back to a clients list) using the specific UUID it succeeds in adding a correct value.

But then there is no way of ChatGPT reading this value back. The clickup_get_task still returns "custom_fields": 1 without any way to expand the schema.

Overall Claude reports 53 tools available, and ChatGPT 32 tools. That's quite a gap there. Comparing these tools it seems ChatGPT doesn't get tools for comments, reminders or task filtering! And that is apart from the actual tools that ChatGPT has but are poor in design (like the custom fields not working).

Are you actively working on improving the MCP client for ChatGPT/Codex?