ClickUp MCP server

ClickUp × Cursor

Use the ClickUp MCP server
in Cursor

Tasks, docs, and spaces across your ClickUp workspace, available to your AI. This guide connects ClickUp to Cursor (the AI code editor) 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 Cursor

Cursor adds MCP servers via MCP settings or install deep links. The gateway route takes about two minutes:

  1. Connect ClickUp to your free gate gateway from the verified directory.
  2. On your gate overview, click 'Add to Cursor' — Cursor opens and asks to install the gateway.
  3. Confirm and approve the sign-in.
  4. ClickUp's tools are now available to Cursor's agent, governed by your rules.

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, Claude Code, ChatGPT, 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 Cursor 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 · ClickUp in Claude Code · ClickUp in ChatGPT · ClickUp in VS Code