Official MCP Server Schema Incompatibility with AntiGravity IDE (Gemini)
G
Giulio Rugarli
Subject: Bug Report: Official MCP Server Schema Incompatibility with AntiGravity IDE (Gemini)
Hi ClickUp Team,
I'm writing to report a bug with your official MCP server that prevents it from functioning with AntiGravity IDE, which is listed as a supported MCP client in your documentation.
---
Issue Summary
When connecting to https://mcp.clickup.com/mcp via AntiGravity IDE, the connection fails immediately with HTTP 400 Bad Request due to an invalid tool schema.
Error received:
GenerateContentRequest.tools[26].function_declarations[0].parameters.properties[max_depth].enum: only allowed for STRING type
GenerateContentRequest.tools[26].function_declarations[0].parameters.properties[max_depth].enum[0]: cannot be empty
GenerateContentRequest.tools[26].function_declarations[0].parameters.properties[max_depth].enum[1]: cannot be empty
GenerateContentRequest.tools[26].function_declarations[0].parameters.properties[max_depth].enum[2]: cannot be empty
Root Cause
The
max_depth
parameter in one of your tool definitions (tools[26]) declares an enum
on an INTEGER type field. The Gemini API — which powers AntiGravity IDE — only allows enum
on STRING types. This is a schema incompatibility that causes a hard failure before any tool can be invoked.Steps to Reproduce
- Open AntiGravity IDE
- Add the following MCP server config:
```json
{
"mcpServers": {
"clickup": {
"serverUrl": "https://mcp.clickup.com/mcp"
}
}
}
```
- Attempt to initialize the MCP connection
- Observe HTTP 400 error
Expected Behavior
The MCP server should load successfully and tools should be available in AntiGravity IDE, as per your documentation which explicitly lists AntiGravity as a supported client.
Suggested Fix
Convert the
max_depth
parameter (and any other integer enum fields) to STRING type with a runtime conversion on your server side, or remove the enum constraint and validate the value programmatically instead.Environment
- MCP Client: AntiGravity IDE
- MCP Server: https://mcp.clickup.com/mcp (official, first-party)
- Underlying model: Gemini (Google)
Since AntiGravity is listed as a supported client in your documentation (https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server), I'd appreciate a prompt resolution.
Thank you,
Log In
Arkady Sokolov
Merged in a post:
Ability to use string enums for Google Gemini in MCP Server
J
Jan Marlowe Dauz
I've done a bit of extra digging and found this: https://github.com/google-gemini/gemini-cli/issues/4127
It seems like Google's Gemini doesn't support integer enums at all. For future reference, Clickup uses this in their MCP only in this field, so it might be worth considering changing this to e.g. a string enum instead to become compatible with Google's Gemini models:
"max_depth": {
"description": "Maximum depth of hierarchy to return: 0=spaces only, 1=spaces+folders, 2=spaces+folders+lists (default: 2)",
"enum": [
0,
1,
2
],
"type": "number"
},
-Niels
s
shouldz
Hey! I created a free, lightweight Node bridge to solve the schema errors with ClickUp MCP in Gemini / Antigravity: https://github.com/herr-schulz/antigravity-clickup-mcp
Talib Kareem
Hi Giulio Rugarli
I recommend the Premium version at clickup-mcp-server
The MCP is not only supported on Antigravity but optimized for IDEs that often struggle with large tool sets. You can filter the available tools with X-Personas and X-Enabled-Tools or X-Disabled-Tools headers.
I recommend disabling all tools you know you won't use to keep it under the 50 limit.
Bodog
Talib Kareem thanks for your work on this!
I ran into this exact issue in Antigravity recently, so I'm giving your repo a try. It's working perfectly so far!
Jinal Kothari
I too would like to use Gemini with the official ClickUp MCP. Facing the same issue.