ClickUp MCP server

Integrates with ClickUp to enable task creation, project management, and workflow automation for teams using AI-powered assistants.
Back to servers
Provider
Nazruden
Release date
Feb 07, 2025
Language
TypeScript
Stats
10 stars

The ClickUp MCP Server provides integration between AI assistants and ClickUp workspaces through the Model Context Protocol (MCP). It enables AI tools to manage tasks, teams, boards, spaces, folders, custom fields, documents, and views within your ClickUp environment.

Quick Start

This server requires your ClickUp Personal API Token for authentication.

Installation and Configuration

  1. Generate a Personal API Token in ClickUp:

    • Go to "My Settings" > "Apps" and generate a token
  2. Configure your MCP Client (e.g., Claude for Desktop):

{
  "mcpServers": {
    "clickup": {
      "command": "npx",
      "args": ["@nazruden/clickup-server"],
      "env": {
        "CLICKUP_PERSONAL_TOKEN": "your_personal_api_token_here"
      }
    }
  }
}
  1. Restart your MCP Client

The server will be automatically downloaded and started when needed.

Installing via Smithery

For Claude Desktop users, you can install automatically via Smithery:

npx -y @smithery/cli install @Nazruden/clickup-mcp-server --client claude

Environment Variables

Required

  • CLICKUP_PERSONAL_TOKEN: Your ClickUp Personal API Token

Optional

  • LOG_LEVEL: Logging level (error, warn, info, debug). Defaults to info
  • ENCRYPTION_KEY: A persistent 32-byte hex-encoded key (not currently used)
  • PORT: Server port (not used in default Stdio MCP server mode)

Available Tools

Task Management

  • clickup_create_task: Create a new task

    • Required: list_id, name
    • Optional: description, status, priority, assignees, due_date, time_estimate, tags
  • clickup_update_task: Update an existing task

    • Required: task_id
    • Optional: Any writable task properties

Team & List Management

  • clickup_get_teams: Retrieve all accessible teams (Workspaces)
  • clickup_get_lists: Get all lists in a specific folder
    • Required: folder_id

Board Management

  • clickup_create_board: Create a new board
    • Required: space_id, name

Space Management

  • clickup_get_spaces: Get all Spaces for a Workspace

    • Required: team_id
    • Optional: archived
  • clickup_create_space: Create a new Space

    • Required: team_id, name
    • Optional: multiple_assignees, features
  • clickup_get_space: Get Space details

    • Required: space_id
  • clickup_update_space: Update a Space

    • Required: space_id
    • Optional: name, color, private, admin_can_manage, archived, features
  • clickup_delete_space: Delete a Space

    • Required: space_id

Folder Management

  • clickup_get_folders: Get all Folders in a Space

    • Required: space_id
    • Optional: archived
  • clickup_create_folder: Create a new Folder

    • Required: space_id, name
  • clickup_get_folder: Get Folder details

    • Required: folder_id
  • clickup_update_folder: Update a Folder

    • Required: folder_id, name
  • clickup_delete_folder: Delete a Folder

    • Required: folder_id

Custom Field Management

  • clickup_get_custom_fields: Get Custom Fields for a List

    • Required: list_id
  • clickup_set_task_custom_field_value: Set Custom Field value

    • Required: task_id, field_id, value
    • Optional: value_options
  • clickup_remove_task_custom_field_value: Clear Custom Field value

    • Required: task_id, field_id

Doc Management

  • clickup_search_docs: Search for Docs

    • Required: workspace_id
    • Optional: query, include_archived
  • clickup_create_doc: Create a new Doc

    • Required: workspace_id, name
    • Optional: parent, visibility, create_page
  • clickup_get_doc_pages: Get pages in a Doc

    • Required: doc_id
  • clickup_create_doc_page: Create a new Doc page

    • Required: workspace_id, doc_id, name
    • Optional: content, orderindex, parent_page_id, sub_title, content_format
  • clickup_get_doc_page_content: Get Doc page content

    • Required: workspace_id, doc_id, page_id
    • Optional: content_format
  • clickup_edit_doc_page_content: Update Doc page content

    • Required: workspace_id, doc_id, page_id, content
    • Optional: title, sub_title, content_edit_mode, content_format

View Management

  • clickup_get_views: Get Views for a resource

    • Required: parent_id, parent_type
  • clickup_create_view: Create a new View

    • Required: parent_id, parent_type, name, type
    • Optional: grouping, divide, sorting, filters, columns, team_sidebar, settings
  • clickup_get_view_details: Get View details

    • Required: view_id
  • clickup_update_view: Update a View

    • Required: view_id
    • Optional: name, grouping, divide, sorting, filters, columns, team_sidebar, settings
  • clickup_delete_view: Delete a View

    • Required: view_id
  • clickup_get_view_tasks: Get tasks in a View

    • Required: view_id
    • Optional: page

Troubleshooting

Common Issues

  1. Authentication Errors (401)

    • Verify your CLICKUP_PERSONAL_TOKEN is correct
    • Ensure the token is valid and not revoked
    • Check server logs for authentication messages
  2. Rate Limiting

    • Server logs rate limit information from ClickUp API responses
    • High usage may trigger rate limits
  3. Server Not Starting

    • Ensure CLICKUP_PERSONAL_TOKEN is set
    • Check for TypeScript errors in the console
    • Look for errors from src/index.ts or ClickUpService

Finding Server Logs

When run by an MCP client like Claude for Desktop, logs can typically be found at:

  • Windows: %USERPROFILE%\AppData\Local\Claude\Logs\mcp\<server_name_and_id>\<process_id>.log
  • macOS: ~/Library/Logs/Claude/mcp/<server_name_and_id>\<process_id>.log

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.

Want to 10x your AI skills?

Get a free account and learn to code + market your apps using AI (with or without vibes!).

Nah, maybe later