ClickUp MCP Server: Connect ClickUp to Claude

ClickUp has grown to 20+ million users worldwide by being the broadest project management platform — sales pipelines, marketing calendars, engineering sprints, docs, and time tracking all in one workspace. That breadth also makes it a uniquely good match for Claude: one MCP connection gives you AI-assisted queries across every function that lives in ClickUp.

What is ClickUp?

ClickUp is a cloud-based work management platform combining task management, docs, whiteboards, goals, time tracking, and team collaboration. It’s used across marketing, engineering, operations, sales, and professional services teams. ClickUp positions itself as “one app to replace them all” — and for many teams, it does consolidate what used to be 4–6 tools into a single workspace. This makes it particularly attractive for Claude integration: one MCP connection to ClickUp can replace several disparate integrations.

What is MCP and why does it matter for ClickUp users?

The Model Context Protocol (MCP) is an open standard by Anthropic that lets AI models connect to external tools. Unlike ClickUp’s built-in AI (which is useful but tied to ClickUp’s own model choices and context), MCP lets you use Claude — a full-capability assistant — with live access to your ClickUp data.

For ClickUp users, this means:

• Cross-team analysis: “Summarise what each department has delivered this quarter across their respective ClickUp spaces”
• Context-rich questions: “Look at every task tagged ‘bug’ in the last 30 days and tell me what the most common root causes have been”
• Cross-source reasoning: combine ClickUp data with data from your CRM or accounting system in a single Claude conversation

The native ClickUp AI is good at summarising a single task or list. MCP + Claude is good at reasoning across your entire ClickUp workspace and combining it with other systems.

Current state of ClickUp + Claude integration

As of April 2026, ClickUp is not in Anthropic’s Connectors Directory. There is no native Claude connector for ClickUp. This is notable given ClickUp’s user base and the clear demand — “how do I connect ClickUp to Claude” is a high-volume search query with no official answer.

Lightning Ventures’ MCP server for ClickUp covers the full ClickUp API v2 surface area:

• Tasks, subtasks, comments, attachments metadata, custom fields
• Spaces, folders, lists, views
• Time tracking entries and reports
• Goals and key results
• Workspace members and roles
• ClickUp Docs (via separate Docs API)

How it works

The ClickUp + Claude integration runs on your infrastructure via a locally-deployed MCP server. Lightning Ventures handles setup end-to-end: OAuth 2.0 configuration for multi-user team access (rather than a shared personal token), rate limiting to stay within ClickUp’s 100 req/min cap per workspace, response caching for stable metadata, monitoring, and an Australian Privacy Act compliance review.

Typical deployment is 3 business days for a standard read-only configuration covering Tasks, Spaces, Folders, Lists, Custom Fields, Time Tracking, and Docs. Multi-workspace, write workflows, or custom automations are 2–3 weeks under the Custom Build tier.

Security and compliance considerations

Personal API tokens have full account access. Treat them like a password. Never commit them to source control, and rotate them if you suspect exposure (ClickUp → Apps → Revoke and regenerate).

OAuth is required for multi-user deployments. If more than one person will use this MCP server, don’t share a personal token — each user should authenticate separately via OAuth 2.0 so access is scoped to their ClickUp permissions. Lightning Ventures’ Deploy & Harden tier handles this.

Data flow: ClickUp data → your locally-run MCP server → Claude’s context window. The MCP server does not cache or store ClickUp data between sessions.

Write operations require extra care. Claude writing to ClickUp is useful but introduces risk: a misinterpreted instruction could create or modify tasks in ways you don’t want. Lightning Ventures’ default configuration is read-only. For write access, we recommend approval gates — Claude drafts the change, you confirm, the write executes.

Privacy Act considerations: The MCP server runs on your infrastructure. Claude’s API calls (which include query context) are processed on Anthropic’s US-based servers — if ClickUp task content includes personal information about Australian residents (customer names, client contact details), factor Anthropic’s data processing terms into your Privacy Policy compliance review.