ClickUp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLICKUP_APP_ENV | No | Application environment (default: development) | development |
| CLICKUP_BASE_URL | No | Base URL for ClickUp API (default: https://api.clickup.com/api/v2) | https://api.clickup.com/api/v2 |
| CLICKUP_API_TOKEN | Yes | Your ClickUp API token (required) | |
| CLICKUP_MAX_RETRIES | No | Maximum number of retries for failed requests (default: 2) | 2 |
| CLICKUP_RETRY_BACKOFF_SECONDS | No | Retry backoff in seconds (default: 0.5) | 0.5 |
| CLICKUP_REQUEST_TIMEOUT_SECONDS | No | Request timeout in seconds (default: 15) | 15 |
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 |
|---|---|
| get_userA | Return the current ClickUp user profile using the configured API token. Use this to verify authentication and retrieve your user details (id, email, name). |
| get_taskC | Get a specific task by ID. Parameters:
|
| create_taskC | Create a new task in a list. Parameters:
|
| update_taskB | Update an existing task. Parameters:
|
| delete_taskC | Delete a task. Parameters:
|
| list_tasksA | List tasks in a list with optional filtering. Parameters:
|
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 6 tools
Each tool has a distinct purpose: creating, deleting, getting, listing, and updating tasks, plus retrieving user info. No overlapping functionality.
All tools follow a consistent verb_noun pattern (e.g., create_task, get_task, list_tasks), making them predictable and easy to understand.
With 6 tools, the server covers essential task operations (CRUD) plus user verification, which is a reasonable scope for a task-focused MCP server.
The tool set provides full CRUD for tasks and user authentication, which covers basic task management. Minor gaps exist, such as no tool for managing lists or members, but core functionality is complete.