Skip to main content
Glama
mcp-clickup
by mikah13

ClickUp MCP Server

MCP Server for the ClickUp API, enabling Claude to interact with ClickUp workspaces.

Tools

  1. clickup_authenticate

    • Authenticate with ClickUp API using an API token and workspace ID

    • Required inputs:

      • api_token (string): ClickUp API token for authentication

      • workspace_id (string): ClickUp workspace ID for authentication

    • Returns: User information and authentication status

  2. clickup_get_task

    • Retrieve a task from ClickUp by task ID

    • Required inputs:

      • api_token (string): ClickUp API token for authentication

      • task_id (string): The ID of the ClickUp task to retrieve

    • Returns: Detailed task information including description, status, and metadata

  3. clickup_get_task_by_custom_id

    • Retrieve a task from ClickUp by custom ID

    • Required inputs:

      • api_token (string): ClickUp API token for authentication

      • custom_id (string): The custom ID of the ClickUp task to retrieve

      • workspace_id (string): The workspace ID required for the API request

    • Returns: Detailed task information including description, status, and metadata

  4. clickup_get_tasks

    • Retrieve multiple tasks from ClickUp by their IDs

    • Required inputs:

      • api_token (string): ClickUp API token for authentication

      • workspace_id (string): ClickUp workspace ID

      • task_ids (string[]): List of task IDs to retrieve

    • Returns: List of tasks with their complete information

Related MCP server: clickup-custom-mcp

Setup

  1. Get your ClickUp API Token:

    • Log in to your ClickUp account

    • Go to Settings → Apps

    • Click "Generate API Token"

    • Copy your API token

  2. Get your Workspace ID:

    • Open ClickUp in your browser

    • The Workspace ID is in the URL: https://app.clickup.com/{workspace_id}/home

    • It's a number that starts with a number

Usage with Claude Desktop

Add the following to your claude_desktop_config.json:

npx

{
  "mcpServers": {
    "clickup": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-clickup"
      ],
      "env": {
        "CLICKUP_API_TOKEN": "your-api-token",
        "CLICKUP_WORKSPACE_ID": "your-workspace-id"
      }
    }
  }
}

docker

{
  "mcpServers": {
    "clickup": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "CLICKUP_API_TOKEN",
        "-e",
        "CLICKUP_WORKSPACE_ID",
        "mcp/clickup"
      ],
      "env": {
        "CLICKUP_API_TOKEN": "your-api-token",
        "CLICKUP_WORKSPACE_ID": "your-workspace-id"
      }
    }
  }
}

Troubleshooting

If you encounter errors, verify that:

  1. Your API token is valid and has not expired

  2. The workspace ID is correct

  3. You have the necessary permissions in the ClickUp workspace

  4. The task IDs you're trying to access exist and are accessible to you

Build

Docker build:

docker build -t mcp/clickup .

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

Available Tools

4 tools
clickup_authenticateC

Authenticate with ClickUp API using an API token and workspace ID

Inputs: type (required).

clickup_get_taskC

Get a task by its ID

Inputs: type (required).

clickup_get_task_by_custom_idC

Get a task by its custom ID

Inputs: type (required).

clickup_get_tasksC

Get multiple tasks by their IDs

Inputs: type (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    Tools are mostly distinct: authentication vs. task retrieval. However, clickup_get_task and clickup_get_task_by_custom_id have similar purposes differentiated only by ID type, which could cause minor confusion despite clear descriptions.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (clickup_authenticate, clickup_get_task, etc.) with no deviations, making the naming predictable and clear.

    Tool Count4/5

    With 4 tools, the server is slightly sparse but appropriate for a focused task retrieval scope. The count is not excessive, but the server could benefit from a few more tools for a broader feature set.

    Completeness2/5

    The tool surface is severely incomplete for a task management API. It only provides authentication and read operations for tasks, missing create, update, delete, and other essential endpoints like listing tasks by filter or managing other entities (lists, folders).

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers