ClickUp

Provides MCP endpoints to authenticate with ClickUp and fetch tasks by ID or custom ID within a ClickUp workspace.
  • typescript

3

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

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

This MCP Server enables Claude to interact with ClickUp workspaces by exposing API tools that authenticate, fetch tasks, and retrieve task details. It lets you perform essential ClickUp operations from your MCP client in a streamlined, programmatic way.

How to use

You integrate the ClickUp MCP Server with your MCP client to authenticate against ClickUp and to retrieve task data. Start by running one of the provided MCP configurations, then call the exposed tools to perform actions such as authenticating, fetching a task by ID or by custom ID, and listing multiple tasks.

How to install

Prerequisites you need before installing include a runtime environment for executing MCP servers (Node.js and npm, or Docker). You also need a ClickUp API token and your ClickUp workspace ID.

Install and run the MCP server using one of the two supported local execution methods shown here. Pick the method that matches your environment.

Standard runtime via npx (recommended for quick start)

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

Docker-based runtime

{
  "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"
      }
    }
  }
}

Additional sections (H2)

In addition to running the MCP server, you can manage security by keeping your API token secret and rotating it if you suspect compromise. Only grant tokens the minimum permissions required for your tasks.

Troubleshooting

If you encounter errors, verify that your API token is valid and not expired, that the workspace ID is correct, and that you have the necessary permissions in the ClickUp workspace. Ensure the task IDs you request exist and are accessible to your account.

Build

To prepare a container-ready image, you can build the MCP clickup image locally if you maintain a Docker workflow.

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.

Available tools

clickup_authenticate

Authenticate with ClickUp API using an API token and workspace ID, returning user information and authentication status.

clickup_get_task

Retrieve a task by its ClickUp task ID, returning detailed task information including description, status, and metadata.

clickup_get_task_by_custom_id

Retrieve a task by its custom ID within a given workspace, returning detailed task information.

clickup_get_tasks

Retrieve multiple tasks by their IDs, returning a list with complete task information.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational