ClickUp MCP Server

@Nazruden

About ClickUp MCP Server

A Model Context Protocol server implementation for ClickUp integration, enabling AI assistants to interact with ClickUp workspaces.

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "clickup-mcp-server-nazruden": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli",
        "install",
        "@Nazruden/clickup-mcp-server",
        "--client",
        "claude"
      ]
    }
  }
}

Tools

No tools detected

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is ClickUp MCP Server?

A Model Context Protocol (MCP) server that integrates AI assistants with ClickUp workspaces. It enables AI assistants to interact with ClickUp tasks, docs, spaces, folders, views, and custom fields using ClickUp’s API v2/v3. It is intended for developers and users who want to control ClickUp through natural language via an MCP client.

How to use ClickUp MCP Server?

Set the CLICKUP_PERSONAL_TOKEN environment variable with your ClickUp Personal API Token, then configure your MCP client (e.g., Claude for Desktop) to run npx @nazruden/clickup-server. The server communicates via Stdio transport. Optionally install via Smithery with npx -y @smithery/cli install @Nazruden/clickup-mcp-server --client claude.

Key features of ClickUp MCP Server

Create and update tasks in ClickUp lists.
Manage workspaces, spaces, folders, and boards.
Create, edit, and retrieve docs (Markdown content).
Set and remove custom field values on tasks.
Manage views (list, board, calendar, Gantt) and retrieve view tasks.

Use cases of ClickUp MCP Server

Automate task creation and updates from AI chat.
Search and manage ClickUp docs via natural language.
Create or delete folders/spaces/boards programmatically.
Retrieve and modify custom fields on tasks.
List teams, spaces, folders, and views for reporting.

FAQ from ClickUp MCP Server

How does the server authenticate with ClickUp?

It requires a CLICKUP_PERSONAL_TOKEN environment variable set to a valid ClickUp Personal API Token. The token is passed to the ClickUp API for all requests.

What transport does this server use?

It runs via Stdio transport as per the MCP specification. The server is invoked by an MCP client and communicates over stdin/stdout.

Are there any known limitations?

Yes, ClickUp’s API for Docs (especially v3) does not support direct document deletion; manage Doc lifecycle via archiving or page manipulation. Also, the ENCRYPTION_KEY mechanism is currently not used for encrypting the token in the authentication flow.

What is the server’s runtime requirement?

It requires Node.js and uses npx to run the npm package @nazruden/clickup-server. The server is automatically downloaded and started by the MCP client when needed.

How can I get server logs?

When run via npm run dev or npm start, logs go to the console. When run by an MCP client (e.g., Claude for Desktop), logs are managed by that client and can be found in platform-specific directories as described in the README.

Frequently asked questions

How does the server authenticate with ClickUp?

It requires a `CLICKUP_PERSONAL_TOKEN` environment variable set to a valid ClickUp Personal API Token. The token is passed to the ClickUp API for all requests.

What transport does this server use?

It runs via Stdio transport as per the MCP specification. The server is invoked by an MCP client and communicates over stdin/stdout.

Are there any known limitations?

Yes, ClickUp’s API for Docs (especially v3) does not support direct document deletion; manage Doc lifecycle via archiving or page manipulation. Also, the `ENCRYPTION_KEY` mechanism is currently not used for encrypting the token in the authentication flow.

What is the server’s runtime requirement?

It requires Node.js and uses `npx` to run the npm package `@nazruden/clickup-server`. The server is automatically downloaded and started by the MCP client when needed.

How can I get server logs?

When run via `npm run dev` or `npm start`, logs go to the console. When run by an MCP client (e.g., Claude for Desktop), logs are managed by that client and can be found in platform-specific directories as described in the README.

Comments

Basic information

More Other MCP servers

Peekaboo MCP – lightning-fast macOS screenshots for AI agents

steipete

Peekaboo is a macOS CLI & optional MCP server that enables AI agents to capture screenshots of applications, or the entire system, with optional visual question answering through local or remote AI models.

4.8K