clickup

This MCP server exposes a suite of ClickUp integration tools that let your language models interact with tasks, documents, custom fields, assignees, and workspace structure in ClickUp. Available tools include creating and updating tasks (clickup_create_task, clickup_update_task, clickup_update_task_by_custom_id), querying tasks by ID or custom ID (clickup_get_task, clickup_get_task_by_custom_id), listing tasks (get_list_tasks), and managing documents (clickup_create_doc, clickup_search_docs, clickup_get_doc_pages, clickup_get_page, clickup_create_page, clickup_edit_page). It also provides access to custom fields (clickup_get_list_custom_fields, clickup_set_custom_field_value, clickup_set_custom_field_value_by_custom_id) and workspace structure data (get_spaces, get_folders, get_lists, create_list). To use it, deploy the server via your chosen method (Docker in the provided example) and configure the MCP to point at your ClickUp API token and workspace ID. Once running, send requests to the corresponding tool endpoints; the model can compose natural-language prompts that translate into these tool calls, enabling tasks and documents to be read, created, or updated within ClickUp.

Prerequisites:

• Docker installed and running on your machine or deployment host
• Access to a ClickUp API token with appropriate permissions
• Knowledge of your ClickUp workspace ID

Step 1: Obtain prerequisites

• Generate a ClickUp API token from your ClickUp account settings
• Locate your ClickUp workspace ID from the URL when you are in the workspace (numeric value)

Step 2: Pull or build the MCP server image

• If you have a prebuilt image, replace your-docker-repository in the command below with the exact image name
• Example (Docker):
  • docker buildx build -t your-docker-repository --platform linux/amd64 .
  • docker push your-docker-repository

Step 3: Run the MCP server (Docker example)

• Replace your-api-token and your-workspace-id with your actual values: docker run -i --rm -e CLICKUP_API_TOKEN=your-api-token -e CLICKUP_WORKSPACE_ID=your-workspace-id your-docker-repository

Step 4: Configure MCP client (example in README)

• Add the following to your cline_mcp_settings.json under mcpServers: { "clickup": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "CLICKUP_API_TOKEN", "-e", "CLICKUP_WORKSPACE_ID", "your-docker-repository" ], "env": { "CLICKUP_API_TOKEN": "your-api-token", "CLICKUP_WORKSPACE_ID": "your-workspace-id" } } }

Step 5: Verify and test

• Ensure the Docker container starts without errors
• Use your MCP client to invoke one of the ClickUp tools (e.g., clickup_get_task) to verify connectivity

Tips and troubleshooting:

• Ensure the CLICKUP_API_TOKEN has permissions for the operations you intend to perform (read/write access as needed).
• Double-check the CLICKUP_WORKSPACE_ID to avoid scope issues across workspaces.
• If you encounter authentication errors, re-generate a new API token and update the environment variables.
• When using Docker, make sure the host can reach ClickUp services and that network restrictions (firewalls, VPNs) do not block API calls.
• For local development, you can test with small, simple requests first to validate configuration before moving to production data.
• If you rename the image or repository, update the mcp_config accordingly so the MCP knows which image to run.