clickup-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_MODE | No | Authentication mode: 'env' (token from env var) or 'gateway' (token per-request from X-Clickup-Token header) | env |
| MCP_HTTP_PORT | No | HTTP server port | 8080 |
| MCP_TRANSPORT | No | Transport mode: 'stdio' (Claude Desktop) or 'http' (gateway) | stdio |
| CLICKUP_BASE_URL | No | API base URL | https://api.clickup.com/api/v2 |
| CLICKUP_API_TOKEN | No | ClickUp personal API token (pk_xxxxx) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| clickup_test_connectionA | Test ClickUp connection. Shows configuration requirements when credentials are missing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming consistency is not applicable, but the tool name follows a clear verb_noun pattern.
A single 'test connection' tool is severely insufficient for a platform like ClickUp, which typically requires many tools for tasks, issues, lists, etc.
The tool only tests the connection, lacking any actual CRUD operations or meaningful interactions with ClickUp resources.