home / mcp / clickup mcp server

ClickUp MCP Server

Provides access to ClickUp tasks, details, and comments through MCP for AI assistants.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "csevero-mcp-servers": {
      "command": "npx",
      "args": [
        "@csevero/mcp-clickup"
      ],
      "env": {
        "CLICKUP_API_KEY": "YOUR_API_KEY",
        "CLICKUP_TEAM_ID": "YOUR_TEAM_ID"
      }
    }
  }
}

MCP lets your AI assistant securely connect to external data sources and tools through a standardized interface. This ClickUp MCP Server enables your assistant to access ClickUp tasks, details, comments, and custom field configurations, while properly handling credentials and permissions.

How to use

You can use the ClickUp MCP Server from your AI assistant to retrieve tasks by custom ID, view task details and comments, and inspect custom field configurations. Credentials are managed securely through environment variables, ensuring your API keys stay protected. Integrate the server with your MCP client to perform these actions without exposing sensitive data in your prompts.

Typical usage patterns include: 1) Look up a task by its custom ID to fetch its details, 2) Open a task to see its description and status, 3) Retrieve comments to surface conversations around a task, 4) Inspect field configurations to understand available metadata for reporting.

How to install

Prerequisites: you need a supported runtime for MCP servers (Node.js and npm are common). Ensure you have Node.js version 14+ and npm installed on your system.

Option A — Claude integration (recommended):

claude mcp add clickup --env CLICKUP_API_KEY=YOUR_API_KEY \
  --env CLICKUP_TEAM_ID=YOUR_TEAM_ID \
  -- npx @csevero/mcp-clickup

Option B — Direct installation with npx (no Claude step):

npx @csevero/mcp-clickup

Additional notes

Two environment variables are required for runtime configuration: CLICKUP_API_KEY and CLICKUP_TEAM_ID. These are passed to the MCP server to authenticate with ClickUp and scope the data access. Keep these credentials secure and avoid sharing them in logs or prompts.

Configuration and usage notes

The server exposes a standard interface that your MCP client can consume to perform actions against ClickUp. If your client supports environment-based configuration, supply the API key and team ID as shown in the installation steps. Treat the key as a secret and rotate it periodically according to your security policy.

Troubleshooting

If you encounter authentication errors, verify that CLICKUP_API_KEY and CLICKUP_TEAM_ID are correctly set in your environment and that the key has the necessary permissions for the requested data. Check that your MCP client is invoking the server with the expected command and that the npx invocation resolves to the correct package version.

Available tools

get_tasks_by_custom_id

Retrieve tasks by their Custom ID to obtain task data and related metadata.

get_task_details

Fetch comprehensive details for a specific task, including status, due date, and assigned members.

get_task_comments

Retrieve comments associated with a task to surface discussions and context.

get_custom_fields

Access and list custom field configurations for tasks to understand available metadata.

manage_credentials

Securely manage and rotate API credentials used by the MCP server.