ClickUp MCP: The Official Server at mcp.clickup.com
Yes — ClickUp has an official MCP server. It’s hosted at mcp.clickup.com, built and maintained by ClickUp itself, and it’s in public beta on every plan. Point an MCP-compatible AI client at it, authorize with OAuth, and it can read and act on your tasks, Docs, and Chat.
The thing worth knowing before you set it up: an MCP server hands ClickUp to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches your Workspace for you, nothing fires when a task changes status, and nothing runs while the chat is closed. Here’s exactly what the ClickUp MCP does, how to turn it on, where it stops — and what to use when you want ClickUp work that runs on its own.
ClickUp is one of many — the complete list of MCP servers covers every app that ships one, grouped by category.
What the ClickUp MCP server does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, Cursor, VS Code, and others — talk to an outside app through a shared interface. ClickUp’s own remote server, live at mcp.clickup.com/mcp, exposes around 40 tools spanning search, tasks, time tracking, Chat, and Docs.
With it connected, an AI client can:
- Look up work — “find every open task assigned to me in the Q3 Launch list” answered from the live Workspace.
- Search across Docs and comments — pull a decision buried in a comment thread or a Doc without hunting for it.
- Create and route tasks — add a task with an assignee, priority, and due date across Lists and Spaces.
- Summarize Chat and threads — turn a long comment thread into action items.
It’s genuinely useful for ad-hoc work: ask a question, get an answer grounded in your actual Workspace, make a change on the spot.
How to set up the ClickUp MCP server
ClickUp hosts the server itself, so there’s nothing to install or run:
- In your AI client’s connector settings, add a remote MCP server pointing at
https://mcp.clickup.com/mcp. - Authorize it through the OAuth prompt against your ClickUp account — the agent then acts within your own permissions. Note that OAuth is the only auth path; personal API keys and auth tokens aren’t accepted for MCP.
- Confirm the tools appear in the client (ClickUp lists 22+ vetted clients, including Claude Desktop, ChatGPT, Cursor, VS Code, and Postman), then start a chat and ask it to look up or update something.
One catch worth knowing up front: the beta ships tight rate limits unless you have the Everything AI add-on — 50 calls per 24 hours on Free Forever, 300 per 24 hours on Unlimited and above. Heavy back-and-forth use can hit that ceiling fast.
Where the ClickUp MCP stops
None of this is a knock on MCP — it’s just the shape of the protocol, plus a beta-stage rate limit on top. Four limits show up the moment you want more than a conversation:
- It only works inside a chat you start. Close the window and nothing happens. The AI doesn’t watch ClickUp; it waits for you to ask.
- No triggers. A task moving to Complete, a new comment, a due date slipping — none of these can start anything through MCP. There’s no “when this happens in ClickUp, do that.”
- It’s one app at a time. The ClickUp MCP knows ClickUp. Getting a finished task into Slack, a client’s inbox, and a spreadsheet means wiring up (and authing) a separate MCP server for each, then hoping your client can juggle them in one turn.
- You own the plumbing, the scopes, and the rate limit. OAuth, the 50-or-300-calls-a-day ceiling, and the blast radius of what the AI can touch in your Workspace are all on you.
So the ClickUp MCP is a great way to ask ClickUp things and make one-off edits. It is not a way to make ClickUp run — to have work happen on a schedule or in reaction to an event, across the other tools a task touches.
Running ClickUp work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to ClickUp natively — no MCP server to point at, no OAuth to babysit, no daily call limit to watch — and to the ~260 other apps it supports, plus anything with a public API through your own key. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so ClickUp work happens whether or not anyone has a chat window open.
A few things that MCP can’t do but a Carly workflow can:
- When a task hits Complete → notify the client by email, log the hours to your time-tracking sheet, and post a summary in Slack — automatically, the moment it closes.
- Every Monday morning → pull every task overdue by more than 3 days across all Lists and send the owner a digest.
- When a new task is created from a form → enrich it with the right assignee and priority, and draft the kickoff comment for approval.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (drafting, summarizing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the ClickUp connection and everything downstream.
If you just want to interrogate your Workspace from a chat, ClickUp’s official MCP server is the right tool and it’s free to connect. If you want ClickUp to actually do things — on a trigger, on a schedule, across every app a task flows through — that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does ClickUp have an official MCP server?
Yes. ClickUp hosts it directly at mcp.clickup.com/mcp, and it’s available on every plan. It’s currently in public beta.
Is the ClickUp MCP server free? Connecting is free — you’re authorizing an AI client against your existing ClickUp account. Rate limits are tighter without the Everything AI add-on: 50 calls per 24 hours on Free Forever, 300 per 24 hours on Unlimited and above.
Can the ClickUp MCP trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven ClickUp work across apps, you need a workflow tool like Carly rather than an MCP server.
What AI tools can connect to ClickUp over MCP? ClickUp maintains an allowlist of 22+ vetted clients, including Claude Desktop, ChatGPT, Cursor, VS Code, and Postman.
Can I connect ClickUp to AI without coding or hosting a server? Yes. You don’t have to touch MCP at all. Carly connects to ClickUp for you and lets you build the automation in plain language — describe what you want to happen and it wires up ClickUp and the other apps involved, with no server to host and no rate limit to manage.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
