Skip to main content
Glama
Sign In
enesjakozh
ClickUp MCP Sedrver

ClickUp MCP Sedrver

by nsxdavid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ClickUp MCP Server

A Model Context Protocol (MCP) server that provides a standardized interface for AI assistants to interact with the ClickUp API. This server enables AI systems to access and manipulate ClickUp data such as workspaces, spaces, folders, lists, tasks, docs, comments, and checklists.

Available Tools

  • get_workspaces: Get the list of workspaces

  • get_spaces: Get spaces within a workspace

  • get_tasks: Get tasks from a list

  • create_task: Create a new task

  • update_task: Update an existing task

  • get_docs_from_workspace: Get all docs from a workspace

  • create_folder: Create a new folder in a space

  • get_lists: Get lists in a folder or space

  • create_list: Create a new list

Related MCP server: ClickUp MCP Server

Installation

git clone https://github.com/nsxdavid/clickup-mcp-server.git
cd clickup-mcp-server
npm install

Get ClickUp API Token

  1. Log in to ClickUp account

  2. Go to Settings > Apps

  3. Click "Generate API Token"

  4. Copy the token

Configuration

Add to the MCP settings file:

{
  "mcpServers": {
    "clickup": {
      "command": "node",
      "args": ["/path/to/clickup-mcp-server/build/index.js"],
      "env": {
        "CLICKUP_API_TOKEN": "YOUR_API_TOKEN_HERE"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

  • Make sure to correct the path

  • Make sure to supply your API token

Alternate Installation (npx)

For users who prefer not to clone the repository, the package can be run directly using npx:

{
  "mcpServers": {
    "clickup": {
      "command": "npx",
      "args": [
        "-y",
        "clickup-mcp-server"
      ],
      "env": {
        "CLICKUP_API_TOKEN": "YOUR_API_TOKEN_HERE"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

  • Replace YOUR_API_TOKEN_HERE with your API token

  • No installation or cloning is required with this method

Configuration File Locations

  • Cline VSCode Extension: ~/.vscode/extensions/saoudrizwan.claude-dev/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

  • Claude Desktop Apps:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

Development

Building

npm run build

Running Tests

npm test

License

MIT

Available Tools

42 tools
add_task_to_listB

Add an existing task to a ClickUp list.

Inputs: list_id (required), task_id (required).

create_chat_view_commentA

Create a new comment in a ClickUp chat view. Supports notification settings.

Inputs: view_id (required), comment_text (required), notify_all.

create_checklistB

Create a new checklist in a ClickUp task. Returns the created checklist details.

Inputs: task_id (required), name (required).

create_checklist_itemB

Create a new item in a ClickUp checklist. Supports optional assignee and resolved status.

Inputs: checklist_id (required), name (required), assignee, resolved.

create_folderA

Create a new folder in a ClickUp space with the specified name.

Inputs: space_id (required), name (required).

create_folderless_listA

Create a new list directly in a ClickUp space without placing it in a folder.

Inputs: space_id (required), name (required).

create_listA

Create a new list in a ClickUp folder or space with the specified name.

Inputs: container_type (required), container_id (required), name (required).

create_list_commentB

Create a new comment on a ClickUp list. Supports optional assignee and notification settings.

Inputs: list_id (required), comment_text (required), assignee, notify_all.

create_list_from_template_in_folderB

Create a new list in a ClickUp folder using an existing template.

Inputs: folder_id (required), template_id (required), name (required).

create_list_from_template_in_spaceB

Create a new list in a ClickUp space using an existing template.

Inputs: space_id (required), template_id (required), name (required).

create_taskB

Create a new task in a ClickUp list with specified properties like name, description, assignees, status, and dates.

Inputs: list_id (required), name (required), description, assignees, +10 more.

create_task_commentC

Create a new comment on a ClickUp task. Supports optional assignee and notification settings.

Inputs: task_id (required), comment_text (required), assignee, notify_all.

create_threaded_commentB

Create a new threaded comment (reply) to a parent comment. Supports notification settings.

Inputs: comment_id (required), comment_text (required), notify_all.

delete_checklistA

Delete a checklist from a ClickUp task. Removes the checklist and all its items.

Inputs: checklist_id (required).

delete_checklist_itemB

Delete an item from a ClickUp checklist.

Inputs: checklist_id (required), checklist_item_id (required).

delete_commentB

Delete a comment from ClickUp.

Inputs: comment_id (required).

delete_folderB

Delete a folder from ClickUp. Removes the folder and its contents.

Inputs: folder_id (required).

delete_listB

Delete a list from ClickUp. Removes the list and its tasks.

Inputs: list_id (required).

get_chat_view_commentsB

Get comments for a ClickUp chat view. Returns comment details with pagination support.

Inputs: view_id (required), start, start_id.

get_doc_contentA

Get the content of a specific ClickUp doc. Returns combined content from all pages in the doc.

Inputs: doc_id (required), workspace_id (required).

get_doc_pagesB

Get the pages of a specific ClickUp doc. Returns page content in the requested format (markdown or plain text).

Inputs: doc_id (required), workspace_id (required), content_format.

get_docs_from_workspaceB

Get all docs from a ClickUp workspace. Supports pagination and filtering for deleted/archived docs.

Inputs: workspace_id (required), cursor, deleted, archived, +1 more.

get_folderless_listsB

Get lists that are not in any folder within a ClickUp space.

Inputs: space_id (required).

get_listA

Get details about a specific ClickUp list including its name and content.

Inputs: list_id (required).

get_list_commentsA

Get comments for a ClickUp list. Returns comment details with pagination support.

Inputs: list_id (required), start, start_id.

get_listsA

Get lists from a ClickUp folder or space. Returns list details including name and content.

Inputs: container_type (required), container_id (required).

get_spaceA

Get details about a specific ClickUp space. Returns space name, settings, features, and metadata.

Inputs: space_id (required).

get_spacesB

Get spaces from a ClickUp workspace. Returns space details including name, settings, and features.

Inputs: workspace_id (required).

get_task_commentsA

Get comments for a ClickUp task. Returns comment details including text, author, and timestamps.

Inputs: task_id (required), start, start_id.

get_task_detailsB

Get detailed information about a specific ClickUp task. Returns comprehensive task data including description, assignees, status, and dates.

Inputs: task_id (required), include_subtasks.

get_tasksB

Get tasks from a ClickUp list. Returns task details including name, description, assignees, and status.

Inputs: list_id (required), include_closed, subtasks, page, +2 more.

get_threaded_commentsA

Get threaded comments (replies) for a parent comment. Returns comment details with pagination support.

Inputs: comment_id (required), start, start_id.

get_workspacesA

Get a list of all ClickUp workspaces accessible to the authenticated user. Returns workspace IDs, names, and metadata.

Inputs: no named parameters.

get_workspace_seatsA

Get information about seats (user licenses) in a ClickUp workspace. Returns details about seat allocation and availability.

Inputs: workspace_id (required).

remove_task_from_listA

Remove a task from a ClickUp list without deleting the task.

Inputs: list_id (required), task_id (required).

search_docsA

Search for docs in a ClickUp workspace using a query string. Returns matching docs with their metadata.

Inputs: workspace_id (required), query (required), cursor.

update_checklistA

Update an existing ClickUp checklist's name.

Inputs: checklist_id (required), name (required).

update_checklist_itemB

Update an existing ClickUp checklist item's properties including name, assignee, and resolved status.

Inputs: checklist_id (required), checklist_item_id (required), name, assignee, +1 more.

update_commentB

Update an existing ClickUp comment's properties including text, assignee, and resolved status.

Inputs: comment_id (required), comment_text (required), assignee, resolved.

update_folderB

Update an existing ClickUp folder's name.

Inputs: folder_id (required), name (required).

update_listC

Update an existing ClickUp list's name.

Inputs: list_id (required), name (required).

update_taskB

Update an existing ClickUp task's properties including name, description, assignees, status, and dates.

Inputs: task_id (required), name, description, assignees, +8 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.4/5.0

    Scored across 42 tools

    Disambiguation4/5

    Most tools target distinct entities (tasks, lists, folders, etc.) with clear actions. However, there is potential confusion between create_list and create_folderless_list, and get_lists vs get_folderless_lists, though descriptions differentiate them. Overall, minimal overlap.

    Naming Consistency4/5

    The predominant pattern is verb_entity (e.g., create_task, delete_list, get_spaces). Some deviations like add_task_to_list and remove_task_from_list use a different structure, and create_list_from_template_in_folder is verbose but still consistent. No mixed case issues.

    Tool Count3/5

    42 tools is considerable, but ClickUp is a feature-rich platform with many entities (spaces, folders, lists, tasks, comments, checklists, docs). While each entity has CRUD and extras, the count feels slightly above ideal for coherence; could be streamlined.

    Completeness4/5

    The tool set covers common lifecycle operations for most core entities: create, read, update, delete for folders, lists, tasks, comments, and checklists. Missing updates for spaces and some advanced features (dependencies, custom fields), but the coverage is solid for typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches