ClickUp MCP Pro
Let your coding agent read and update ClickUp workspaces, tasks, and custom fields without leaving the editor.
Overview
ClickUp MCP Pro is a MCP server for the Build phase that exposes 161 ClickUp tools and a clickup_raw escape hatch so agents can manage tasks and workspaces over the official v2/v3 API.
What is this MCP server?
- 161 named MCP tools plus clickup_raw for arbitrary ClickUp v2/v3 API calls
- stdio npm package clickup-mcp-pro with CLICKUP_READONLY guard for safe agent runs
- Optional CLICKUP_TEAM_ID default so tools work without repeating workspace id
- Full workspace coverage: tasks, folders, spaces, custom fields, and webhooks-style workflows via API
- Personal API token auth (pk_...) aligned with ClickUp’s official token model
- 161 dedicated MCP tools documented in server metadata
- clickup_raw tool for full ClickUp v2/v3 API coverage
- Server version 1.0.0 on npm identifier clickup-mcp-pro
What problem does it solve?
You keep specs and tasks in ClickUp but your agent cannot see or update them, so you manually sync context on every coding session.
Who is it for?
Indie builders and tiny teams who already run sprints in ClickUp and want Claude or Cursor to act on live task data during Build and Ship.
Skip if: Teams on Linear, Notion-only roadmaps, or anyone who only needs a one-off CSV export without ongoing API access.
What do I get? / Deliverables
After you register the stdio server with your ClickUp token, the agent can list, create, and update ClickUp entities in chat while respecting optional read-only mode.
- Agent-callable ClickUp operations across 161 tools
- Fallback clickup_raw calls for unwrapped v2/v3 endpoints
- Optional read-only enforcement via CLICKUP_READONLY
Recommended MCP Servers
Journey fit
ClickUp is where solo builders track sprints, bugs, and launch checklists while shipping; the canonical shelf is Build because the server is installed to wire PM into the product workflow, though it stays useful through Ship and Operate. The 161-tool surface maps to project management—lists, tasks, goals, time, and docs—not generic HTTP plumbing, so pm is the right subphase.
How it compares
Deep ClickUp API MCP integration, not a generic project-management skill or browser automation scraper.
Common Questions / FAQ
Who is ClickUp MCP Pro for?
Solo builders and small teams who use ClickUp as their task system and want their AI coding agent to read and write tasks, lists, and workspace data through MCP.
When should I use ClickUp MCP Pro?
Use it during Build and Ship when you want automated task updates from commits, agent-driven backlog triage, or scripted reporting without leaving your editor.
How do I add ClickUp MCP Pro to my agent?
Install the npm package clickup-mcp-pro, set CLICKUP_API_TOKEN (and optionally CLICKUP_TEAM_ID), add the stdio server entry in Claude Code or Cursor MCP config, and set CLICKUP_READONLY=true if you only need reads.