ClickUp MCP Server

What is ClickUp MCP Server?

This ClickUp MCP server is a commercial, independently maintained Model Context Protocol server by taazkareem. It lets AI agents manage ClickUp tasks, lists, sprints, docs, chat, comments and time tracking in natural language, and it requires a paid license.

The project began as open source and later moved to a paid model. Its README says it was refined during a consultancy with ClickUp but is now independent and not affiliated with or endorsed by ClickUp. A license unlocks about 150 tools. It can run as a hosted remote server (https://clickup-mcp.taazkareem.com/mcp) or locally over stdio via the npm package @taazkareem/clickup-mcp-server. ClickUp also runs its own official MCP server, covered below.

How to use ClickUp MCP Server?

Prerequisites:

• A license key, sold through Polar.sh (monthly, annual or lifetime, each with 3 device activations).
• For local stdio only: a ClickUp API token (ClickUp Settings > Apps > Generate under "API Token") and your Team ID, which is the first number after app.clickup.com/ in your workspace URL. Remote setups need neither.

The remote server authenticates with an X-License-Key header plus OAuth 2.1 to your ClickUp account. The local option passes the API key, Team ID and license key as environment variables.

Claude Code

claude mcp add --transport http ClickUp https://clickup-mcp.taazkareem.com/mcp \
  --header "X-License-Key: your-license-key"

Claude Desktop

The remote setup uses the mcp-remote adapter in claude_desktop_config.json:

{
  "mcpServers": {
    "ClickUp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://clickup-mcp.taazkareem.com/mcp",
        "--header",
        "X-License-Key: your-license-key"
      ]
    }
  }
}

Cursor

Add to <project-root>/.cursor/mcp.json (remote option):

{
  "mcpServers": {
    "ClickUp": {
      "url": "https://clickup-mcp.taazkareem.com/mcp",
      "headers": { "X-License-Key": "your-license-key" }
    }
  }
}

Or run it locally over stdio:

{
  "mcpServers": {
    "ClickUp": {
      "command": "npx",
      "args": ["-y", "@taazkareem/clickup-mcp-server@latest"],
      "env": {
        "CLICKUP_API_KEY": "your-api-key",
        "CLICKUP_TEAM_ID": "your-team-id",
        "CLICKUP_MCP_LICENSE_KEY": "your-license-key"
      }
    }
  }
}

VS Code

Use the same remote or local JSON in .vscode/mcp.json (workspace) or your user-level mcp.json.

Codex

Add to ~/.codex/config.toml:

[mcp_servers.ClickUp]
url = "https://clickup-mcp.taazkareem.com/mcp"
http_headers = { "X-License-Key" = "your-license-key" }

The README also covers Windsurf, Roo Code, Augment, n8n, ChatGPT, Antigravity and Hermes. For n8n there is a self-hosted Docker image: docker run -d -p 3231:3231 ghcr.io/taazkareem/clickup-mcp-server:latest.

Key features of ClickUp MCP Server

• Hybrid authentication: OAuth 2.1 with session-isolated caching, backwards compatible with API key and Team ID.
• Global fuzzy search across task, list, folder and space names, custom fields, members, statuses and tags, so the AI rarely needs raw IDs.
• Full task management: CRUD, moves, duplicates, links, dependencies, bulk operations, subtasks, checklists, custom fields, templates and attachments.
• Time tracking with timers, manual entries, edit history and workspace-wide filtering by natural-language dates.
• ClickUp Docs with markdown pages, plus comments and chat channels with threaded replies and reactions.
• Goals and Key Results, views, webhooks, tags and access control at every level of the hierarchy.
• Multi-workspace support in one session through extra API keys.
• Tool filtering by name, category or persona to cut context noise.

ClickUp MCP Server tools

The licensed server exposes about 150 tools, grouped by category:

• Tasks: create_task, update_task, move_task, create_bulk_tasks, get_workspace_tasks (deep search), add_task_dependency and task links.
• Comments, checklists and attachments: create_comment, create_comment_reply, create_checklist, create_checklist_item and upload_attachment.
• Sprints and structure: get_active_sprint, list_sprints, plus create, update and move tools for spaces, folders and lists, including set_list_permissions.
• Time tracking: start_time_entry, stop_time_entry, add_time_entry, get_time_entries and get_time_in_status.
• Docs and chat: create_document, update_document_page, create_chat_message and create_chat_message_reply.
• Goals, views, webhooks and admin: create_goal, create_key_result, create_view, create_webhook, user groups, guests and get_audit_logs (Enterprise).

To limit what the agent sees, set ENABLED_TOOLS / ENABLED_CATEGORIES locally, or X-Enabled-Tools / X-Enabled-Categories headers remotely. You can also pick a persona with CLICKUP_MCP_PERSONA or X-Persona, such as auditor (read-only), task_worker, project_manager or safe_power_user (everything except destructive deletes).

Use cases of ClickUp MCP Server

• Plan work from a chat: "Break the Q3 launch into a list with subtasks and owners."
• Check sprint health: "Audit the Sprint board and report what's at risk."
• Log time without leaving your editor: "Start a timer on the login bug task," then "Log 45 minutes on yesterday's code review."
• Keep docs current: "Append today's release notes to the Engineering Changelog doc."
• Triage across workspaces, for example moving or duplicating tasks between two authorized ClickUp accounts.
• Run read-only reporting agents with the auditor persona.

ClickUp MCP Server vs alternatives

ClickUp's own official MCP server is documented in the ClickUp Help Center. It is hosted by ClickUp and is the natural first choice if you want a vendor-supported connection. This taazkareem server is a paid third-party option that emphasizes a very large tool set, personas, tool filtering and multi-workspace sessions. For other project trackers, see the Asana MCP Server, Linear MCP Server or Trello MCP Server.

Troubleshooting ClickUp MCP Server

• An old free install stops getting fixes: earlier versions keep working, but they receive no updates, bug fixes or support without a license.
• License not accepted on remote setups: make sure the header is exactly X-License-Key: your-license-key. Claude Desktop needs the mcp-remote adapter to send it.
• Local stdio cannot reach your workspace: check CLICKUP_API_KEY and CLICKUP_TEAM_ID. The Team ID is the first number after app.clickup.com/ in the URL.
• Too many tools crowd the context: filter with ENABLED_CATEGORIES or a persona such as task_worker.
• n8n cannot connect to Docker: use http://host.docker.internal:3231/mcp as the URL.