What you need before you start
ClickUp runs its own MCP server at https://mcp.clickup.com/mcp, and the company states that it is available on all plans. That is the first useful fact here: nothing in the ClickUp billing stands between you and the connection, and the plan questions all come from the Claude side.
Which route you take depends on which Claude you pay for, not on what you want to do:
- Claude Pro, Team or Enterprise, in the browser or the desktop app: the Connectors menu, no file to edit.
- Claude Free, desktop app: the configuration file, because the Connectors menu route is documented for paid plans.
- Claude Code: one command in the terminal, then an authentication round.
Have these ready: a ClickUp account and workspace, a Claude account on one of those plans, and a rough idea of which lists the assistant should read, since ClickUp’s tools act with your own permissions and nothing more.
How the job is done with ClickUp
On a paid Claude plan. Open Settings in the browser or the desktop app, scroll to Connectors at the bottom, click Add, then fill two fields. Name: ClickUp. Remote MCP Server URL: https://mcp.clickup.com/mcp. Save, and complete the authorization that opens.
On Claude Free. Open the Claude desktop settings page, go to the Developer section, click Edit config, and open claude_desktop_config.json. Add this block, then restart the app:
{"mcpServers": {"clickup": {"command": "npx", "args": ["-y", "mcp-remote", "https://mcp.clickup.com/mcp"]}}}
The Claude Free route goes through mcp-remote, which needs Node.js on the machine.
In Claude Code. Run:
claude mcp add --transport http clickup https://mcp.clickup.com/mcp
Open a session, run /mcp, and follow the authentication flow.
Other clients are documented the same way, with the same URL: Cursor, VS Code, Windsurf, Devin and Copilot Studio each get a short section, and the address never changes.
What the server exposes is a large slice of the ClickUp API, arranged around work rather than around endpoints. Search across the whole workspace, including tasks, docs, dashboards, whiteboards, chats and forms. Task management: create, read and update tasks with assignees, priorities and due dates. Time tracking, with time entries and timers. Comments and chat, including summaries and posted updates. Every tool acts with your own permissions, so the assistant can do exactly what you could do by hand.
On this page
What to check in the result
Start with a search question you can verify in one glance, such as the tasks carrying a tag you know. A wrong search result usually means the connection landed on the wrong workspace.
Then create one task in a list you control, with an assignee, a due date and a priority, and check all three fields in ClickUp. The failure to catch is a task created with the right name and the wrong list, which looks correct in the chat and wrong in the workspace.
Ask for something across two tools, such as a summary of last week’s completed tasks with the time logged on them. A single tool call proves the connection; two calls in one answer prove the assistant can chain them, which is the point of the server.
Where it usually goes wrong
The plan mismatch runs the other way here. ClickUp’s server is on every plan, but the Connectors route in Claude needs a paid Claude plan, and a Free account that follows the wrong instructions ends up stuck in a menu that will not accept the server. The documented fix is the JSON file.
Rate limits. ClickUp states that the MCP server has rate limits that depend on the workspace plan and on whether the workspace bought the Everything AI add-on, and that usage falls under a fair use policy. A long agentic session can hit them, and the error arrives from ClickUp rather than from Claude.
Permissions. The assistant inherits your access, which means a workspace where you are a guest produces an assistant that can see almost nothing. That is not a bug in the MCP server.
Authentication on a client that caches. Some clients keep an old token after a workspace change, and the symptom is an assistant answering about a workspace you left.
What the plan allows
ClickUp bills the workspace, not the connection, and the MCP server is listed as available on all plans. On the grid read on November 6, 2026, the paid entry is $12 a month per user on the annual view, with a Free Forever tier below it that carries limits on storage and on some features.
What the connection really consumes is rate limit, not seats. The company ties the ceiling to the workspace plan and to the Everything AI add-on, so a workspace on the lowest tier should expect the assistant to slow down before it fails, and to fail earlier than a workspace that bought the add-on.
The full grid, tier by tier and with the date each price was read, is in the ClickUp review. ## What we did not do
Nobody on this site has connected ClickUp to Claude. We did not create an account, add the server to a client, run a prompt against it or hit a rate limit. Everything above comes from ClickUp’s developer documentation and pricing page, read on November 16, 2026.
The steps are documented rather than tested. We did not measure how many tool calls a typical request needs, we did not verify the rate limit numbers, which the documentation describes by criteria rather than by figures, and we did not test the Copilot Studio or Devin routes.
Sources
Read on November 16, 2026.
ClickUp’s MCP Server, https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server.
MCP Server Setup Instructions, https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server-1.
Supported Tools, https://developer.clickup.com/docs/mcp-tools.
Pricing, https://clickup.com/pricing, read November 6, 2026.
Update log
November 16, 2026: first version, built from ClickUp’s developer documentation and pricing page. No hands-on test has been done.
Start with ClickUp
This is an link to the publisher. A commission may be paid if you subscribe, and the price stays the same for you.