ClickUp MCP server

ClickUp × Claude

Use the ClickUp MCP server
in Claude

Tasks, docs, and spaces across your ClickUp workspace, available to your AI. This guide connects ClickUp to Claude (claude.ai and the Claude desktop app) through a governed gateway — one URL that also works in every other MCP client you use, with your rules and a full log attached.

Live-probed · Security-scanned · Note: ClickUp currently restricts third-party sign-ins — API-key path recommended

Setup: ClickUp in Claude

Claude adds MCP servers via custom connectors in Settings. The gateway route takes about two minutes:

  1. Create a free gate gateway and connect ClickUp to it from the verified directory (one click — note: ClickUp currently restricts third-party sign-ins, so use the API-key path if the vendor offers one).
  2. Open claude.ai → Settings → Connectors and click 'Add custom connector'.
  3. Name it 'gate' and paste your gateway URL, then approve the authorization.
  4. Ask Claude something ClickUp can answer — the call runs through your gateway, with your rules applied and logged.

What to ask once it’s connected

What's overdue in the sprint space?
Create tasks from this feedback list.
Summarize the product-spec doc.
Which tasks are waiting on me?

Why route it through a gateway

One URL, every client

The same ClickUp connection works in Claude Code, ChatGPT, Cursor, VS Code too — no per-client re-wiring.

Rules before regret

Allow, ask, or block every tool ClickUp exposes — reads can flow freely while writes require your approval.

Every call logged

A plain-language activity log of everything Claude did with ClickUp — searchable, exportable, auditable.

Scanned and probed

ClickUp passed a live handshake probe and a security scan before listing — and drift detection watches it after you connect.

Also available: ClickUp in Claude Code · ClickUp in ChatGPT · ClickUp in Cursor · ClickUp in VS Code