This MCP server provides an integration for ClickUp, focused on managing tasks and related workspace content. It supports operations across tasks, lists, docs, folders, and time, and is described as offering 50+ tools with instant setup. The package is referenced under the name io.github.taazkareem/clickup.
🛠️ Key Features
ClickUp tasks, lists, docs, and folders support
Time-related capabilities
50+ tools
Model Context Protocol (MCP) server
🚀 Use Cases
Automating task and list workflows in ClickUp
Working with ClickUp documentation and folder structure
Integrating time entries into productivity flows
⚡ Developer Benefits
Built as an MCP server (topics include mcp-server and model-context-protocol)
Properly Connect ClickUp to AI Agents and Agentic Workflows
A high-performance Model Context Protocol (MCP) server for managing tasks, checklists, sprints, comments, tags, spaces, lists, folders, files, docs, chat, and time using natural language.
⭐️ Proven Performance: 460+ Stars (from previous public repo) & thousands of weekly NPM downloads.
The industry-standard ClickUp integration for AI.
🔥 Multi-Account Support: Manage multiple authorized workspaces seamlessly in a single session. See setup
🔐 Hybrid Authentication
MCP spec-compliant OAuth 2.1 with advanced security hardening and session-isolated caching for fast, secure multi-tenant operation. Backwards compatible with API Key/Team ID(s).
🔍 Intelligent Search & Resolution
Smart tiered, global fuzzy search across task, list, folder, and space names, custom fields, members/emails, statuses, tags, descriptions, and more. Automatic resolution—no IDs needed.
📝 Task Management
Full CRUD, move, duplicate, link, and set dependencies between tasks. Supports bulk operations, nested subtasks, checklists, sprints (active detection), natural language dates, custom task IDs, custom task types, custom fields, task templates, and file attachments (upload via URL, local path, or base64).
⏱️ Time Tracking
Start/stop timers, log manual entries, edit existing entries, retrieve timer history, manage time entry tags, and filter time entries across the entire workspace using natural language dates or date ranges.
📄 Document Management
Create, read, and append to ClickUp Docs with full markdown text. Manage pages within documents for structured, long-form content (consolidated action-based tool).
💬 Comments & Chat
Post, edit, resolve, and reply to comments on tasks, lists, and views. Create and manage chat channels (including DMs), send messages with threaded replies, reactions, and follower management. Both support rich text, subtypes, and @mentions.
🎯 Goals & Key Results
Create and manage Goals with full lifecycle support—create, update, delete, and archive. Define and track nested Key Results to measure OKR progress across the workspace.
📋 Views
Create, list, update, and delete views at any level of the workspace hierarchy—space, folder, or list. Fetch tasks scoped to a specific view for focused filtering.
🗂️ Task Templates
Browse available task templates and instantly create tasks from them. Streamlines repeatable workflows without manual setup each time.
🌳 Workspace Control
Full CRUD for spaces, folders, lists, webhooks, and tags across the entire workspace hierarchy. Manage access control (ACL) permissions at any level. Switch workspaces mid-conversation without reconfiguration.
💎 Premium Access
Unlock 150 Enterprise-Grade Custom Tools
This project transitioned from open-source to a paid model for sustainable full-time development and priority support.
A license grants full, unrestricted access to all features across your agents⎯no limits.
Add via Chat: Grok Bot typically has no manual settings form for custom MCP servers. Instruct the Bot directly in chat:
text
Add a custom MCP server named ClickUp at https://clickup-mcp.taazkareem.com/mcp using streamable HTTP.
Public HTTPS Requirement: The endpoint must be public HTTPS (https://clickup-mcp.taazkareem.com/mcp). Localhost or stdio running on your local machine will not work because Grok Bot runs in the cloud.
Authentication: Connectors authenticate via MCP OAuth 2.1 (preferred). If a license header is supported by the client prompt, provide X-License-Key: your-license-key. Never paste secret license keys directly into the chat transcript—only provide them if prompted by a dedicated secure secret dialog.
Cloud Computer Stdio (Alternative): You can optionally run stdio directly on the Bot's cloud computer (not your local Mac) using:
bash
npx -y @taazkareem/clickup-mcp-server@latest
(Do not store credentials in command arguments on shared or team bots).
Usage: Once connected, attach the server in chat with @ClickUp or reference tasks directly. Built-in catalog plugins can also be managed in the Connect Apps sidebar (formerly Marketplace).
Meta Muse
Meta Muse is Meta's cloud AI assistant supporting tool integrations via Model Context Protocol connectors.
Important: The MCP server must be hosted on a public HTTPS endpoint because Muse executes in Meta's cloud infrastructure. Meta does not review custom connectors—grant permissions with caution.
Create Custom Connector via Chat: While built-in connectors can be found in Settings → Connectors, custom MCP connectors are created conversationally. Send Muse the following request in chat:
text
Create a Custom Connector for ClickUp MCP.
Transport: remote streamable HTTP
URL: https://clickup-mcp.taazkareem.com/mcp
Auth: OAuth (preferred) or license key via Secure Credentials as header X-License-Key
(Alternatively, if your client interface exposes it, navigate to Settings → Connectors → Add custom connector and paste the server URL).
Authentication & Credentials: Connect via OAuth 2.1 (preferred). If configuring a license key header (X-License-Key: your-license-key), store it in Muse's Secure Credentials Store when prompted—never post raw secret keys into conversational chat.
Usage: Ask Muse to interact with your ClickUp workspace (e.g. "List all high-priority tasks in my Sprint").
Dots (OpenAI Agents in ChatGPT)
Dots are OpenAI's always-on autonomous agents operating within ChatGPT. Rather than configuring MCP servers directly inside an individual Dot's settings, Dots execute through supported plugins and custom MCP connectors installed and enabled on your ChatGPT account.
Note: This section covers OpenAI's native ChatGPT Dots agent feature (not the unrelated GetDot analytics product). For standard ChatGPT setup, see ChatGPT (Developer Mode).
In ChatGPT on the web, navigate to Plugins → + → Add custom MCP server (or via Settings → Connectors).
Set Name:ClickUp
Set Server URL:https://clickup-mcp.taazkareem.com/mcp
Authentication:
Configure authentication using OAuth 2.1 (preferred) or add HTTP header X-License-Key: your-license-key when the form allows.
Acknowledge the risk warning and click Create as a plugin.
Account & Workspace Requirements:
Install and enable the plugin on your ChatGPT account.
Developer Mode and workspace administrative permissions apply (typically requires a ChatGPT Business, Enterprise, or Edu workspace for full read/write MCP capability; Pro accounts may have limited access).
Enable & Verify with your Dot:
Prompt your Dot in chat to access ClickUp (e.g. "Review active sprint tasks on ClickUp").
Documentation Gap Note: OpenAI documentation states that Dots utilize supported plugins on the account, but does not explicitly document whether every custom third-party MCP connector is universally recognized as "supported" across all Dot capabilities. Verify tool availability directly in your Dot chat session to confirm ClickUp actions trigger properly.
Claude Duet
Claude Duet is Anthropic's proactive, always-on personal AI agent (research preview for Pro/Max users). Operating continuously in the cloud, Duet surfaces morning briefs, triages incoming items, and coordinates workflows across integrated apps without requiring synchronous chat prompting. Because Claude Duet inherits its connected apps, memory, and skills directly from your Claude account, adding the ClickUp MCP connector equips Duet to monitor and manage your tasks, sprints, docs, and comments.
Important: The MCP server must be hosted on a public HTTPS endpoint because Claude Duet executes in Anthropic's cloud environment. Duet incorporates built-in confirmation safeguards: it proactively organizes and drafts updates, but pauses for your explicit sign-off before executing high-impact modifications.
Add Custom Connector in Claude:
In Claude on the web or desktop, click your profile / customize menu and navigate to Customize → Connectors (or click the + icon in any active chat and choose Manage connectors).
Click + next to Connectors and select Add custom connector.
Set Name:ClickUp
Set Server URL:https://clickup-mcp.taazkareem.com/mcp
Authentication & Permissions:
Configure authentication using OAuth 2.1 (preferred) or supply your license key via HTTP header X-License-Key: your-license-key.
Click Add to complete registration.
(For Claude Team and Enterprise workspaces, custom connectors are added and approved by an Owner/Admin in Organization Settings before team members enable them).
Usage & Proactive Routines:
Instruct Claude Duet in chat to track ClickUp activity (e.g. "Include high-priority ClickUp tasks in my daily morning brief" or "Alert me when blocked sprint dependencies clear").
Verify tool availability directly in your Duet session to ensure proactive ClickUp actions execute with proper approval prompts.
imageAntigravity (IDE & 2.0)
Download from antigravity.google. Covers Antigravity IDE (VS Code-based agentic editor) and Antigravity 2.0 (standalone desktop agent orchestration app). Both share the same configuration file.
Run a team of specialized agents on the same workspace (or separate). Each Hermes profile is an isolated agent with its own config and SOUL.md instructions. Configure each profile to match a persona (X-Persona) as needed. This will scope which ClickUp tools is in its context. Guide with examples:
Optional: Use --clone to copy the existing config.yaml/.env/SOUL.md, or re-run the commands from above.
2. Set each profile's persona. The profile has the MCP config now, so just add the matching persona:
bash
project_manager config set mcp_servers.clickup.headers.X-Persona "project_manager"
task_worker config set mcp_servers.clickup.headers.X-Persona "task_worker"
auditor config set mcp_servers.clickup.headers.X-Persona "auditor"
3. Give each agent its instructions in ~/.hermes/profiles/<name>/SOUL.md (auditor shown):
markdown
# ClickUp Auditor
You are a read-only project auditor. Observe and report — never change anything.
- Summarize task status, overdue items, and blockers concisely.
- Surface risks and recommend actions, but never execute them.
- If asked to create or modify a task, decline and explain you are read-only.
Run any agent query by its profile (call by User or Agent):
bash
project_manager chat -q "Break the Q3 launch into a list with subtasks and owners"
auditor chat -q "Audit the Sprint board and report what's at risk"
-OR-
Run a TUI or Gateway called by User:
bash
project_manager gateway start
auditor chat
Other (Custom Agents, etc.)
For most other MCP-compliant hosts:
Server URL:https://clickup-mcp.taazkareem.com/mcp
Auth Header:X-License-Key: your-license-key
OpenClaw (via mcporter)
1. Enable mcporter in ~/.openclaw/openclaw.json:
json
{"skills":{"allowBundled":["mcporter"]}}
2. Configure & Auth
bash
# Add ClickUp as a remote server
mcporter config add ClickUp https://clickup-mcp.taazkareem.com/mcp --auth oauth --header "X-License-Key=your-license-key"# Authenticate session
mcporter auth ClickUp
Pro Tip: Use Personas to define multiple isolated configurations (e.g., Auditor vs. Worker) in your agent's mcporter.json.
💡 Pro Tip! Reduce context noise for the AI by limiting available tools. There are 3 ways to do this. You can filter by exact tool name, by tool category, by personas (presets), or a combination of all three.
Simplify setup by using Personas. You can set a persona via the CLICKUP_MCP_PERSONA environment variable or the X-Persona HTTP header to automatically filter a set of tools.
Multiple personas can be combined (e.g., "X-Persona": "task_worker,time_specialist").
Persona
Description
Target Use Case
📋 auditor
Read-only access
View tasks, goals, docs, and chat (Read-only).
👷 task_worker
Daily management
Task CRUD, time tracking, and checklists.
⏱️ time_specialist
Time tracking focus
Time logs, timesheets, and entry history.
🏗️ project_manager
High-level control
Spaces, folders, lists, and bulk operations.
📚 content_manager
Communication
Docs, chat, comments, and attachments.
🏢 workspace_admin
Admin control
Permissions, guests, and audit logs.
💻 developer
Programmatic
Webhooks, custom fields, bulk automation.
🛡️ safe_power_user
Full access
All tools except destructive deletes/removals.
Local (Environment Variable):
json
"CLICKUP_MCP_PERSONA":"task_worker"
-or- Remote (Header):
json
"X-Persona":"task_worker"
💡 Need to customize? To view the exact tools included in each preset or to build a custom list based on a persona, see the Personas Reference Guide.
🌍 Multi-Workspace Support
Simultaneously federate OAuth and multiple API keys to manage tasks across different authorized ClickUp accounts/workspaces in a single session. Easily move or duplicate tasks between workspaces, configure AI Agents for cross-workspace automation, and more.
Why isn't this free anymore?
Building reliable MCP integrations requires significant maintenance. Moving to a paid model allows us to support this as a product rather than a hobby, ensuring compatibility with API changes.
I have an old version. Will it stop working?
Existing local clones will continue to work, but you will not receive updates, bug fixes, or support without a license.
How do I get support?
Premium users get priority support. Please open an issue in this repository.
⚖️ Disclaimer
Originally developed as open source and refined during a consultancy with ClickUp, this project is now independently maintained.
This software makes use of third-party APIs and may reference trademarks or brands owned by third parties. The use of such APIs or references does not imply any affiliation with or endorsement by the respective companies. All trademarks and brand names are the property of their respective owners. This project is an independent work and is not officially associated with or sponsored by any third-party company mentioned.